Get Observable verdicts - Cisco XDR APIs

{"type":"api","title":"Get Observable verdicts","meta":{"id":"/apps/pubhub/media/cisco-xdr-api-docs/fa9197522b1e6452b6dbfc472555dcc7ceeb71bd/0aedfab1-f4ca-36de-85d5-679dbd7db871","info":{"title":"IROH-INT Enrich","description":"IROH Integrations: configure and query Threat Response modules","contact":{"name":"Cisco Security Business Group -- Advanced Threat","email":"cisco-intel-api-support@cisco.com"},"license":{"name":"All Rights Reserved","url":"https://www.cisco.com"},"version":"1.0.107"},"security":[{"oAuth2":["integration:read","private-intel:read","profile:read","inspect:read","users:read","invite:read","enrich:read","oauth:read","response:read","global-intel:read","ao:read","playbook:read"]}],"tags":[{"name":"Health","description":"This set of routes allow to check the health of your integrations setup Verify if your modules are setup correctly and if your credentials are correct."},{"name":"Deliberate","description":"This set of routes allow to quickly get answers from your integrations You might use them at the start of any investigation to quickly get answers from your modules if something is bad."},{"name":"Observe","description":"This set of routes allow to get in depth investigation data about a threat You might use them at the start of any investigation to get the full picture and get to know if something has been seen in your environment."},{"name":"Refer","description":"This set of routes allow to get relevant Reference links and quickly pivot pursuing your investigation on a specific product interface. "}],"x-parser-conf":{"serverConfig":"select","overview":{"markdownPath":"reference/enrich/overview.md","uri":"enrich-api-guide"},"disableAuthEditing":true,"exampleAsDefault":true,"oAuth2":{"clientId":"client-546e34fc-c6bf-4951-ac69-f6d7987a7814","clientSecret":"MYw4_E_tBdFwUwrX6WFYKVD5LQrG2k7XrJ5J046wWE0s1gAKCxJ8VA","proxyEnabled":false},"meta":{"useProxy":true}},"openapi":"3.0.1","servers":[{"url":"https://visibility.amp.cisco.com"}],"securitySchemes":{"oAuth2":{"type":"oauth2","flows":{"clientCredentials":{"tokenUrl":"https://visibility.amp.cisco.com/iroh/oauth2/token","scopes":{"telemetry":"Collect application data for analytics","integration:read":"Manage your modules","private-intel:read":"Access Private Intelligence","admin":"Provide admin privileges","cognitive":"Cognitive Integration","profile:read":"Get your profile information","inspect:read":"Extract Observables and data from text","asset":"Access and modify your assets","event":"Read IROH Events","feedback":"Submit Customer Feedback","sse":"SSE Integration. Manage your Devices.","registry":"Manage registry entries","users:read":"Manage users of your organization","investigation":"Perform threat analysis investigation","invite:read":"Invite users into your organization","casebook":"Access and modify your casebooks","playbook":"Access and modify your playbooks","playbook:read":"Access and modify your playbooks","orbital":"Orbital Integration.","enrich:read":"Query your configured modules for threat intelligence","oauth:read":"Manage OAuth2 Clients","vault":"Grants access to Module Vaults","response:read":"List and execute response actions using configured modules","notification":"Receive notifications from integrations","global-intel:read":"Access AMP Global Intelligence","webhook":"Manage your Webhooks","ao:read":"AO Integration."}}}}}},"spec":{"tags":["Deliberate"],"summary":"Get Observable verdicts","description":"[required scopes](/iroh/doc/iroh-auth/#scopes): `enrich/observables/deliberate:read`\n\nThis route queries all enabled modules supporting the enrichment protocol with the supplied `Observables` in order to quickly get fast `Verdicts` from all your integrations.","parameters":[{"name":"mids","in":"query","description":"Use this parameter to query only some Modules passing their Ids","style":"form","explode":true,"schema":{"type":"array","items":{"type":"string"}}}],"requestBody":{"description":"An Observable list","content":{"application/json":{"schema":{"type":"array","description":"An Observable list","example":[{"type":"domain","value":"ilo.brenz.pl"},{"type":"email","value":"no-reply@internetbadguys.com"},{"type":"sha256","value":"8fda14f91e27afec5c1b1f71d708775c9b6e2af31e8331bbf26751bc0583dc7e"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"application/x-yaml":{"schema":{"type":"array","description":"An Observable list","example":[{"type":"domain","value":"ilo.brenz.pl"},{"type":"email","value":"no-reply@internetbadguys.com"},{"type":"sha256","value":"8fda14f91e27afec5c1b1f71d708775c9b6e2af31e8331bbf26751bc0583dc7e"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"application/edn":{"schema":{"type":"array","description":"An Observable list","example":[{"type":"domain","value":"ilo.brenz.pl"},{"type":"email","value":"no-reply@internetbadguys.com"},{"type":"sha256","value":"8fda14f91e27afec5c1b1f71d708775c9b6e2af31e8331bbf26751bc0583dc7e"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"application/transit+json":{"schema":{"type":"array","description":"An Observable list","example":[{"type":"domain","value":"ilo.brenz.pl"},{"type":"email","value":"no-reply@internetbadguys.com"},{"type":"sha256","value":"8fda14f91e27afec5c1b1f71d708775c9b6e2af31e8331bbf26751bc0583dc7e"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"application/transit+msgpack":{"schema":{"type":"array","description":"An Observable list","example":[{"type":"domain","value":"ilo.brenz.pl"},{"type":"email","value":"no-reply@internetbadguys.com"},{"type":"sha256","value":"8fda14f91e27afec5c1b1f71d708775c9b6e2af31e8331bbf26751bc0583dc7e"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}}},"required":true},"responses":{"200":{"description":"A `Bundle` including `Verdict` documents only","content":{"application/json":{"schema":{"type":"object","properties":{"data":{"type":"array","items":{"required":["data","module","module_instance_id","module_type_id"],"type":"object","properties":{"module":{"type":"string"},"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"data":{"type":"object","properties":{"tools":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The kind(s) of tool(s) being described.","example":["credential-exploitation"],"items":{"type":"string"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"tool","enum":["tool"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tool_version":{"type":"string","description":"The version identifier associated with the Tool.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of kill chain phases for which this Tool can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Tool"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataTools"},"indicators":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","producer","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"tags":{"type":"array","description":"Descriptors for this indicator.","example":["string"],"items":{"type":"string"}},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"producer":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","description":"The fixed value indicator","example":"indicator","enum":["indicator"]},"created":{"type":"string","format":"date-time"},"test_mechanisms":{"type":"array","description":"Test Mechanisms effective at identifying the cyber Observables specified in this cyber threat Indicator.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"composite_indicator_expression":{"required":["indicator_ids","operator"],"type":"object","properties":{"operator":{"type":"string","example":"and","enum":["not","or","and"]},"indicator_ids":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"operator":"and","indicator_ids":["string"]},"$$ref":"#/components/schemas/CompositeIndicatorExpression"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"likely_impact":{"type":"string","description":"Likely potential impact within the relevant context if this Indicator were to occur.","example":"string"},"indicator_type":{"type":"array","description":"Specifies the type or types for this Indicator.","example":["Anonymization"],"items":{"type":"string","enum":["File Hash Watchlist","Private Threat Feed","IMEI Watchlist","Malicious E-mail","Exfiltration","C2","URL Watchlist","IMSI Watchlist","Malware Artifacts","Domain Watchlist","Anonymization","Host Characteristics","IP Watchlist","Compromised PKI Certificate","Login Name"]}},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"Relevant kill chain phases indicated by this Indicator.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"negate":{"type":"boolean","description":"Specifies the absence of the pattern.","example":true},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"level of confidence held in the accuracy of this Indicator.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"specification":{"type":"object","example":{},"x-oneOf":[{"required":["judgements","required_judgements","type"],"type":"object","properties":{"type":{"type":"string","example":"Judgement","enum":["Judgement"]},"judgements":{"type":"array","example":["string"],"items":{"type":"string"}},"required_judgements":{"type":"array","example":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}],"items":{"required":["judgement_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"},"$$ref":"#/components/schemas/RelatedJudgement"}}},"additionalProperties":false,"description":"An indicator based on a list of judgements. If any of the Observables in it's judgements are encountered, than it may be matches against. If there are any required judgements, they all must be matched in order for the indicator to be considered a match.","example":{"type":"Judgement","judgements":["string"],"required_judgements":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}]},"$$ref":"#/components/schemas/JudgementSpecification"},{"required":["type","variables"],"type":"object","properties":{"type":{"type":"string","example":"ThreatBrain","enum":["ThreatBrain"]},"query":{"type":"string","example":"string"},"variables":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"description":"An indicator which runs in threatbrain...","example":{"type":"ThreatBrain","query":"string","variables":["string"]},"$$ref":"#/components/schemas/ThreatBrainSpecification"},{"required":["snort_sig","type"],"type":"object","properties":{"type":{"type":"string","example":"Snort","enum":["Snort"]},"snort_sig":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"Snort","snort_sig":"string"},"$$ref":"#/components/schemas/SnortSpecification"},{"required":["SIOC","type"],"type":"object","properties":{"type":{"type":"string","example":"SIOC","enum":["SIOC"]},"SIOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"SIOC","SIOC":"string"},"$$ref":"#/components/schemas/SIOCSpecification"},{"required":["open_IOC","type"],"type":"object","properties":{"type":{"type":"string","example":"OpenIOC","enum":["OpenIOC"]},"open_IOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which contains an XML blob of an openIOC indicator.","example":{"type":"OpenIOC","open_IOC":"string"},"$$ref":"#/components/schemas/OpenIOCSpecification"}]}},"additionalProperties":false,"$$ref":"#/components/schemas/Indicator"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIndicators"},"attack_patterns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"abstraction_level":{"type":"string","description":"The CAPEC abstraction level for patterns describing techniques to attack a system.","example":"aggregate","enum":["detailed","standard","aggregate","meta","category"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"attack-pattern","enum":["attack-pattern"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"x_mitre_platforms":{"type":"array","description":"ATT&CK Technique.Platforms.","example":["string"],"items":{"type":"string"}},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"x_mitre_data_sources":{"type":"array","description":"ATT&CK Technique.Data Sources.","example":["string"],"items":{"type":"string"}},"kill_chain_phases":{"type":"array","description":"A kill chain is a series of steps that an attacker must go through to successfully achieve their objective. The concept was originally developed by the military, but has been adapted to the cybersecurity field to describe the steps an attacker goes through to compromise a target system and achieve their goal.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"x_mitre_contributors":{"type":"array","description":"ATT&CK Technique.Contributors.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/AttackPattern"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataAttackPatterns"},"weaknesses":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Should be short and limited to the key points that define this weakness.","example":"string"},"background_details":{"type":"string","description":"Information that is relevant but not related to the nature of the weakness itself.","example":"string"},"paradigms":{"type":"array","description":"Applicable paradigms.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Paradigm name (Client Server, Mainframe)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Paradigm"}},"abstraction_level":{"type":"string","description":"Refers to the level of abstraction or granularity used to describe the weakness. It helps to categorize the vulnerability based on the level of detail provided.","example":"Base","enum":["Variant","Class","Base","Compound"]},"architectures":{"type":"array","description":"Applicable architectures.","example":[{"prevalence":"Often","name":"string","class":"Embedded"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Architecture name (ARM, x86, ...)","example":"string"},"class":{"type":"string","description":"Class of architecture","example":"Embedded"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Embedded"},"$$ref":"#/components/schemas/Architecture"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"alternate_terms":{"type":"array","description":"Indicates one or more other names used to describe this weakness.","example":[{"term":"string","description":"string"}],"items":{"required":["term"],"type":"object","properties":{"term":{"type":"string","description":"The actual alternate term.","example":"string"},"description":{"type":"string","description":"Provides context for the alternate term by which this weakness may be known.","example":"string"}},"additionalProperties":false,"example":{"term":"string","description":"string"},"$$ref":"#/components/schemas/AlternateTerm"}},"likelihood":{"type":"string","description":"Likelihood of exploit.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","description":"The fixed value weakness","example":"weakness","enum":["weakness"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"functional_areas":{"type":"array","description":"Identifies the functional area of the software in which the weakness is most likely to occur.","example":["Authentication"],"items":{"type":"string"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"modes_of_introduction":{"type":"array","description":"Information about how and when a given weakness may be introduced.","example":[{"phase":"Architecture and Design","note":"string"}],"items":{"required":["phase"],"type":"object","properties":{"phase":{"type":"string","description":"Identifies the point in the software life cycle at which the weakness may be introduced.","example":"Architecture and Design"},"note":{"type":"string","description":"Provides a typical scenario related to introduction during the given phase.","example":"string"}},"additionalProperties":false,"example":{"phase":"Architecture and Design","note":"string"},"$$ref":"#/components/schemas/ModeOfIntroduction"}},"structure":{"type":"string","description":"Defines the structural nature of the weakness.","example":"Chain","enum":["Chain","Simple","Composite"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"notes":{"type":"array","description":"Provides any additional comments about the weakness.","example":[{"content":"","id":"","note_class":"","related_entities":[],"schema_version":"1.3.18","type":"note"}],"items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}},"common_consequences":{"type":"array","description":"Refers to the typical or expected negative effects that can result from exploiting the weakness. This could include anything from unauthorized access to data, denial of service, system crashes or other things.","example":[{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"}],"items":{"required":["scopes"],"type":"object","properties":{"scopes":{"type":"array","description":"Identifies the security property that is violated.","example":["Access Control"],"items":{"type":"string"}},"impacts":{"type":"array","description":"Describes the technical impact that arises if an adversary succeeds in exploiting this weakness.","example":["Alter Execution Logic"],"items":{"type":"string"}},"likelihood":{"type":"string","description":"How likely the specific consequence is expected to be seen relative to the other consequences.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"note":{"type":"string","description":"Additional commentary about a consequence.","example":"string"}},"additionalProperties":false,"example":{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"},"$$ref":"#/components/schemas/Consequence"}},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"detection_methods":{"type":"array","description":"Identifies methods that may be employed to detect this weakness, including their strengths and limitations.","example":[{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"}],"items":{"required":["description","method"],"type":"object","properties":{"method":{"type":"string","description":"Identifies the particular detection method being described.","example":"Architecture or Design Review"},"description":{"type":"string","description":"Provides some context of how this method can be applied to a specific weakness.","example":"string"},"effectiveness":{"type":"string","description":"How effective the detection method may be in detecting the associated weakness.","example":"High"},"effectiveness_notes":{"type":"string","description":"Provides additional discussion of the strengths and shortcomings of this detection method.","example":"string"}},"additionalProperties":false,"example":{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"},"$$ref":"#/components/schemas/DetectionMethod"}},"operating_systems":{"type":"array","description":"Applicable operating systems.","example":[{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"version":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"cpe_id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"class":{"type":"string","description":"Class of Operating System.","example":"Android"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"},"$$ref":"#/components/schemas/OperatingSystem"}},"client_id":{"type":"string"},"affected_resources":{"type":"array","description":"Identifies system resources that can be affected by an exploit of this weakness.","example":["CPU"],"items":{"type":"string"}},"languages":{"type":"array","description":"Applicable Languages.","example":[{"prevalence":"Often","name":"string","class":"Assembly"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Language name (Clojure, Java, ...)","example":"string"},"class":{"type":"string","description":"Class of language.","example":"Assembly"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Assembly"},"$$ref":"#/components/schemas/Language"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"potential_mitigations":{"type":"array","description":"Describes potential mitigations associated with a weakness.","example":[{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"}],"items":{"required":["description"],"type":"object","properties":{"description":{"type":"string","description":"A description of this individual mitigation including any strengths and shortcomings of this mitigation for the weakness.","example":"string"},"phases":{"type":"array","description":"Indicates the development life cycle phase during which this particular mitigation may be applied.","example":["Architecture and Design"],"items":{"type":"string"}},"strategy":{"type":"string","description":"A general strategy for protecting a system to which this mitigation contributes.","example":"Attack Surface Reduction"},"effectiveness":{"type":"string","description":"Summarizes how effective the mitigation may be in preventing the weakness.","example":"Defense in Depth"},"effectiveness_notes":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"}},"additionalProperties":false,"example":{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"},"$$ref":"#/components/schemas/Mitigation"}},"technologies":{"type":"array","description":"Applicable technologies.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Technology name (Web Server, Web Client)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Technology"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Weakness"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataWeaknesses"},"feedbacks":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["entity_id","feedback","id","reason","schema_version","type"],"type":"object","properties":{"feedback":{"type":"integer","format":"int64","example":-1,"enum":[0,1,-1]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"feedback","enum":["feedback"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Feedback"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataFeedbacks"},"verdicts":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["disposition","observable","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"type":{"type":"string","example":"verdict","enum":["verdict"]},"created":{"type":"string","format":"date-time"},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Numeric verdict identifiers.","format":"int64","example":1,"enum":[1,4,3,2,5]},"disposition_name":{"type":"string","description":"The disposition_name field is optional, but is intended to be shown to a user. Applications must therefore remember the mapping of numbers to human words, as in: {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"client_id":{"type":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/Verdict"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVerdicts"},"campaigns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["campaign_type","description","id","schema_version","short_description","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"campaign","enum":["campaign"]},"created":{"type":"string","format":"date-time"},"campaign_type":{"type":"string","description":"String value that describes the type of campaign. For example, a campaign type could be 'Ransomware', 'Advanced Persistent Threat', 'Business Email Compromise', 'Phishing', etc. ","example":"string"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"activity":{"type":"array","description":"Used to capture specific activities or tactics associated with the campaign.\nThe 'activity' field is an array of objects, and each element represents a specific activity and time associated with the campaign. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc. By capturing these activities analysts can identify the specific tactics used by the threat actor(s) behind the campaign.","example":[{"date_time":"2016-01-01T01:01:01.000Z","description":"string"}],"items":{"required":["date_time","description"],"type":"object","properties":{"date_time":{"type":"string","description":"Specifies the date and time at which the activity occured.","format":"date-time","example":"2016-01-01T01:01:01Z"},"description":{"type":"string","description":"A description of the activity.","example":"string"}},"additionalProperties":false,"description":"Captures the specific activities or tactics associated with the entity. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc.","example":{"date_time":"2016-01-01T01:01:01.000Z","description":"string"},"$$ref":"#/components/schemas/Activity"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"array","description":"Characterizes the intended effect of this cyber threat campaign.","example":["Account Takeover"],"items":{"type":"string"}},"status":{"type":"string","description":"Indicates current Status of the Campaign. \n\nCan have one of the following values: \n\n- Ongoing: Indicates that the campaign is currently active and ongoing. For example, a mass phishing campaign that is actively targeting users is considered 'ongoing'.\n\n- Historic: Campaign has already occurred and is now in the past.\n\n- Future: This indicates that a campaign is planned or expected to occur in the future. For example, a threat actor may announce their intention to launch a specific cyberattack campaign at a future date.","example":"Future","enum":["Historic","Future","Ongoing"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Level of confidence held in the characterization of this Campaign.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"names":{"type":"array","description":"Used to capture alternate names or aliases associated with the campaign. A cyberattack campaign may have multiple names or aliases depending on the group or actor(s) behind the attack, e.g., 'Wannacry' is also known as 'WannaCrypt', 'WCry', 'Wanna Decryptor', etc.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Campaign"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCampaigns"},"actors":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","source","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"motivation":{"type":"string","description":"The reason or purpose behind the malicious activity attributed to this Actor. By understanding a threat actor's motivation, analysts can better predict the attacker's behavior and anticipate future malicious actions.","example":"Ego"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["description","related_identities"],"type":"object","properties":{"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"related_identities":{"type":"array","description":"Identifies other entity Identities related to this Identity.","example":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}],"items":{"required":["identity"],"type":"object","properties":{"identity":{"type":"string","description":"The reference (URI) of the related Identity object.","example":"string"},"confidence":{"type":"string","description":"Specifies the level of confidence in the assertion of the relationship between the two objects.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"information_source":{"type":"string","description":"Specifies the source of the information about the relationship between the two components.","example":"string"},"relationship":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes a related Identity","example":{"identity":"string","confidence":"High","information_source":"string","relationship":"string"},"$$ref":"#/components/schemas/RelatedIdentity"}}},"additionalProperties":false,"description":"Can contain information such as the name of the attacker, the group or organization they belong to, or any other identifier that can help in the attribution process.","example":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"$$ref":"#/components/schemas/Identity"},"sophistication":{"type":"string","description":"Represents the level of expertise and skill that the threat actor has displayed in their malicious activities. Can help security analysts assess the potential impact of an attacker's TTPs and determine the potential attack surface. \n\nFor example, a threat actor with a low sophistication level may primarily rely on off-the-shelf malware and attack tools, while an attacker with high sophistication may use custom tools with advanced evasion techniques, zero-day exploits, and sophisticated methods for command and control of their malware. \n\nThe sophistication level of an attacker can also be inferred based on several factors such as the complexity of attacks, the attacker's knowledge of the targeted organization's systems, and the attacker's ability to remain undetected.\n\nIf an attacker shows a high level of sophistication in reconnaissances, social engineering, and phishing, then the attacker may have a good knowledge of the targeted organization and its employees. This means that the attacker may be more successful in infiltrating the organization's network and compromising its systems.","example":"Aspirant","enum":["Aspirant","Innovator","Practitioner","Novice","Expert"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"planning_and_operational_support":{"type":"string","description":"Provides information about the resources and capabilities of the attacker that could be used to assist in planning and operations related to the threat.\n\n It can be used to describe Infrastructure, Tools, Techniques, and Capabilities used by the threat actor.","example":"string"},"type":{"type":"string","example":"actor","enum":["actor"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Represents the desired outcome or impact the threat actor is trying to achieve through their malicious activities. \n\n Helps security analysts to understand the attacker's goals beyond the immediate impact of the attack. By understanding the intended effect, analysts can draw connections between seemingly unrelated attacks and build a more complete understanding of an attacker's long-term goals and motivations.","example":"Account Takeover"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"aliases":{"type":"array","description":"A list of other names that this Threat Actor is believed to use.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"This field can help analysts decide how much trust they can put in the information provided by the threat intelligence sources.\n\nFor example, an Actor entity can have high confidence if the organization's security researchers have been tracking it for a long time and have gathered a significant amount of intelligence about it through various sources, such as analysis of malware, network traffic, and human intelligence. In contrast, low confidence may indicate the organization has only seen limited or circumstantial evidence.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Actor"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataActors"},"data_tables":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["columns","id","rows","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"columns":{"type":"array","description":"An ordered list of column definitions.","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"type":{"type":"string","example":"data-table","enum":["data-table"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"rows":{"type":"array","description":"An ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/DataTable"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataDataTables"},"notes":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataNotes"},"identity_assertions":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["assertions","id","identity","schema_version","type"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["observables"],"type":"object","properties":{"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"additionalProperties":false,"description":"Attributes for which the assertion is being made.","example":{"observables":[{"value":"1.2.3.4","type":"ip"}]},"$$ref":"#/components/schemas/IdentityCoordinates"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"identity-assertion","enum":["identity-assertion"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"assertions":{"type":"array","description":"Any known context about the identity attributes.","example":[{"name":"cisco:ctr:ad:host_domain_name","value":"string"}],"items":{"required":["name","value"],"type":"object","properties":{"name":{"type":"string","description":"An open vocabulary containing well known assertion types","example":"cisco:ctr:ad:host_domain_name"},"value":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"cisco:ctr:ad:host_domain_name","value":"string"},"$$ref":"#/components/schemas/Assertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/IdentityAssertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIdentityAssertions"},"judgements":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","disposition","disposition_name","id","observable","priority","schema_version","severity","source","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"reason_uri":{"type":"string","description":"A URI","example":"string"},"type":{"type":"string","example":"judgement","enum":["judgement"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Matches :disposition_name as in {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","format":"int64","example":1,"enum":[1,4,3,2,5]},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"disposition_name":{"type":"string","description":"String verdict identifiers.","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"priority":{"type":"integer","description":"A value 0-100 that determine the priority of a judgement. Curated feeds of black/white lists, for example known good products within your organizations, should use a 95. All automated systems should use a priority of 90, or less. Human judgements should have a priority of 100, so that humans can always override machines.","format":"int64","example":10},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]}},"additionalProperties":false,"$$ref":"#/components/schemas/Judgement"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataJudgements"},"malwares":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The type of malware being described.","example":["adware"],"items":{"type":"string"}},"abstraction_level":{"type":"string","description":"Malware abstraction level.","example":"family","enum":["family","version","variant"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"malware","enum":["malware"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of Kill Chain Phases for which this Malware can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Malware"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataMalwares"},"incidents":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","id","incident_time","schema_version","status","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"assignees":{"type":"array","description":"A set of owners assigned to this incident.","example":["string"],"items":{"type":"string"}},"meta":{"type":"object","additionalProperties":{"type":"object","description":"custom field relevant to attach meta data to.","example":{},"x-oneOf":[{"example":"string","type":"string"},{"example":10,"type":"number","format":"double"},{"example":"2016-01-01T01:01:01.000Z","type":"string","format":"date-time"},{"example":"keyword","type":"string"},{"example":true,"type":"boolean"}]},"description":"metadata associated to the incident.","example":{"keyword":{}},"$$ref":"#/components/schemas/MetaData"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"incident","enum":["incident"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"incident_time":{"required":["opened"],"type":"object","properties":{"opened":{"type":"string","description":"Time the incident was first opened.","format":"date-time","example":"2016-01-01T01:01:01Z"},"discovered":{"type":"string","description":"Time the incident was first discovered.","format":"date-time","example":"2016-01-01T01:01:01Z"},"reported":{"type":"string","description":"Time the incident was first reported.","format":"date-time","example":"2016-01-01T01:01:01Z"},"remediated":{"type":"string","description":"Time that the remediation of the damage from the incident was completed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"closed":{"type":"string","description":"Time that the incident was last closed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"rejected":{"type":"string","description":"Time that the incident was first rejected.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Relevant time values associated with this Incident.","example":{"opened":"2016-01-01T01:01:01.000Z","discovered":"2016-01-01T01:01:01.000Z","reported":"2016-01-01T01:01:01.000Z","remediated":"2016-01-01T01:01:01.000Z","closed":"2016-01-01T01:01:01.000Z","rejected":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/IncidentTime"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"discovery_method":{"type":"string","description":"Identifies how the incident was discovered.","example":"Agent Disclosure"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Specifies the suspected intended effect of this incident","example":"Account Takeover"},"categories":{"type":"array","description":"A set of categories for this incident.","example":["Attrition"],"items":{"type":"string"}},"status":{"type":"string","description":"The `status` field represents the current state of an incident within the incident management process. Its values help in tracking and reporting the progress of the incident from its discovery to its resolution.","example":"Closed","enum":["New","Closed","Open: Recovered","Closed: Other","Hold: Internal","Hold: Legal","Closed: Under Review","Rejected","Open","Restoration Achieved","Incident Reported","Closed: Suspected","Stalled","Open: Contained","Closed: Near-Miss","Hold: External","Containment Achieved","New: Processing","Closed: Confirmed Threat","Closed: False Positive","Open: Reported","Open: Investigating","Hold","New: Presented"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"promotion_method":{"type":"string","description":"Describes method for promoting an Incident, whether manually or automatically. An Incident may be created manually by a SOAR analyst or SOC operator, or through an automated correlation or aggregation rule or engine that matches a specific set of events or alerts, and promotes them to Incident(s).","example":"Automated","enum":["Automated","Manual"]},"severity":{"type":"string","description":"Represents the potential impact of an incident on an organization's security posture and business operations. It helps organizations prioritize and allocate resources for incident response based on the severity level of the incident \nIt helps analysts and incident handlers prioritize incidents by indicating the level of risk and potential impact associated with the incident. This enables organizations to allocate resources efficiently and address the most critical incidents first.\nCan also be used to generate reports and metrics for measuring the effectiveness of the incident response process and to identify trends and patterns in the threat landscape.\nIt is important to note that the `severity` field is subjective and can be interpreted differently by different organizations or analysts. Therefore, it should be used in conjunction with other intelligence attributes, such as the `confidence` field, to provide a more comprehensive view of the incident.","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"scores":{"type":"object","additionalProperties":{"type":"number","description":"Field is used to indicate the severity or impact of the threat represented by the incident.\nIt's an open-type dictionary object with score types and numeric value of the score.\n\nFor example, systems can have the following score types:\n\n- `asset` - assesses the potential damage or harm that the threat can cause to the affected asset(s). The scale ranges from 0 to 10, with 10 indicating the highest potential harm. \n\n- `global` - assesses the overall impact or significance of the threat to the organization or wider community. The scale ranges from 0 to 1000, with 1000 indicating the highest impact.\n\n- `ttp` - a measure of the threat actor's proficiency in utilizing TTPs. Typically, ranges from 0-100, with a higher score indicating a greater threat or concern.","format":"double","example":10},"description":"Used to indicate the severity or impact score of the threat represented by the incident.","example":{"asset":10},"$$ref":"#/components/schemas/IncidentScores"},"client_id":{"type":"string"},"techniques":{"type":"array","description":"Represents the specific methods or actions used by an attacker to carry out an offensive maneuver or achieve their goals.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Represents the level of certainty or trustworthiness associated with the incident. It denotes the reliability of the intelligence associated with the incident.\nThe `confidence` field can take on several values, including:\n- `info`: Indicates that the incident information is based on sources with no previous track record or there is no track record for the source reporting the incident.\n- `low`: Indicates that the incident information is based on sources with a questionable track record or there is limited information about the accuracy of the source.\n- `medium`: Indicates that the incident information is based on sources with a mixed track record or of uncertain reliability.\n- `high`: Indicates that the incident information is based on sources with a proven track record and high degree of reliability.\nThe `confidence` field can be used to indicate the level of trust and confidence that can be attributed to the incident, and it may impact how the incident is prioritized, analyzed and addressed. It can also help in the decision-making process associated with the incident response activities.\nIt is important to note that the `confidence` field is subjective and can be interpreted differently by different organizations or analysts. As such, it is often used in conjunction with other intelligence attributes, such as the `severity` field, to provide a more complete picture of the incident.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"tactics":{"type":"array","description":"Represents the offensive techniques, approaches, or procedures that an adversary may use to achieve their objectives during an attack. It helps in understanding the intent and capabilities of the adversary and can be used to identify indicators of attack (IoAs) or indicators of compromise (IoCs) that are associated with the adversary's tactics.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Incident"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIncidents"},"sightings":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","count","id","observed_time","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"relations":{"type":"array","description":"Provide any context we can about where the observable came from.","example":[{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}}],"items":{"required":["origin","related","relation","source"],"type":"object","properties":{"origin":{"type":"string","example":"string"},"origin_uri":{"type":"string","description":"A URI","example":"string"},"relation":{"type":"string","example":"Allocated"},"relation_info":{"type":"object","additionalProperties":{"type":"object","example":{}},"example":{"keyword":{}},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightingsDocsRelationsRelationInfo"},"source":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"related":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"additionalProperties":false,"description":"A relation inside a Sighting.","example":{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}},"$$ref":"#/components/schemas/ObservedRelation"}},"sensor_coordinates":{"required":["observables","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the device that made the sighting (sensor) and contains identifying observables for the sensor.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"os":"string"},"$$ref":"#/components/schemas/SensorCoordinates"},"observables":{"type":"array","description":"The object(s) of interest.","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"type":{"type":"string","example":"sighting","enum":["sighting"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"targets":{"type":"array","description":"May include one or more targets that observed the associated indicator. Targets can include network devices, host devices, or other entities that are capable of detecting indicators of compromise.\n\nCan be used to assess the scope of potential threats, helping analysts understand which devices or components of the network may be vulnerable to attack. For example, if a particular malware strain is detected on several different systems within an organization, the `targets` field may indicate which systems are affected and which may need to be isolated or patched to prevent further spread.","example":[{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"}],"items":{"required":["observables","observed_time","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the target of the sighting and contains identifying observables for the target.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"},"$$ref":"#/components/schemas/IdentitySpecification"}},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"resolution":{"type":"string","description":"Represents the disposition or actions taken on the associated threat intelligence.","example":"detected"},"internal":{"type":"boolean","description":"If `true`, indicates that the sighting was reported from internal sources, such as an organization's own internal security tools or SOC.\n Internal sightings are often considered more reliable and actionable than external sightings, which are reported from external sources and may have a lower level of trustworthiness. Internal sightings can provide more context and can help identify potential threats that are unique to a particular environment or organization.\n Internal sightings can also help organizations prioritize their security response efforts by identifying threats that are specific to their environment and may not yet be widely known.","example":false},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"count":{"type":"integer","description":"The number of times an indicator was observed within a certain period of time.\nFor example, if an IP address associated with known malicious activity is observed once within a period of time, it may indicate a low-level threat. However, if the same IP address is observed multiple times within a short time frame, it may indicate a more severe and persistent threat.\nIt can also be used to prioritize security alerts and indicate the urgency of a response. High counts indicate that an indicator is actively being used in a larger campaign, while low counts may indicate isolated incidents.","format":"int64","example":10},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"context":{"type":"object","properties":{"http_events":{"type":"array","description":"a list of `HTTPType`","example":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"items":{"required":["host","process_id","process_name","time","traffic","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"method":{"type":"string","example":"CONNECT","enum":["OPTIONS","PATCH","TRACE","HEAD","POST","CONNECT","GET","PUT"]},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"HTTPEvent","enum":["HTTPEvent"]},"host":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"query":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"encrypted":{"type":"boolean","example":true},"url_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10},"$$ref":"#/components/schemas/HTTPType"}},"process_create_events":{"type":"array","description":"a list of `ProcessCreate`","example":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"items":{"required":["process_id","process_name","time","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"parent_process_guid":{"type":"integer","format":"int64","example":10},"process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_size":{"type":"integer","format":"int64","example":10},"process_size":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"ProcessCreateEvent","enum":["ProcessCreateEvent"]},"parent_process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_creation_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"},"$$ref":"#/components/schemas/ProcessCreateType"}},"registry_delete_events":{"type":"array","description":"a list of `RegistryDeleteType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryDeleteEvent","enum":["RegistryDeleteEvent"]},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"},"$$ref":"#/components/schemas/RegistryDeleteType"}},"file_modify_events":{"type":"array","description":"a list of `FileModifyType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileModifyEvent","enum":["FileModifyEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileModifyType"}},"registry_set_events":{"type":"array","description":"a list of `RegistrySetType`","example":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_value","time","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"registry_data":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"RegistrySetEvent","enum":["RegistrySetEvent"]},"registry_data_length":{"type":"integer","format":"int64","example":10},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"},"$$ref":"#/components/schemas/RegistrySetType"}},"file_create_events":{"type":"array","description":"a list of `FileCreateType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileCreateEvent","enum":["FileCreateEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileCreateType"}},"registry_create_events":{"type":"array","description":"a list of `RegistryCreateType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryCreateEvent","enum":["RegistryCreateEvent"]}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"},"$$ref":"#/components/schemas/RegistryCreateType"}},"library_load_events":{"type":"array","description":"a list of `LibraryLoadType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"items":{"required":["dll_library_name","dll_library_path","process_id","process_name","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"LibraryLoadEvent","enum":["LibraryLoadEvent"]},"dll_library_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"dll_library_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"},"$$ref":"#/components/schemas/LibraryLoadType"}},"file_move_events":{"type":"array","description":"a list of `FileMoveType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"items":{"required":["file_name","file_path","new_name","old_name","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileMoveEvent","enum":["FileMoveEvent"]},"old_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"new_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"},"$$ref":"#/components/schemas/FileMoveType"}},"file_delete_events":{"type":"array","description":"a list of `FileDeleteType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileDeleteEvent","enum":["FileDeleteEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileDeleteType"}},"netflow_events":{"type":"array","description":"a list of `NetflowType`","example":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"items":{"required":["process_id","process_name","time","traffic","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_in":{"type":"integer","format":"int64","example":10},"process_guid":{"type":"integer","format":"int64","example":10},"process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"flow_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"NetflowEvent","enum":["NetflowEvent"]},"process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_out":{"type":"integer","format":"int64","example":10},"process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"},"$$ref":"#/components/schemas/NetflowType"}},"registry_rename_events":{"type":"array","description":"a list of `RegistryRenameType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_old_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryRenameEvent","enum":["RegistryRenameEvent"]},"registry_old_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"},"$$ref":"#/components/schemas/RegistryRenameType"}}},"additionalProperties":false,"description":"Context including the event type that best fits the type of the sighting.","example":{"http_events":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"process_create_events":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"registry_delete_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"file_modify_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_set_events":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"file_create_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_create_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"library_load_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"file_move_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"file_delete_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"netflow_events":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"registry_rename_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}]},"$$ref":"#/components/schemas/Context"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"sensor":{"type":"string","description":"The OpenC2 Actuator name that best fits the device that is creating this sighting (e.g. network.firewall)","example":"endpoint"},"data":{"required":["columns","rows"],"type":"object","properties":{"columns":{"type":"array","description":"an ordered list of column definitions","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"rows":{"type":"array","description":"an ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10}},"additionalProperties":false,"description":"An embedded data table for the Sighting.","example":{"columns":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"rows":[[{}]],"row_count":10},"$$ref":"#/components/schemas/SightingDataTable"}},"additionalProperties":false,"$$ref":"#/components/schemas/Sighting"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightings"},"relationships":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","relationship_type","schema_version","source_ref","target_ref","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"target_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"type":{"type":"string","example":"relationship","enum":["relationship"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"source_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"relationship_type":{"type":"string","example":"attributed-to"}},"additionalProperties":false,"$$ref":"#/components/schemas/Relationship"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataRelationships"},"vulnerabilities":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Various sources of vulnerability information can be used, including third-party resources like the National Vulnerability Database (NVD) and the Common Vulnerabilities and Exposures (CVE) database. The platform then analyzes this data and provides the user with relevant details such as the severity of the vulnerability, the affected systems, and remediation recommendations. \n\n Based on this information, the user can prioritize patching and other mitigation strategies to reduce the risk of potential attacks.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"}},"additionalProperties":false,"$$ref":"#/components/schemas/Vulnerability"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVulnerabilities"},"coas":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"stage":{"type":"string","description":"Specifies what stage in the cyber threat management lifecycle this Course Of Action is relevant to.","example":"Containment","enum":["Identification","Lessons Learned","Remedy","Preparation","Containment","Response","Eradication","Recovery"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"efficacy":{"type":"string","description":"Effectiveness of this course of action in achieving its targeted objective.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","example":"coa","enum":["coa"]},"created":{"type":"string","format":"date-time"},"related_COAs":{"type":"array","description":"Identifies or characterizes relationships to one or more related courses of action.","example":[{"confidence":"High","source":"string","relationship":"string","COA_id":"string"}],"items":{"required":["COA_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"COA_id":{"type":"string","description":"A URI leading to a COA.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","COA_id":"string"},"$$ref":"#/components/schemas/RelatedCOA"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"coa_type":{"type":"string","description":"The type of this COA","example":"Diplomatic Actions","enum":["Diplomatic Actions","Physical Access Restrictions","Policy Actions","Internal Blocking","Playbook","Redirection","Phase","Eradication","Public Disclosure","Monitoring","Patching","Logical Access Restrictions","Redirection (Honey Pot)","Rebuilding","Perimeter Blocking","Hardening","Other","Training","Task"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"objective":{"type":"array","description":"Characterizes the objective to provide guidance on how to mitigate a security incident that has been identified.","example":["string"],"items":{"type":"string"}},"cost":{"type":"string","description":"Characterizes the estimated cost for applying this course of action.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"open_c2_coa":{"required":["action","type"],"type":"object","properties":{"type":{"type":"string","example":"structured_coa","enum":["structured_coa"]},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"action":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"alert","enum":["stop","save","delete","remediate","redirect","alert","query","augment","snapshot","update","allow","scan","investigate","modify","sync","start","pause","deny","substitute","distill","move","restart","other","detonate","response","set","notify","report","restore","get","throttle","mitigate","resume","locate","contain"]}},"additionalProperties":false,"example":{"type":"alert"},"$$ref":"#/components/schemas/ActionType"},"target":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"amp_computer_guid"},"specifiers":{"type":"string","description":"Observable types that can be acted upon.","example":"string"}},"additionalProperties":false,"example":{"type":"amp_computer_guid","specifiers":"string"},"$$ref":"#/components/schemas/TargetType"},"actuator":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"endpoint","enum":["endpoint.sensor","process.network-scanner","network.switch","network.security_manager","process.vulnerability-scanner","network.hub","network.ids","network.firewall","process","network.sense_making","process.sandbox","network.modem","process.email-service","process.dns-server","network.vpn","process.connection-scanner","network.nic","endpoint.printer","network.gateway","process.reputation-service","process.remediation-service","network","process.virtualization-service","network.ips","endpoint.smart-meter","endpoint.digital-telephone-handset","endpoint.workstation","endpoint.server","network.wap","endpoint.laptop","process.aaa-server","process.directory-service","endpoint.pos-terminal","network.bridge","other","process.file-scanner","network.proxy","endpoint","process.location-service","network.sensor","endpoint.smart-phone","network.hips","process.anti-virus-scanner","endpoint.tablet","network.guard","network.router"]},"specifiers":{"type":"array","description":"List of additional properties describing the actuator.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"type":"endpoint","specifiers":["string"]},"$$ref":"#/components/schemas/ActuatorType"},"modifiers":{"type":"object","properties":{"response":{"type":"string","example":"acknowledge","enum":["query","status","acknowledge","command-ref"]},"method":{"type":"array","example":["acl"],"items":{"type":"string","enum":["blackhole","unauthenticated","suspend","graceful","hibernate","whitelist","honeypot","immediate","spawn","blacklist","acl","segmentation","authenticated"]}},"additional_properties":{"required":["context"],"type":"object","properties":{"context":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"context":"string"},"$$ref":"#/components/schemas/AdditionalProperties"},"time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"frequency":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"duration":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"source":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"search":{"type":"string","example":"cve","enum":["vendor_bulletin","patch","signature","cve"]},"option":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"location":{"type":"string","example":"internal","enum":["internal","perimeter"]},"delay":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"destination":{"type":"string","example":"copy-to","enum":["modify-to","set-to","copy-to","move-to","save-to","restore-point","report-to"]}},"additionalProperties":false,"example":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"},"$$ref":"#/components/schemas/ModifierType"}},"additionalProperties":false,"example":{"type":"structured_coa","id":"string","action":{"type":"alert"},"target":{"type":"amp_computer_guid","specifiers":"string"},"actuator":{"type":"endpoint","specifiers":["string"]},"modifiers":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"}},"$$ref":"#/components/schemas/OpenC2COA"},"structured_coa_type":{"type":"string","example":"openc2","enum":["openc2"]},"impact":{"type":"string","description":"Characterizes the estimated impact of applying this course of action.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/COA"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCoas"}},"additionalProperties":false,"$$ref":"#/components/schemas/ModuleObserveBundle"}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleData"}},"errors":{"type":"array","items":{"required":["code","message","module_instance_id","module_type_id","type"],"type":"object","properties":{"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"code":{"type":"string"},"message":{"type":"string"},"type":{"type":"string","enum":["fatal","warning","error"]},"module":{"type":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/ErrorMessage"}}},"additionalProperties":false,"example":{"data":[{"module":"Sample Module","module_instance_id":"da033b3c-81da-4118-b73a-f03feb3adecf","module_type_id":"c84f54db-c187-4cab-8751-2b39b007ee55","data":{"verdicts":{"count":2,"docs":[{"type":"verdict","disposition":2,"observable":{"value":"https://ilo.brenz.pl/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.410Z","end_time":"2023-03-11T13:36:23.410Z"}},{"type":"verdict","disposition":2,"observable":{"value":"http://ilo.brenz.pl/favicon.ico/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.420Z","end_time":"2023-03-11T13:36:23.420Z"}}]}}}]},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundle"}},"application/x-yaml":{"schema":{"type":"object","properties":{"data":{"type":"array","items":{"required":["data","module","module_instance_id","module_type_id"],"type":"object","properties":{"module":{"type":"string"},"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"data":{"type":"object","properties":{"tools":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The kind(s) of tool(s) being described.","example":["credential-exploitation"],"items":{"type":"string"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"tool","enum":["tool"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tool_version":{"type":"string","description":"The version identifier associated with the Tool.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of kill chain phases for which this Tool can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Tool"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataTools"},"indicators":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","producer","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"tags":{"type":"array","description":"Descriptors for this indicator.","example":["string"],"items":{"type":"string"}},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"producer":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","description":"The fixed value indicator","example":"indicator","enum":["indicator"]},"created":{"type":"string","format":"date-time"},"test_mechanisms":{"type":"array","description":"Test Mechanisms effective at identifying the cyber Observables specified in this cyber threat Indicator.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"composite_indicator_expression":{"required":["indicator_ids","operator"],"type":"object","properties":{"operator":{"type":"string","example":"and","enum":["not","or","and"]},"indicator_ids":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"operator":"and","indicator_ids":["string"]},"$$ref":"#/components/schemas/CompositeIndicatorExpression"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"likely_impact":{"type":"string","description":"Likely potential impact within the relevant context if this Indicator were to occur.","example":"string"},"indicator_type":{"type":"array","description":"Specifies the type or types for this Indicator.","example":["Anonymization"],"items":{"type":"string","enum":["File Hash Watchlist","Private Threat Feed","IMEI Watchlist","Malicious E-mail","Exfiltration","C2","URL Watchlist","IMSI Watchlist","Malware Artifacts","Domain Watchlist","Anonymization","Host Characteristics","IP Watchlist","Compromised PKI Certificate","Login Name"]}},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"Relevant kill chain phases indicated by this Indicator.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"negate":{"type":"boolean","description":"Specifies the absence of the pattern.","example":true},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"level of confidence held in the accuracy of this Indicator.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"specification":{"type":"object","example":{},"x-oneOf":[{"required":["judgements","required_judgements","type"],"type":"object","properties":{"type":{"type":"string","example":"Judgement","enum":["Judgement"]},"judgements":{"type":"array","example":["string"],"items":{"type":"string"}},"required_judgements":{"type":"array","example":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}],"items":{"required":["judgement_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"},"$$ref":"#/components/schemas/RelatedJudgement"}}},"additionalProperties":false,"description":"An indicator based on a list of judgements. If any of the Observables in it's judgements are encountered, than it may be matches against. If there are any required judgements, they all must be matched in order for the indicator to be considered a match.","example":{"type":"Judgement","judgements":["string"],"required_judgements":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}]},"$$ref":"#/components/schemas/JudgementSpecification"},{"required":["type","variables"],"type":"object","properties":{"type":{"type":"string","example":"ThreatBrain","enum":["ThreatBrain"]},"query":{"type":"string","example":"string"},"variables":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"description":"An indicator which runs in threatbrain...","example":{"type":"ThreatBrain","query":"string","variables":["string"]},"$$ref":"#/components/schemas/ThreatBrainSpecification"},{"required":["snort_sig","type"],"type":"object","properties":{"type":{"type":"string","example":"Snort","enum":["Snort"]},"snort_sig":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"Snort","snort_sig":"string"},"$$ref":"#/components/schemas/SnortSpecification"},{"required":["SIOC","type"],"type":"object","properties":{"type":{"type":"string","example":"SIOC","enum":["SIOC"]},"SIOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"SIOC","SIOC":"string"},"$$ref":"#/components/schemas/SIOCSpecification"},{"required":["open_IOC","type"],"type":"object","properties":{"type":{"type":"string","example":"OpenIOC","enum":["OpenIOC"]},"open_IOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which contains an XML blob of an openIOC indicator.","example":{"type":"OpenIOC","open_IOC":"string"},"$$ref":"#/components/schemas/OpenIOCSpecification"}]}},"additionalProperties":false,"$$ref":"#/components/schemas/Indicator"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIndicators"},"attack_patterns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"abstraction_level":{"type":"string","description":"The CAPEC abstraction level for patterns describing techniques to attack a system.","example":"aggregate","enum":["detailed","standard","aggregate","meta","category"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"attack-pattern","enum":["attack-pattern"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"x_mitre_platforms":{"type":"array","description":"ATT&CK Technique.Platforms.","example":["string"],"items":{"type":"string"}},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"x_mitre_data_sources":{"type":"array","description":"ATT&CK Technique.Data Sources.","example":["string"],"items":{"type":"string"}},"kill_chain_phases":{"type":"array","description":"A kill chain is a series of steps that an attacker must go through to successfully achieve their objective. The concept was originally developed by the military, but has been adapted to the cybersecurity field to describe the steps an attacker goes through to compromise a target system and achieve their goal.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"x_mitre_contributors":{"type":"array","description":"ATT&CK Technique.Contributors.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/AttackPattern"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataAttackPatterns"},"weaknesses":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Should be short and limited to the key points that define this weakness.","example":"string"},"background_details":{"type":"string","description":"Information that is relevant but not related to the nature of the weakness itself.","example":"string"},"paradigms":{"type":"array","description":"Applicable paradigms.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Paradigm name (Client Server, Mainframe)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Paradigm"}},"abstraction_level":{"type":"string","description":"Refers to the level of abstraction or granularity used to describe the weakness. It helps to categorize the vulnerability based on the level of detail provided.","example":"Base","enum":["Variant","Class","Base","Compound"]},"architectures":{"type":"array","description":"Applicable architectures.","example":[{"prevalence":"Often","name":"string","class":"Embedded"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Architecture name (ARM, x86, ...)","example":"string"},"class":{"type":"string","description":"Class of architecture","example":"Embedded"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Embedded"},"$$ref":"#/components/schemas/Architecture"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"alternate_terms":{"type":"array","description":"Indicates one or more other names used to describe this weakness.","example":[{"term":"string","description":"string"}],"items":{"required":["term"],"type":"object","properties":{"term":{"type":"string","description":"The actual alternate term.","example":"string"},"description":{"type":"string","description":"Provides context for the alternate term by which this weakness may be known.","example":"string"}},"additionalProperties":false,"example":{"term":"string","description":"string"},"$$ref":"#/components/schemas/AlternateTerm"}},"likelihood":{"type":"string","description":"Likelihood of exploit.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","description":"The fixed value weakness","example":"weakness","enum":["weakness"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"functional_areas":{"type":"array","description":"Identifies the functional area of the software in which the weakness is most likely to occur.","example":["Authentication"],"items":{"type":"string"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"modes_of_introduction":{"type":"array","description":"Information about how and when a given weakness may be introduced.","example":[{"phase":"Architecture and Design","note":"string"}],"items":{"required":["phase"],"type":"object","properties":{"phase":{"type":"string","description":"Identifies the point in the software life cycle at which the weakness may be introduced.","example":"Architecture and Design"},"note":{"type":"string","description":"Provides a typical scenario related to introduction during the given phase.","example":"string"}},"additionalProperties":false,"example":{"phase":"Architecture and Design","note":"string"},"$$ref":"#/components/schemas/ModeOfIntroduction"}},"structure":{"type":"string","description":"Defines the structural nature of the weakness.","example":"Chain","enum":["Chain","Simple","Composite"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"notes":{"type":"array","description":"Provides any additional comments about the weakness.","example":[{"content":"","id":"","note_class":"","related_entities":[],"schema_version":"1.3.18","type":"note"}],"items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}},"common_consequences":{"type":"array","description":"Refers to the typical or expected negative effects that can result from exploiting the weakness. This could include anything from unauthorized access to data, denial of service, system crashes or other things.","example":[{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"}],"items":{"required":["scopes"],"type":"object","properties":{"scopes":{"type":"array","description":"Identifies the security property that is violated.","example":["Access Control"],"items":{"type":"string"}},"impacts":{"type":"array","description":"Describes the technical impact that arises if an adversary succeeds in exploiting this weakness.","example":["Alter Execution Logic"],"items":{"type":"string"}},"likelihood":{"type":"string","description":"How likely the specific consequence is expected to be seen relative to the other consequences.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"note":{"type":"string","description":"Additional commentary about a consequence.","example":"string"}},"additionalProperties":false,"example":{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"},"$$ref":"#/components/schemas/Consequence"}},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"detection_methods":{"type":"array","description":"Identifies methods that may be employed to detect this weakness, including their strengths and limitations.","example":[{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"}],"items":{"required":["description","method"],"type":"object","properties":{"method":{"type":"string","description":"Identifies the particular detection method being described.","example":"Architecture or Design Review"},"description":{"type":"string","description":"Provides some context of how this method can be applied to a specific weakness.","example":"string"},"effectiveness":{"type":"string","description":"How effective the detection method may be in detecting the associated weakness.","example":"High"},"effectiveness_notes":{"type":"string","description":"Provides additional discussion of the strengths and shortcomings of this detection method.","example":"string"}},"additionalProperties":false,"example":{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"},"$$ref":"#/components/schemas/DetectionMethod"}},"operating_systems":{"type":"array","description":"Applicable operating systems.","example":[{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"version":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"cpe_id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"class":{"type":"string","description":"Class of Operating System.","example":"Android"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"},"$$ref":"#/components/schemas/OperatingSystem"}},"client_id":{"type":"string"},"affected_resources":{"type":"array","description":"Identifies system resources that can be affected by an exploit of this weakness.","example":["CPU"],"items":{"type":"string"}},"languages":{"type":"array","description":"Applicable Languages.","example":[{"prevalence":"Often","name":"string","class":"Assembly"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Language name (Clojure, Java, ...)","example":"string"},"class":{"type":"string","description":"Class of language.","example":"Assembly"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Assembly"},"$$ref":"#/components/schemas/Language"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"potential_mitigations":{"type":"array","description":"Describes potential mitigations associated with a weakness.","example":[{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"}],"items":{"required":["description"],"type":"object","properties":{"description":{"type":"string","description":"A description of this individual mitigation including any strengths and shortcomings of this mitigation for the weakness.","example":"string"},"phases":{"type":"array","description":"Indicates the development life cycle phase during which this particular mitigation may be applied.","example":["Architecture and Design"],"items":{"type":"string"}},"strategy":{"type":"string","description":"A general strategy for protecting a system to which this mitigation contributes.","example":"Attack Surface Reduction"},"effectiveness":{"type":"string","description":"Summarizes how effective the mitigation may be in preventing the weakness.","example":"Defense in Depth"},"effectiveness_notes":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"}},"additionalProperties":false,"example":{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"},"$$ref":"#/components/schemas/Mitigation"}},"technologies":{"type":"array","description":"Applicable technologies.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Technology name (Web Server, Web Client)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Technology"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Weakness"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataWeaknesses"},"feedbacks":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["entity_id","feedback","id","reason","schema_version","type"],"type":"object","properties":{"feedback":{"type":"integer","format":"int64","example":-1,"enum":[0,1,-1]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"feedback","enum":["feedback"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Feedback"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataFeedbacks"},"verdicts":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["disposition","observable","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"type":{"type":"string","example":"verdict","enum":["verdict"]},"created":{"type":"string","format":"date-time"},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Numeric verdict identifiers.","format":"int64","example":1,"enum":[1,4,3,2,5]},"disposition_name":{"type":"string","description":"The disposition_name field is optional, but is intended to be shown to a user. Applications must therefore remember the mapping of numbers to human words, as in: {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"client_id":{"type":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/Verdict"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVerdicts"},"campaigns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["campaign_type","description","id","schema_version","short_description","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"campaign","enum":["campaign"]},"created":{"type":"string","format":"date-time"},"campaign_type":{"type":"string","description":"String value that describes the type of campaign. For example, a campaign type could be 'Ransomware', 'Advanced Persistent Threat', 'Business Email Compromise', 'Phishing', etc. ","example":"string"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"activity":{"type":"array","description":"Used to capture specific activities or tactics associated with the campaign.\nThe 'activity' field is an array of objects, and each element represents a specific activity and time associated with the campaign. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc. By capturing these activities analysts can identify the specific tactics used by the threat actor(s) behind the campaign.","example":[{"date_time":"2016-01-01T01:01:01.000Z","description":"string"}],"items":{"required":["date_time","description"],"type":"object","properties":{"date_time":{"type":"string","description":"Specifies the date and time at which the activity occured.","format":"date-time","example":"2016-01-01T01:01:01Z"},"description":{"type":"string","description":"A description of the activity.","example":"string"}},"additionalProperties":false,"description":"Captures the specific activities or tactics associated with the entity. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc.","example":{"date_time":"2016-01-01T01:01:01.000Z","description":"string"},"$$ref":"#/components/schemas/Activity"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"array","description":"Characterizes the intended effect of this cyber threat campaign.","example":["Account Takeover"],"items":{"type":"string"}},"status":{"type":"string","description":"Indicates current Status of the Campaign. \n\nCan have one of the following values: \n\n- Ongoing: Indicates that the campaign is currently active and ongoing. For example, a mass phishing campaign that is actively targeting users is considered 'ongoing'.\n\n- Historic: Campaign has already occurred and is now in the past.\n\n- Future: This indicates that a campaign is planned or expected to occur in the future. For example, a threat actor may announce their intention to launch a specific cyberattack campaign at a future date.","example":"Future","enum":["Historic","Future","Ongoing"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Level of confidence held in the characterization of this Campaign.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"names":{"type":"array","description":"Used to capture alternate names or aliases associated with the campaign. A cyberattack campaign may have multiple names or aliases depending on the group or actor(s) behind the attack, e.g., 'Wannacry' is also known as 'WannaCrypt', 'WCry', 'Wanna Decryptor', etc.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Campaign"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCampaigns"},"actors":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","source","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"motivation":{"type":"string","description":"The reason or purpose behind the malicious activity attributed to this Actor. By understanding a threat actor's motivation, analysts can better predict the attacker's behavior and anticipate future malicious actions.","example":"Ego"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["description","related_identities"],"type":"object","properties":{"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"related_identities":{"type":"array","description":"Identifies other entity Identities related to this Identity.","example":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}],"items":{"required":["identity"],"type":"object","properties":{"identity":{"type":"string","description":"The reference (URI) of the related Identity object.","example":"string"},"confidence":{"type":"string","description":"Specifies the level of confidence in the assertion of the relationship between the two objects.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"information_source":{"type":"string","description":"Specifies the source of the information about the relationship between the two components.","example":"string"},"relationship":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes a related Identity","example":{"identity":"string","confidence":"High","information_source":"string","relationship":"string"},"$$ref":"#/components/schemas/RelatedIdentity"}}},"additionalProperties":false,"description":"Can contain information such as the name of the attacker, the group or organization they belong to, or any other identifier that can help in the attribution process.","example":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"$$ref":"#/components/schemas/Identity"},"sophistication":{"type":"string","description":"Represents the level of expertise and skill that the threat actor has displayed in their malicious activities. Can help security analysts assess the potential impact of an attacker's TTPs and determine the potential attack surface. \n\nFor example, a threat actor with a low sophistication level may primarily rely on off-the-shelf malware and attack tools, while an attacker with high sophistication may use custom tools with advanced evasion techniques, zero-day exploits, and sophisticated methods for command and control of their malware. \n\nThe sophistication level of an attacker can also be inferred based on several factors such as the complexity of attacks, the attacker's knowledge of the targeted organization's systems, and the attacker's ability to remain undetected.\n\nIf an attacker shows a high level of sophistication in reconnaissances, social engineering, and phishing, then the attacker may have a good knowledge of the targeted organization and its employees. This means that the attacker may be more successful in infiltrating the organization's network and compromising its systems.","example":"Aspirant","enum":["Aspirant","Innovator","Practitioner","Novice","Expert"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"planning_and_operational_support":{"type":"string","description":"Provides information about the resources and capabilities of the attacker that could be used to assist in planning and operations related to the threat.\n\n It can be used to describe Infrastructure, Tools, Techniques, and Capabilities used by the threat actor.","example":"string"},"type":{"type":"string","example":"actor","enum":["actor"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Represents the desired outcome or impact the threat actor is trying to achieve through their malicious activities. \n\n Helps security analysts to understand the attacker's goals beyond the immediate impact of the attack. By understanding the intended effect, analysts can draw connections between seemingly unrelated attacks and build a more complete understanding of an attacker's long-term goals and motivations.","example":"Account Takeover"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"aliases":{"type":"array","description":"A list of other names that this Threat Actor is believed to use.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"This field can help analysts decide how much trust they can put in the information provided by the threat intelligence sources.\n\nFor example, an Actor entity can have high confidence if the organization's security researchers have been tracking it for a long time and have gathered a significant amount of intelligence about it through various sources, such as analysis of malware, network traffic, and human intelligence. In contrast, low confidence may indicate the organization has only seen limited or circumstantial evidence.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Actor"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataActors"},"data_tables":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["columns","id","rows","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"columns":{"type":"array","description":"An ordered list of column definitions.","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"type":{"type":"string","example":"data-table","enum":["data-table"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"rows":{"type":"array","description":"An ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/DataTable"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataDataTables"},"notes":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataNotes"},"identity_assertions":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["assertions","id","identity","schema_version","type"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["observables"],"type":"object","properties":{"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"additionalProperties":false,"description":"Attributes for which the assertion is being made.","example":{"observables":[{"value":"1.2.3.4","type":"ip"}]},"$$ref":"#/components/schemas/IdentityCoordinates"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"identity-assertion","enum":["identity-assertion"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"assertions":{"type":"array","description":"Any known context about the identity attributes.","example":[{"name":"cisco:ctr:ad:host_domain_name","value":"string"}],"items":{"required":["name","value"],"type":"object","properties":{"name":{"type":"string","description":"An open vocabulary containing well known assertion types","example":"cisco:ctr:ad:host_domain_name"},"value":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"cisco:ctr:ad:host_domain_name","value":"string"},"$$ref":"#/components/schemas/Assertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/IdentityAssertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIdentityAssertions"},"judgements":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","disposition","disposition_name","id","observable","priority","schema_version","severity","source","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"reason_uri":{"type":"string","description":"A URI","example":"string"},"type":{"type":"string","example":"judgement","enum":["judgement"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Matches :disposition_name as in {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","format":"int64","example":1,"enum":[1,4,3,2,5]},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"disposition_name":{"type":"string","description":"String verdict identifiers.","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"priority":{"type":"integer","description":"A value 0-100 that determine the priority of a judgement. Curated feeds of black/white lists, for example known good products within your organizations, should use a 95. All automated systems should use a priority of 90, or less. Human judgements should have a priority of 100, so that humans can always override machines.","format":"int64","example":10},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]}},"additionalProperties":false,"$$ref":"#/components/schemas/Judgement"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataJudgements"},"malwares":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The type of malware being described.","example":["adware"],"items":{"type":"string"}},"abstraction_level":{"type":"string","description":"Malware abstraction level.","example":"family","enum":["family","version","variant"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"malware","enum":["malware"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of Kill Chain Phases for which this Malware can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Malware"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataMalwares"},"incidents":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","id","incident_time","schema_version","status","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"assignees":{"type":"array","description":"A set of owners assigned to this incident.","example":["string"],"items":{"type":"string"}},"meta":{"type":"object","additionalProperties":{"type":"object","description":"custom field relevant to attach meta data to.","example":{},"x-oneOf":[{"example":"string","type":"string"},{"example":10,"type":"number","format":"double"},{"example":"2016-01-01T01:01:01.000Z","type":"string","format":"date-time"},{"example":"keyword","type":"string"},{"example":true,"type":"boolean"}]},"description":"metadata associated to the incident.","example":{"keyword":{}},"$$ref":"#/components/schemas/MetaData"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"incident","enum":["incident"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"incident_time":{"required":["opened"],"type":"object","properties":{"opened":{"type":"string","description":"Time the incident was first opened.","format":"date-time","example":"2016-01-01T01:01:01Z"},"discovered":{"type":"string","description":"Time the incident was first discovered.","format":"date-time","example":"2016-01-01T01:01:01Z"},"reported":{"type":"string","description":"Time the incident was first reported.","format":"date-time","example":"2016-01-01T01:01:01Z"},"remediated":{"type":"string","description":"Time that the remediation of the damage from the incident was completed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"closed":{"type":"string","description":"Time that the incident was last closed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"rejected":{"type":"string","description":"Time that the incident was first rejected.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Relevant time values associated with this Incident.","example":{"opened":"2016-01-01T01:01:01.000Z","discovered":"2016-01-01T01:01:01.000Z","reported":"2016-01-01T01:01:01.000Z","remediated":"2016-01-01T01:01:01.000Z","closed":"2016-01-01T01:01:01.000Z","rejected":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/IncidentTime"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"discovery_method":{"type":"string","description":"Identifies how the incident was discovered.","example":"Agent Disclosure"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Specifies the suspected intended effect of this incident","example":"Account Takeover"},"categories":{"type":"array","description":"A set of categories for this incident.","example":["Attrition"],"items":{"type":"string"}},"status":{"type":"string","description":"The `status` field represents the current state of an incident within the incident management process. Its values help in tracking and reporting the progress of the incident from its discovery to its resolution.","example":"Closed","enum":["New","Closed","Open: Recovered","Closed: Other","Hold: Internal","Hold: Legal","Closed: Under Review","Rejected","Open","Restoration Achieved","Incident Reported","Closed: Suspected","Stalled","Open: Contained","Closed: Near-Miss","Hold: External","Containment Achieved","New: Processing","Closed: Confirmed Threat","Closed: False Positive","Open: Reported","Open: Investigating","Hold","New: Presented"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"promotion_method":{"type":"string","description":"Describes method for promoting an Incident, whether manually or automatically. An Incident may be created manually by a SOAR analyst or SOC operator, or through an automated correlation or aggregation rule or engine that matches a specific set of events or alerts, and promotes them to Incident(s).","example":"Automated","enum":["Automated","Manual"]},"severity":{"type":"string","description":"Represents the potential impact of an incident on an organization's security posture and business operations. It helps organizations prioritize and allocate resources for incident response based on the severity level of the incident \nIt helps analysts and incident handlers prioritize incidents by indicating the level of risk and potential impact associated with the incident. This enables organizations to allocate resources efficiently and address the most critical incidents first.\nCan also be used to generate reports and metrics for measuring the effectiveness of the incident response process and to identify trends and patterns in the threat landscape.\nIt is important to note that the `severity` field is subjective and can be interpreted differently by different organizations or analysts. Therefore, it should be used in conjunction with other intelligence attributes, such as the `confidence` field, to provide a more comprehensive view of the incident.","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"scores":{"type":"object","additionalProperties":{"type":"number","description":"Field is used to indicate the severity or impact of the threat represented by the incident.\nIt's an open-type dictionary object with score types and numeric value of the score.\n\nFor example, systems can have the following score types:\n\n- `asset` - assesses the potential damage or harm that the threat can cause to the affected asset(s). The scale ranges from 0 to 10, with 10 indicating the highest potential harm. \n\n- `global` - assesses the overall impact or significance of the threat to the organization or wider community. The scale ranges from 0 to 1000, with 1000 indicating the highest impact.\n\n- `ttp` - a measure of the threat actor's proficiency in utilizing TTPs. Typically, ranges from 0-100, with a higher score indicating a greater threat or concern.","format":"double","example":10},"description":"Used to indicate the severity or impact score of the threat represented by the incident.","example":{"asset":10},"$$ref":"#/components/schemas/IncidentScores"},"client_id":{"type":"string"},"techniques":{"type":"array","description":"Represents the specific methods or actions used by an attacker to carry out an offensive maneuver or achieve their goals.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Represents the level of certainty or trustworthiness associated with the incident. It denotes the reliability of the intelligence associated with the incident.\nThe `confidence` field can take on several values, including:\n- `info`: Indicates that the incident information is based on sources with no previous track record or there is no track record for the source reporting the incident.\n- `low`: Indicates that the incident information is based on sources with a questionable track record or there is limited information about the accuracy of the source.\n- `medium`: Indicates that the incident information is based on sources with a mixed track record or of uncertain reliability.\n- `high`: Indicates that the incident information is based on sources with a proven track record and high degree of reliability.\nThe `confidence` field can be used to indicate the level of trust and confidence that can be attributed to the incident, and it may impact how the incident is prioritized, analyzed and addressed. It can also help in the decision-making process associated with the incident response activities.\nIt is important to note that the `confidence` field is subjective and can be interpreted differently by different organizations or analysts. As such, it is often used in conjunction with other intelligence attributes, such as the `severity` field, to provide a more complete picture of the incident.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"tactics":{"type":"array","description":"Represents the offensive techniques, approaches, or procedures that an adversary may use to achieve their objectives during an attack. It helps in understanding the intent and capabilities of the adversary and can be used to identify indicators of attack (IoAs) or indicators of compromise (IoCs) that are associated with the adversary's tactics.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Incident"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIncidents"},"sightings":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","count","id","observed_time","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"relations":{"type":"array","description":"Provide any context we can about where the observable came from.","example":[{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}}],"items":{"required":["origin","related","relation","source"],"type":"object","properties":{"origin":{"type":"string","example":"string"},"origin_uri":{"type":"string","description":"A URI","example":"string"},"relation":{"type":"string","example":"Allocated"},"relation_info":{"type":"object","additionalProperties":{"type":"object","example":{}},"example":{"keyword":{}},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightingsDocsRelationsRelationInfo"},"source":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"related":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"additionalProperties":false,"description":"A relation inside a Sighting.","example":{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}},"$$ref":"#/components/schemas/ObservedRelation"}},"sensor_coordinates":{"required":["observables","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the device that made the sighting (sensor) and contains identifying observables for the sensor.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"os":"string"},"$$ref":"#/components/schemas/SensorCoordinates"},"observables":{"type":"array","description":"The object(s) of interest.","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"type":{"type":"string","example":"sighting","enum":["sighting"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"targets":{"type":"array","description":"May include one or more targets that observed the associated indicator. Targets can include network devices, host devices, or other entities that are capable of detecting indicators of compromise.\n\nCan be used to assess the scope of potential threats, helping analysts understand which devices or components of the network may be vulnerable to attack. For example, if a particular malware strain is detected on several different systems within an organization, the `targets` field may indicate which systems are affected and which may need to be isolated or patched to prevent further spread.","example":[{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"}],"items":{"required":["observables","observed_time","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the target of the sighting and contains identifying observables for the target.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"},"$$ref":"#/components/schemas/IdentitySpecification"}},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"resolution":{"type":"string","description":"Represents the disposition or actions taken on the associated threat intelligence.","example":"detected"},"internal":{"type":"boolean","description":"If `true`, indicates that the sighting was reported from internal sources, such as an organization's own internal security tools or SOC.\n Internal sightings are often considered more reliable and actionable than external sightings, which are reported from external sources and may have a lower level of trustworthiness. Internal sightings can provide more context and can help identify potential threats that are unique to a particular environment or organization.\n Internal sightings can also help organizations prioritize their security response efforts by identifying threats that are specific to their environment and may not yet be widely known.","example":false},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"count":{"type":"integer","description":"The number of times an indicator was observed within a certain period of time.\nFor example, if an IP address associated with known malicious activity is observed once within a period of time, it may indicate a low-level threat. However, if the same IP address is observed multiple times within a short time frame, it may indicate a more severe and persistent threat.\nIt can also be used to prioritize security alerts and indicate the urgency of a response. High counts indicate that an indicator is actively being used in a larger campaign, while low counts may indicate isolated incidents.","format":"int64","example":10},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"context":{"type":"object","properties":{"http_events":{"type":"array","description":"a list of `HTTPType`","example":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"items":{"required":["host","process_id","process_name","time","traffic","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"method":{"type":"string","example":"CONNECT","enum":["OPTIONS","PATCH","TRACE","HEAD","POST","CONNECT","GET","PUT"]},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"HTTPEvent","enum":["HTTPEvent"]},"host":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"query":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"encrypted":{"type":"boolean","example":true},"url_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10},"$$ref":"#/components/schemas/HTTPType"}},"process_create_events":{"type":"array","description":"a list of `ProcessCreate`","example":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"items":{"required":["process_id","process_name","time","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"parent_process_guid":{"type":"integer","format":"int64","example":10},"process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_size":{"type":"integer","format":"int64","example":10},"process_size":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"ProcessCreateEvent","enum":["ProcessCreateEvent"]},"parent_process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_creation_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"},"$$ref":"#/components/schemas/ProcessCreateType"}},"registry_delete_events":{"type":"array","description":"a list of `RegistryDeleteType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryDeleteEvent","enum":["RegistryDeleteEvent"]},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"},"$$ref":"#/components/schemas/RegistryDeleteType"}},"file_modify_events":{"type":"array","description":"a list of `FileModifyType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileModifyEvent","enum":["FileModifyEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileModifyType"}},"registry_set_events":{"type":"array","description":"a list of `RegistrySetType`","example":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_value","time","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"registry_data":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"RegistrySetEvent","enum":["RegistrySetEvent"]},"registry_data_length":{"type":"integer","format":"int64","example":10},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"},"$$ref":"#/components/schemas/RegistrySetType"}},"file_create_events":{"type":"array","description":"a list of `FileCreateType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileCreateEvent","enum":["FileCreateEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileCreateType"}},"registry_create_events":{"type":"array","description":"a list of `RegistryCreateType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryCreateEvent","enum":["RegistryCreateEvent"]}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"},"$$ref":"#/components/schemas/RegistryCreateType"}},"library_load_events":{"type":"array","description":"a list of `LibraryLoadType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"items":{"required":["dll_library_name","dll_library_path","process_id","process_name","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"LibraryLoadEvent","enum":["LibraryLoadEvent"]},"dll_library_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"dll_library_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"},"$$ref":"#/components/schemas/LibraryLoadType"}},"file_move_events":{"type":"array","description":"a list of `FileMoveType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"items":{"required":["file_name","file_path","new_name","old_name","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileMoveEvent","enum":["FileMoveEvent"]},"old_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"new_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"},"$$ref":"#/components/schemas/FileMoveType"}},"file_delete_events":{"type":"array","description":"a list of `FileDeleteType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileDeleteEvent","enum":["FileDeleteEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileDeleteType"}},"netflow_events":{"type":"array","description":"a list of `NetflowType`","example":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"items":{"required":["process_id","process_name","time","traffic","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_in":{"type":"integer","format":"int64","example":10},"process_guid":{"type":"integer","format":"int64","example":10},"process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"flow_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"NetflowEvent","enum":["NetflowEvent"]},"process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_out":{"type":"integer","format":"int64","example":10},"process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"},"$$ref":"#/components/schemas/NetflowType"}},"registry_rename_events":{"type":"array","description":"a list of `RegistryRenameType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_old_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryRenameEvent","enum":["RegistryRenameEvent"]},"registry_old_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"},"$$ref":"#/components/schemas/RegistryRenameType"}}},"additionalProperties":false,"description":"Context including the event type that best fits the type of the sighting.","example":{"http_events":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"process_create_events":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"registry_delete_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"file_modify_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_set_events":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"file_create_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_create_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"library_load_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"file_move_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"file_delete_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"netflow_events":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"registry_rename_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}]},"$$ref":"#/components/schemas/Context"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"sensor":{"type":"string","description":"The OpenC2 Actuator name that best fits the device that is creating this sighting (e.g. network.firewall)","example":"endpoint"},"data":{"required":["columns","rows"],"type":"object","properties":{"columns":{"type":"array","description":"an ordered list of column definitions","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"rows":{"type":"array","description":"an ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10}},"additionalProperties":false,"description":"An embedded data table for the Sighting.","example":{"columns":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"rows":[[{}]],"row_count":10},"$$ref":"#/components/schemas/SightingDataTable"}},"additionalProperties":false,"$$ref":"#/components/schemas/Sighting"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightings"},"relationships":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","relationship_type","schema_version","source_ref","target_ref","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"target_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"type":{"type":"string","example":"relationship","enum":["relationship"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"source_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"relationship_type":{"type":"string","example":"attributed-to"}},"additionalProperties":false,"$$ref":"#/components/schemas/Relationship"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataRelationships"},"vulnerabilities":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Various sources of vulnerability information can be used, including third-party resources like the National Vulnerability Database (NVD) and the Common Vulnerabilities and Exposures (CVE) database. The platform then analyzes this data and provides the user with relevant details such as the severity of the vulnerability, the affected systems, and remediation recommendations. \n\n Based on this information, the user can prioritize patching and other mitigation strategies to reduce the risk of potential attacks.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"}},"additionalProperties":false,"$$ref":"#/components/schemas/Vulnerability"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVulnerabilities"},"coas":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"stage":{"type":"string","description":"Specifies what stage in the cyber threat management lifecycle this Course Of Action is relevant to.","example":"Containment","enum":["Identification","Lessons Learned","Remedy","Preparation","Containment","Response","Eradication","Recovery"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"efficacy":{"type":"string","description":"Effectiveness of this course of action in achieving its targeted objective.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","example":"coa","enum":["coa"]},"created":{"type":"string","format":"date-time"},"related_COAs":{"type":"array","description":"Identifies or characterizes relationships to one or more related courses of action.","example":[{"confidence":"High","source":"string","relationship":"string","COA_id":"string"}],"items":{"required":["COA_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"COA_id":{"type":"string","description":"A URI leading to a COA.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","COA_id":"string"},"$$ref":"#/components/schemas/RelatedCOA"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"coa_type":{"type":"string","description":"The type of this COA","example":"Diplomatic Actions","enum":["Diplomatic Actions","Physical Access Restrictions","Policy Actions","Internal Blocking","Playbook","Redirection","Phase","Eradication","Public Disclosure","Monitoring","Patching","Logical Access Restrictions","Redirection (Honey Pot)","Rebuilding","Perimeter Blocking","Hardening","Other","Training","Task"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"objective":{"type":"array","description":"Characterizes the objective to provide guidance on how to mitigate a security incident that has been identified.","example":["string"],"items":{"type":"string"}},"cost":{"type":"string","description":"Characterizes the estimated cost for applying this course of action.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"open_c2_coa":{"required":["action","type"],"type":"object","properties":{"type":{"type":"string","example":"structured_coa","enum":["structured_coa"]},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"action":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"alert","enum":["stop","save","delete","remediate","redirect","alert","query","augment","snapshot","update","allow","scan","investigate","modify","sync","start","pause","deny","substitute","distill","move","restart","other","detonate","response","set","notify","report","restore","get","throttle","mitigate","resume","locate","contain"]}},"additionalProperties":false,"example":{"type":"alert"},"$$ref":"#/components/schemas/ActionType"},"target":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"amp_computer_guid"},"specifiers":{"type":"string","description":"Observable types that can be acted upon.","example":"string"}},"additionalProperties":false,"example":{"type":"amp_computer_guid","specifiers":"string"},"$$ref":"#/components/schemas/TargetType"},"actuator":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"endpoint","enum":["endpoint.sensor","process.network-scanner","network.switch","network.security_manager","process.vulnerability-scanner","network.hub","network.ids","network.firewall","process","network.sense_making","process.sandbox","network.modem","process.email-service","process.dns-server","network.vpn","process.connection-scanner","network.nic","endpoint.printer","network.gateway","process.reputation-service","process.remediation-service","network","process.virtualization-service","network.ips","endpoint.smart-meter","endpoint.digital-telephone-handset","endpoint.workstation","endpoint.server","network.wap","endpoint.laptop","process.aaa-server","process.directory-service","endpoint.pos-terminal","network.bridge","other","process.file-scanner","network.proxy","endpoint","process.location-service","network.sensor","endpoint.smart-phone","network.hips","process.anti-virus-scanner","endpoint.tablet","network.guard","network.router"]},"specifiers":{"type":"array","description":"List of additional properties describing the actuator.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"type":"endpoint","specifiers":["string"]},"$$ref":"#/components/schemas/ActuatorType"},"modifiers":{"type":"object","properties":{"response":{"type":"string","example":"acknowledge","enum":["query","status","acknowledge","command-ref"]},"method":{"type":"array","example":["acl"],"items":{"type":"string","enum":["blackhole","unauthenticated","suspend","graceful","hibernate","whitelist","honeypot","immediate","spawn","blacklist","acl","segmentation","authenticated"]}},"additional_properties":{"required":["context"],"type":"object","properties":{"context":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"context":"string"},"$$ref":"#/components/schemas/AdditionalProperties"},"time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"frequency":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"duration":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"source":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"search":{"type":"string","example":"cve","enum":["vendor_bulletin","patch","signature","cve"]},"option":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"location":{"type":"string","example":"internal","enum":["internal","perimeter"]},"delay":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"destination":{"type":"string","example":"copy-to","enum":["modify-to","set-to","copy-to","move-to","save-to","restore-point","report-to"]}},"additionalProperties":false,"example":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"},"$$ref":"#/components/schemas/ModifierType"}},"additionalProperties":false,"example":{"type":"structured_coa","id":"string","action":{"type":"alert"},"target":{"type":"amp_computer_guid","specifiers":"string"},"actuator":{"type":"endpoint","specifiers":["string"]},"modifiers":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"}},"$$ref":"#/components/schemas/OpenC2COA"},"structured_coa_type":{"type":"string","example":"openc2","enum":["openc2"]},"impact":{"type":"string","description":"Characterizes the estimated impact of applying this course of action.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/COA"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCoas"}},"additionalProperties":false,"$$ref":"#/components/schemas/ModuleObserveBundle"}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleData"}},"errors":{"type":"array","items":{"required":["code","message","module_instance_id","module_type_id","type"],"type":"object","properties":{"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"code":{"type":"string"},"message":{"type":"string"},"type":{"type":"string","enum":["fatal","warning","error"]},"module":{"type":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/ErrorMessage"}}},"additionalProperties":false,"example":{"data":[{"module":"Sample Module","module_instance_id":"da033b3c-81da-4118-b73a-f03feb3adecf","module_type_id":"c84f54db-c187-4cab-8751-2b39b007ee55","data":{"verdicts":{"count":2,"docs":[{"type":"verdict","disposition":2,"observable":{"value":"https://ilo.brenz.pl/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.410Z","end_time":"2023-03-11T13:36:23.410Z"}},{"type":"verdict","disposition":2,"observable":{"value":"http://ilo.brenz.pl/favicon.ico/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.420Z","end_time":"2023-03-11T13:36:23.420Z"}}]}}}]},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundle"}},"application/edn":{"schema":{"type":"object","properties":{"data":{"type":"array","items":{"required":["data","module","module_instance_id","module_type_id"],"type":"object","properties":{"module":{"type":"string"},"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"data":{"type":"object","properties":{"tools":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The kind(s) of tool(s) being described.","example":["credential-exploitation"],"items":{"type":"string"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"tool","enum":["tool"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tool_version":{"type":"string","description":"The version identifier associated with the Tool.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of kill chain phases for which this Tool can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Tool"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataTools"},"indicators":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","producer","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"tags":{"type":"array","description":"Descriptors for this indicator.","example":["string"],"items":{"type":"string"}},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"producer":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","description":"The fixed value indicator","example":"indicator","enum":["indicator"]},"created":{"type":"string","format":"date-time"},"test_mechanisms":{"type":"array","description":"Test Mechanisms effective at identifying the cyber Observables specified in this cyber threat Indicator.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"composite_indicator_expression":{"required":["indicator_ids","operator"],"type":"object","properties":{"operator":{"type":"string","example":"and","enum":["not","or","and"]},"indicator_ids":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"operator":"and","indicator_ids":["string"]},"$$ref":"#/components/schemas/CompositeIndicatorExpression"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"likely_impact":{"type":"string","description":"Likely potential impact within the relevant context if this Indicator were to occur.","example":"string"},"indicator_type":{"type":"array","description":"Specifies the type or types for this Indicator.","example":["Anonymization"],"items":{"type":"string","enum":["File Hash Watchlist","Private Threat Feed","IMEI Watchlist","Malicious E-mail","Exfiltration","C2","URL Watchlist","IMSI Watchlist","Malware Artifacts","Domain Watchlist","Anonymization","Host Characteristics","IP Watchlist","Compromised PKI Certificate","Login Name"]}},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"Relevant kill chain phases indicated by this Indicator.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"negate":{"type":"boolean","description":"Specifies the absence of the pattern.","example":true},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"level of confidence held in the accuracy of this Indicator.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"specification":{"type":"object","example":{},"x-oneOf":[{"required":["judgements","required_judgements","type"],"type":"object","properties":{"type":{"type":"string","example":"Judgement","enum":["Judgement"]},"judgements":{"type":"array","example":["string"],"items":{"type":"string"}},"required_judgements":{"type":"array","example":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}],"items":{"required":["judgement_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"},"$$ref":"#/components/schemas/RelatedJudgement"}}},"additionalProperties":false,"description":"An indicator based on a list of judgements. If any of the Observables in it's judgements are encountered, than it may be matches against. If there are any required judgements, they all must be matched in order for the indicator to be considered a match.","example":{"type":"Judgement","judgements":["string"],"required_judgements":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}]},"$$ref":"#/components/schemas/JudgementSpecification"},{"required":["type","variables"],"type":"object","properties":{"type":{"type":"string","example":"ThreatBrain","enum":["ThreatBrain"]},"query":{"type":"string","example":"string"},"variables":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"description":"An indicator which runs in threatbrain...","example":{"type":"ThreatBrain","query":"string","variables":["string"]},"$$ref":"#/components/schemas/ThreatBrainSpecification"},{"required":["snort_sig","type"],"type":"object","properties":{"type":{"type":"string","example":"Snort","enum":["Snort"]},"snort_sig":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"Snort","snort_sig":"string"},"$$ref":"#/components/schemas/SnortSpecification"},{"required":["SIOC","type"],"type":"object","properties":{"type":{"type":"string","example":"SIOC","enum":["SIOC"]},"SIOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"SIOC","SIOC":"string"},"$$ref":"#/components/schemas/SIOCSpecification"},{"required":["open_IOC","type"],"type":"object","properties":{"type":{"type":"string","example":"OpenIOC","enum":["OpenIOC"]},"open_IOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which contains an XML blob of an openIOC indicator.","example":{"type":"OpenIOC","open_IOC":"string"},"$$ref":"#/components/schemas/OpenIOCSpecification"}]}},"additionalProperties":false,"$$ref":"#/components/schemas/Indicator"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIndicators"},"attack_patterns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"abstraction_level":{"type":"string","description":"The CAPEC abstraction level for patterns describing techniques to attack a system.","example":"aggregate","enum":["detailed","standard","aggregate","meta","category"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"attack-pattern","enum":["attack-pattern"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"x_mitre_platforms":{"type":"array","description":"ATT&CK Technique.Platforms.","example":["string"],"items":{"type":"string"}},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"x_mitre_data_sources":{"type":"array","description":"ATT&CK Technique.Data Sources.","example":["string"],"items":{"type":"string"}},"kill_chain_phases":{"type":"array","description":"A kill chain is a series of steps that an attacker must go through to successfully achieve their objective. The concept was originally developed by the military, but has been adapted to the cybersecurity field to describe the steps an attacker goes through to compromise a target system and achieve their goal.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"x_mitre_contributors":{"type":"array","description":"ATT&CK Technique.Contributors.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/AttackPattern"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataAttackPatterns"},"weaknesses":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Should be short and limited to the key points that define this weakness.","example":"string"},"background_details":{"type":"string","description":"Information that is relevant but not related to the nature of the weakness itself.","example":"string"},"paradigms":{"type":"array","description":"Applicable paradigms.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Paradigm name (Client Server, Mainframe)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Paradigm"}},"abstraction_level":{"type":"string","description":"Refers to the level of abstraction or granularity used to describe the weakness. It helps to categorize the vulnerability based on the level of detail provided.","example":"Base","enum":["Variant","Class","Base","Compound"]},"architectures":{"type":"array","description":"Applicable architectures.","example":[{"prevalence":"Often","name":"string","class":"Embedded"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Architecture name (ARM, x86, ...)","example":"string"},"class":{"type":"string","description":"Class of architecture","example":"Embedded"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Embedded"},"$$ref":"#/components/schemas/Architecture"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"alternate_terms":{"type":"array","description":"Indicates one or more other names used to describe this weakness.","example":[{"term":"string","description":"string"}],"items":{"required":["term"],"type":"object","properties":{"term":{"type":"string","description":"The actual alternate term.","example":"string"},"description":{"type":"string","description":"Provides context for the alternate term by which this weakness may be known.","example":"string"}},"additionalProperties":false,"example":{"term":"string","description":"string"},"$$ref":"#/components/schemas/AlternateTerm"}},"likelihood":{"type":"string","description":"Likelihood of exploit.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","description":"The fixed value weakness","example":"weakness","enum":["weakness"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"functional_areas":{"type":"array","description":"Identifies the functional area of the software in which the weakness is most likely to occur.","example":["Authentication"],"items":{"type":"string"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"modes_of_introduction":{"type":"array","description":"Information about how and when a given weakness may be introduced.","example":[{"phase":"Architecture and Design","note":"string"}],"items":{"required":["phase"],"type":"object","properties":{"phase":{"type":"string","description":"Identifies the point in the software life cycle at which the weakness may be introduced.","example":"Architecture and Design"},"note":{"type":"string","description":"Provides a typical scenario related to introduction during the given phase.","example":"string"}},"additionalProperties":false,"example":{"phase":"Architecture and Design","note":"string"},"$$ref":"#/components/schemas/ModeOfIntroduction"}},"structure":{"type":"string","description":"Defines the structural nature of the weakness.","example":"Chain","enum":["Chain","Simple","Composite"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"notes":{"type":"array","description":"Provides any additional comments about the weakness.","example":[{"content":"","id":"","note_class":"","related_entities":[],"schema_version":"1.3.18","type":"note"}],"items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}},"common_consequences":{"type":"array","description":"Refers to the typical or expected negative effects that can result from exploiting the weakness. This could include anything from unauthorized access to data, denial of service, system crashes or other things.","example":[{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"}],"items":{"required":["scopes"],"type":"object","properties":{"scopes":{"type":"array","description":"Identifies the security property that is violated.","example":["Access Control"],"items":{"type":"string"}},"impacts":{"type":"array","description":"Describes the technical impact that arises if an adversary succeeds in exploiting this weakness.","example":["Alter Execution Logic"],"items":{"type":"string"}},"likelihood":{"type":"string","description":"How likely the specific consequence is expected to be seen relative to the other consequences.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"note":{"type":"string","description":"Additional commentary about a consequence.","example":"string"}},"additionalProperties":false,"example":{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"},"$$ref":"#/components/schemas/Consequence"}},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"detection_methods":{"type":"array","description":"Identifies methods that may be employed to detect this weakness, including their strengths and limitations.","example":[{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"}],"items":{"required":["description","method"],"type":"object","properties":{"method":{"type":"string","description":"Identifies the particular detection method being described.","example":"Architecture or Design Review"},"description":{"type":"string","description":"Provides some context of how this method can be applied to a specific weakness.","example":"string"},"effectiveness":{"type":"string","description":"How effective the detection method may be in detecting the associated weakness.","example":"High"},"effectiveness_notes":{"type":"string","description":"Provides additional discussion of the strengths and shortcomings of this detection method.","example":"string"}},"additionalProperties":false,"example":{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"},"$$ref":"#/components/schemas/DetectionMethod"}},"operating_systems":{"type":"array","description":"Applicable operating systems.","example":[{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"version":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"cpe_id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"class":{"type":"string","description":"Class of Operating System.","example":"Android"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"},"$$ref":"#/components/schemas/OperatingSystem"}},"client_id":{"type":"string"},"affected_resources":{"type":"array","description":"Identifies system resources that can be affected by an exploit of this weakness.","example":["CPU"],"items":{"type":"string"}},"languages":{"type":"array","description":"Applicable Languages.","example":[{"prevalence":"Often","name":"string","class":"Assembly"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Language name (Clojure, Java, ...)","example":"string"},"class":{"type":"string","description":"Class of language.","example":"Assembly"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Assembly"},"$$ref":"#/components/schemas/Language"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"potential_mitigations":{"type":"array","description":"Describes potential mitigations associated with a weakness.","example":[{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"}],"items":{"required":["description"],"type":"object","properties":{"description":{"type":"string","description":"A description of this individual mitigation including any strengths and shortcomings of this mitigation for the weakness.","example":"string"},"phases":{"type":"array","description":"Indicates the development life cycle phase during which this particular mitigation may be applied.","example":["Architecture and Design"],"items":{"type":"string"}},"strategy":{"type":"string","description":"A general strategy for protecting a system to which this mitigation contributes.","example":"Attack Surface Reduction"},"effectiveness":{"type":"string","description":"Summarizes how effective the mitigation may be in preventing the weakness.","example":"Defense in Depth"},"effectiveness_notes":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"}},"additionalProperties":false,"example":{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"},"$$ref":"#/components/schemas/Mitigation"}},"technologies":{"type":"array","description":"Applicable technologies.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Technology name (Web Server, Web Client)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Technology"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Weakness"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataWeaknesses"},"feedbacks":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["entity_id","feedback","id","reason","schema_version","type"],"type":"object","properties":{"feedback":{"type":"integer","format":"int64","example":-1,"enum":[0,1,-1]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"feedback","enum":["feedback"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Feedback"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataFeedbacks"},"verdicts":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["disposition","observable","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"type":{"type":"string","example":"verdict","enum":["verdict"]},"created":{"type":"string","format":"date-time"},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Numeric verdict identifiers.","format":"int64","example":1,"enum":[1,4,3,2,5]},"disposition_name":{"type":"string","description":"The disposition_name field is optional, but is intended to be shown to a user. Applications must therefore remember the mapping of numbers to human words, as in: {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"client_id":{"type":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/Verdict"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVerdicts"},"campaigns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["campaign_type","description","id","schema_version","short_description","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"campaign","enum":["campaign"]},"created":{"type":"string","format":"date-time"},"campaign_type":{"type":"string","description":"String value that describes the type of campaign. For example, a campaign type could be 'Ransomware', 'Advanced Persistent Threat', 'Business Email Compromise', 'Phishing', etc. ","example":"string"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"activity":{"type":"array","description":"Used to capture specific activities or tactics associated with the campaign.\nThe 'activity' field is an array of objects, and each element represents a specific activity and time associated with the campaign. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc. By capturing these activities analysts can identify the specific tactics used by the threat actor(s) behind the campaign.","example":[{"date_time":"2016-01-01T01:01:01.000Z","description":"string"}],"items":{"required":["date_time","description"],"type":"object","properties":{"date_time":{"type":"string","description":"Specifies the date and time at which the activity occured.","format":"date-time","example":"2016-01-01T01:01:01Z"},"description":{"type":"string","description":"A description of the activity.","example":"string"}},"additionalProperties":false,"description":"Captures the specific activities or tactics associated with the entity. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc.","example":{"date_time":"2016-01-01T01:01:01.000Z","description":"string"},"$$ref":"#/components/schemas/Activity"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"array","description":"Characterizes the intended effect of this cyber threat campaign.","example":["Account Takeover"],"items":{"type":"string"}},"status":{"type":"string","description":"Indicates current Status of the Campaign. \n\nCan have one of the following values: \n\n- Ongoing: Indicates that the campaign is currently active and ongoing. For example, a mass phishing campaign that is actively targeting users is considered 'ongoing'.\n\n- Historic: Campaign has already occurred and is now in the past.\n\n- Future: This indicates that a campaign is planned or expected to occur in the future. For example, a threat actor may announce their intention to launch a specific cyberattack campaign at a future date.","example":"Future","enum":["Historic","Future","Ongoing"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Level of confidence held in the characterization of this Campaign.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"names":{"type":"array","description":"Used to capture alternate names or aliases associated with the campaign. A cyberattack campaign may have multiple names or aliases depending on the group or actor(s) behind the attack, e.g., 'Wannacry' is also known as 'WannaCrypt', 'WCry', 'Wanna Decryptor', etc.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Campaign"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCampaigns"},"actors":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","source","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"motivation":{"type":"string","description":"The reason or purpose behind the malicious activity attributed to this Actor. By understanding a threat actor's motivation, analysts can better predict the attacker's behavior and anticipate future malicious actions.","example":"Ego"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["description","related_identities"],"type":"object","properties":{"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"related_identities":{"type":"array","description":"Identifies other entity Identities related to this Identity.","example":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}],"items":{"required":["identity"],"type":"object","properties":{"identity":{"type":"string","description":"The reference (URI) of the related Identity object.","example":"string"},"confidence":{"type":"string","description":"Specifies the level of confidence in the assertion of the relationship between the two objects.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"information_source":{"type":"string","description":"Specifies the source of the information about the relationship between the two components.","example":"string"},"relationship":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes a related Identity","example":{"identity":"string","confidence":"High","information_source":"string","relationship":"string"},"$$ref":"#/components/schemas/RelatedIdentity"}}},"additionalProperties":false,"description":"Can contain information such as the name of the attacker, the group or organization they belong to, or any other identifier that can help in the attribution process.","example":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"$$ref":"#/components/schemas/Identity"},"sophistication":{"type":"string","description":"Represents the level of expertise and skill that the threat actor has displayed in their malicious activities. Can help security analysts assess the potential impact of an attacker's TTPs and determine the potential attack surface. \n\nFor example, a threat actor with a low sophistication level may primarily rely on off-the-shelf malware and attack tools, while an attacker with high sophistication may use custom tools with advanced evasion techniques, zero-day exploits, and sophisticated methods for command and control of their malware. \n\nThe sophistication level of an attacker can also be inferred based on several factors such as the complexity of attacks, the attacker's knowledge of the targeted organization's systems, and the attacker's ability to remain undetected.\n\nIf an attacker shows a high level of sophistication in reconnaissances, social engineering, and phishing, then the attacker may have a good knowledge of the targeted organization and its employees. This means that the attacker may be more successful in infiltrating the organization's network and compromising its systems.","example":"Aspirant","enum":["Aspirant","Innovator","Practitioner","Novice","Expert"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"planning_and_operational_support":{"type":"string","description":"Provides information about the resources and capabilities of the attacker that could be used to assist in planning and operations related to the threat.\n\n It can be used to describe Infrastructure, Tools, Techniques, and Capabilities used by the threat actor.","example":"string"},"type":{"type":"string","example":"actor","enum":["actor"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Represents the desired outcome or impact the threat actor is trying to achieve through their malicious activities. \n\n Helps security analysts to understand the attacker's goals beyond the immediate impact of the attack. By understanding the intended effect, analysts can draw connections between seemingly unrelated attacks and build a more complete understanding of an attacker's long-term goals and motivations.","example":"Account Takeover"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"aliases":{"type":"array","description":"A list of other names that this Threat Actor is believed to use.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"This field can help analysts decide how much trust they can put in the information provided by the threat intelligence sources.\n\nFor example, an Actor entity can have high confidence if the organization's security researchers have been tracking it for a long time and have gathered a significant amount of intelligence about it through various sources, such as analysis of malware, network traffic, and human intelligence. In contrast, low confidence may indicate the organization has only seen limited or circumstantial evidence.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Actor"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataActors"},"data_tables":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["columns","id","rows","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"columns":{"type":"array","description":"An ordered list of column definitions.","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"type":{"type":"string","example":"data-table","enum":["data-table"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"rows":{"type":"array","description":"An ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/DataTable"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataDataTables"},"notes":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataNotes"},"identity_assertions":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["assertions","id","identity","schema_version","type"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["observables"],"type":"object","properties":{"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"additionalProperties":false,"description":"Attributes for which the assertion is being made.","example":{"observables":[{"value":"1.2.3.4","type":"ip"}]},"$$ref":"#/components/schemas/IdentityCoordinates"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"identity-assertion","enum":["identity-assertion"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"assertions":{"type":"array","description":"Any known context about the identity attributes.","example":[{"name":"cisco:ctr:ad:host_domain_name","value":"string"}],"items":{"required":["name","value"],"type":"object","properties":{"name":{"type":"string","description":"An open vocabulary containing well known assertion types","example":"cisco:ctr:ad:host_domain_name"},"value":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"cisco:ctr:ad:host_domain_name","value":"string"},"$$ref":"#/components/schemas/Assertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/IdentityAssertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIdentityAssertions"},"judgements":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","disposition","disposition_name","id","observable","priority","schema_version","severity","source","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"reason_uri":{"type":"string","description":"A URI","example":"string"},"type":{"type":"string","example":"judgement","enum":["judgement"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Matches :disposition_name as in {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","format":"int64","example":1,"enum":[1,4,3,2,5]},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"disposition_name":{"type":"string","description":"String verdict identifiers.","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"priority":{"type":"integer","description":"A value 0-100 that determine the priority of a judgement. Curated feeds of black/white lists, for example known good products within your organizations, should use a 95. All automated systems should use a priority of 90, or less. Human judgements should have a priority of 100, so that humans can always override machines.","format":"int64","example":10},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]}},"additionalProperties":false,"$$ref":"#/components/schemas/Judgement"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataJudgements"},"malwares":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The type of malware being described.","example":["adware"],"items":{"type":"string"}},"abstraction_level":{"type":"string","description":"Malware abstraction level.","example":"family","enum":["family","version","variant"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"malware","enum":["malware"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of Kill Chain Phases for which this Malware can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Malware"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataMalwares"},"incidents":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","id","incident_time","schema_version","status","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"assignees":{"type":"array","description":"A set of owners assigned to this incident.","example":["string"],"items":{"type":"string"}},"meta":{"type":"object","additionalProperties":{"type":"object","description":"custom field relevant to attach meta data to.","example":{},"x-oneOf":[{"example":"string","type":"string"},{"example":10,"type":"number","format":"double"},{"example":"2016-01-01T01:01:01.000Z","type":"string","format":"date-time"},{"example":"keyword","type":"string"},{"example":true,"type":"boolean"}]},"description":"metadata associated to the incident.","example":{"keyword":{}},"$$ref":"#/components/schemas/MetaData"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"incident","enum":["incident"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"incident_time":{"required":["opened"],"type":"object","properties":{"opened":{"type":"string","description":"Time the incident was first opened.","format":"date-time","example":"2016-01-01T01:01:01Z"},"discovered":{"type":"string","description":"Time the incident was first discovered.","format":"date-time","example":"2016-01-01T01:01:01Z"},"reported":{"type":"string","description":"Time the incident was first reported.","format":"date-time","example":"2016-01-01T01:01:01Z"},"remediated":{"type":"string","description":"Time that the remediation of the damage from the incident was completed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"closed":{"type":"string","description":"Time that the incident was last closed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"rejected":{"type":"string","description":"Time that the incident was first rejected.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Relevant time values associated with this Incident.","example":{"opened":"2016-01-01T01:01:01.000Z","discovered":"2016-01-01T01:01:01.000Z","reported":"2016-01-01T01:01:01.000Z","remediated":"2016-01-01T01:01:01.000Z","closed":"2016-01-01T01:01:01.000Z","rejected":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/IncidentTime"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"discovery_method":{"type":"string","description":"Identifies how the incident was discovered.","example":"Agent Disclosure"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Specifies the suspected intended effect of this incident","example":"Account Takeover"},"categories":{"type":"array","description":"A set of categories for this incident.","example":["Attrition"],"items":{"type":"string"}},"status":{"type":"string","description":"The `status` field represents the current state of an incident within the incident management process. Its values help in tracking and reporting the progress of the incident from its discovery to its resolution.","example":"Closed","enum":["New","Closed","Open: Recovered","Closed: Other","Hold: Internal","Hold: Legal","Closed: Under Review","Rejected","Open","Restoration Achieved","Incident Reported","Closed: Suspected","Stalled","Open: Contained","Closed: Near-Miss","Hold: External","Containment Achieved","New: Processing","Closed: Confirmed Threat","Closed: False Positive","Open: Reported","Open: Investigating","Hold","New: Presented"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"promotion_method":{"type":"string","description":"Describes method for promoting an Incident, whether manually or automatically. An Incident may be created manually by a SOAR analyst or SOC operator, or through an automated correlation or aggregation rule or engine that matches a specific set of events or alerts, and promotes them to Incident(s).","example":"Automated","enum":["Automated","Manual"]},"severity":{"type":"string","description":"Represents the potential impact of an incident on an organization's security posture and business operations. It helps organizations prioritize and allocate resources for incident response based on the severity level of the incident \nIt helps analysts and incident handlers prioritize incidents by indicating the level of risk and potential impact associated with the incident. This enables organizations to allocate resources efficiently and address the most critical incidents first.\nCan also be used to generate reports and metrics for measuring the effectiveness of the incident response process and to identify trends and patterns in the threat landscape.\nIt is important to note that the `severity` field is subjective and can be interpreted differently by different organizations or analysts. Therefore, it should be used in conjunction with other intelligence attributes, such as the `confidence` field, to provide a more comprehensive view of the incident.","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"scores":{"type":"object","additionalProperties":{"type":"number","description":"Field is used to indicate the severity or impact of the threat represented by the incident.\nIt's an open-type dictionary object with score types and numeric value of the score.\n\nFor example, systems can have the following score types:\n\n- `asset` - assesses the potential damage or harm that the threat can cause to the affected asset(s). The scale ranges from 0 to 10, with 10 indicating the highest potential harm. \n\n- `global` - assesses the overall impact or significance of the threat to the organization or wider community. The scale ranges from 0 to 1000, with 1000 indicating the highest impact.\n\n- `ttp` - a measure of the threat actor's proficiency in utilizing TTPs. Typically, ranges from 0-100, with a higher score indicating a greater threat or concern.","format":"double","example":10},"description":"Used to indicate the severity or impact score of the threat represented by the incident.","example":{"asset":10},"$$ref":"#/components/schemas/IncidentScores"},"client_id":{"type":"string"},"techniques":{"type":"array","description":"Represents the specific methods or actions used by an attacker to carry out an offensive maneuver or achieve their goals.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Represents the level of certainty or trustworthiness associated with the incident. It denotes the reliability of the intelligence associated with the incident.\nThe `confidence` field can take on several values, including:\n- `info`: Indicates that the incident information is based on sources with no previous track record or there is no track record for the source reporting the incident.\n- `low`: Indicates that the incident information is based on sources with a questionable track record or there is limited information about the accuracy of the source.\n- `medium`: Indicates that the incident information is based on sources with a mixed track record or of uncertain reliability.\n- `high`: Indicates that the incident information is based on sources with a proven track record and high degree of reliability.\nThe `confidence` field can be used to indicate the level of trust and confidence that can be attributed to the incident, and it may impact how the incident is prioritized, analyzed and addressed. It can also help in the decision-making process associated with the incident response activities.\nIt is important to note that the `confidence` field is subjective and can be interpreted differently by different organizations or analysts. As such, it is often used in conjunction with other intelligence attributes, such as the `severity` field, to provide a more complete picture of the incident.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"tactics":{"type":"array","description":"Represents the offensive techniques, approaches, or procedures that an adversary may use to achieve their objectives during an attack. It helps in understanding the intent and capabilities of the adversary and can be used to identify indicators of attack (IoAs) or indicators of compromise (IoCs) that are associated with the adversary's tactics.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Incident"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIncidents"},"sightings":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","count","id","observed_time","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"relations":{"type":"array","description":"Provide any context we can about where the observable came from.","example":[{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}}],"items":{"required":["origin","related","relation","source"],"type":"object","properties":{"origin":{"type":"string","example":"string"},"origin_uri":{"type":"string","description":"A URI","example":"string"},"relation":{"type":"string","example":"Allocated"},"relation_info":{"type":"object","additionalProperties":{"type":"object","example":{}},"example":{"keyword":{}},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightingsDocsRelationsRelationInfo"},"source":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"related":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"additionalProperties":false,"description":"A relation inside a Sighting.","example":{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}},"$$ref":"#/components/schemas/ObservedRelation"}},"sensor_coordinates":{"required":["observables","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the device that made the sighting (sensor) and contains identifying observables for the sensor.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"os":"string"},"$$ref":"#/components/schemas/SensorCoordinates"},"observables":{"type":"array","description":"The object(s) of interest.","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"type":{"type":"string","example":"sighting","enum":["sighting"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"targets":{"type":"array","description":"May include one or more targets that observed the associated indicator. Targets can include network devices, host devices, or other entities that are capable of detecting indicators of compromise.\n\nCan be used to assess the scope of potential threats, helping analysts understand which devices or components of the network may be vulnerable to attack. For example, if a particular malware strain is detected on several different systems within an organization, the `targets` field may indicate which systems are affected and which may need to be isolated or patched to prevent further spread.","example":[{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"}],"items":{"required":["observables","observed_time","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the target of the sighting and contains identifying observables for the target.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"},"$$ref":"#/components/schemas/IdentitySpecification"}},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"resolution":{"type":"string","description":"Represents the disposition or actions taken on the associated threat intelligence.","example":"detected"},"internal":{"type":"boolean","description":"If `true`, indicates that the sighting was reported from internal sources, such as an organization's own internal security tools or SOC.\n Internal sightings are often considered more reliable and actionable than external sightings, which are reported from external sources and may have a lower level of trustworthiness. Internal sightings can provide more context and can help identify potential threats that are unique to a particular environment or organization.\n Internal sightings can also help organizations prioritize their security response efforts by identifying threats that are specific to their environment and may not yet be widely known.","example":false},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"count":{"type":"integer","description":"The number of times an indicator was observed within a certain period of time.\nFor example, if an IP address associated with known malicious activity is observed once within a period of time, it may indicate a low-level threat. However, if the same IP address is observed multiple times within a short time frame, it may indicate a more severe and persistent threat.\nIt can also be used to prioritize security alerts and indicate the urgency of a response. High counts indicate that an indicator is actively being used in a larger campaign, while low counts may indicate isolated incidents.","format":"int64","example":10},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"context":{"type":"object","properties":{"http_events":{"type":"array","description":"a list of `HTTPType`","example":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"items":{"required":["host","process_id","process_name","time","traffic","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"method":{"type":"string","example":"CONNECT","enum":["OPTIONS","PATCH","TRACE","HEAD","POST","CONNECT","GET","PUT"]},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"HTTPEvent","enum":["HTTPEvent"]},"host":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"query":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"encrypted":{"type":"boolean","example":true},"url_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10},"$$ref":"#/components/schemas/HTTPType"}},"process_create_events":{"type":"array","description":"a list of `ProcessCreate`","example":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"items":{"required":["process_id","process_name","time","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"parent_process_guid":{"type":"integer","format":"int64","example":10},"process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_size":{"type":"integer","format":"int64","example":10},"process_size":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"ProcessCreateEvent","enum":["ProcessCreateEvent"]},"parent_process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_creation_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"},"$$ref":"#/components/schemas/ProcessCreateType"}},"registry_delete_events":{"type":"array","description":"a list of `RegistryDeleteType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryDeleteEvent","enum":["RegistryDeleteEvent"]},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"},"$$ref":"#/components/schemas/RegistryDeleteType"}},"file_modify_events":{"type":"array","description":"a list of `FileModifyType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileModifyEvent","enum":["FileModifyEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileModifyType"}},"registry_set_events":{"type":"array","description":"a list of `RegistrySetType`","example":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_value","time","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"registry_data":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"RegistrySetEvent","enum":["RegistrySetEvent"]},"registry_data_length":{"type":"integer","format":"int64","example":10},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"},"$$ref":"#/components/schemas/RegistrySetType"}},"file_create_events":{"type":"array","description":"a list of `FileCreateType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileCreateEvent","enum":["FileCreateEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileCreateType"}},"registry_create_events":{"type":"array","description":"a list of `RegistryCreateType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryCreateEvent","enum":["RegistryCreateEvent"]}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"},"$$ref":"#/components/schemas/RegistryCreateType"}},"library_load_events":{"type":"array","description":"a list of `LibraryLoadType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"items":{"required":["dll_library_name","dll_library_path","process_id","process_name","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"LibraryLoadEvent","enum":["LibraryLoadEvent"]},"dll_library_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"dll_library_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"},"$$ref":"#/components/schemas/LibraryLoadType"}},"file_move_events":{"type":"array","description":"a list of `FileMoveType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"items":{"required":["file_name","file_path","new_name","old_name","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileMoveEvent","enum":["FileMoveEvent"]},"old_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"new_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"},"$$ref":"#/components/schemas/FileMoveType"}},"file_delete_events":{"type":"array","description":"a list of `FileDeleteType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileDeleteEvent","enum":["FileDeleteEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileDeleteType"}},"netflow_events":{"type":"array","description":"a list of `NetflowType`","example":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"items":{"required":["process_id","process_name","time","traffic","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_in":{"type":"integer","format":"int64","example":10},"process_guid":{"type":"integer","format":"int64","example":10},"process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"flow_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"NetflowEvent","enum":["NetflowEvent"]},"process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_out":{"type":"integer","format":"int64","example":10},"process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"},"$$ref":"#/components/schemas/NetflowType"}},"registry_rename_events":{"type":"array","description":"a list of `RegistryRenameType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_old_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryRenameEvent","enum":["RegistryRenameEvent"]},"registry_old_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"},"$$ref":"#/components/schemas/RegistryRenameType"}}},"additionalProperties":false,"description":"Context including the event type that best fits the type of the sighting.","example":{"http_events":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"process_create_events":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"registry_delete_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"file_modify_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_set_events":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"file_create_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_create_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"library_load_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"file_move_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"file_delete_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"netflow_events":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"registry_rename_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}]},"$$ref":"#/components/schemas/Context"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"sensor":{"type":"string","description":"The OpenC2 Actuator name that best fits the device that is creating this sighting (e.g. network.firewall)","example":"endpoint"},"data":{"required":["columns","rows"],"type":"object","properties":{"columns":{"type":"array","description":"an ordered list of column definitions","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"rows":{"type":"array","description":"an ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10}},"additionalProperties":false,"description":"An embedded data table for the Sighting.","example":{"columns":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"rows":[[{}]],"row_count":10},"$$ref":"#/components/schemas/SightingDataTable"}},"additionalProperties":false,"$$ref":"#/components/schemas/Sighting"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightings"},"relationships":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","relationship_type","schema_version","source_ref","target_ref","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"target_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"type":{"type":"string","example":"relationship","enum":["relationship"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"source_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"relationship_type":{"type":"string","example":"attributed-to"}},"additionalProperties":false,"$$ref":"#/components/schemas/Relationship"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataRelationships"},"vulnerabilities":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Various sources of vulnerability information can be used, including third-party resources like the National Vulnerability Database (NVD) and the Common Vulnerabilities and Exposures (CVE) database. The platform then analyzes this data and provides the user with relevant details such as the severity of the vulnerability, the affected systems, and remediation recommendations. \n\n Based on this information, the user can prioritize patching and other mitigation strategies to reduce the risk of potential attacks.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"}},"additionalProperties":false,"$$ref":"#/components/schemas/Vulnerability"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVulnerabilities"},"coas":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"stage":{"type":"string","description":"Specifies what stage in the cyber threat management lifecycle this Course Of Action is relevant to.","example":"Containment","enum":["Identification","Lessons Learned","Remedy","Preparation","Containment","Response","Eradication","Recovery"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"efficacy":{"type":"string","description":"Effectiveness of this course of action in achieving its targeted objective.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","example":"coa","enum":["coa"]},"created":{"type":"string","format":"date-time"},"related_COAs":{"type":"array","description":"Identifies or characterizes relationships to one or more related courses of action.","example":[{"confidence":"High","source":"string","relationship":"string","COA_id":"string"}],"items":{"required":["COA_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"COA_id":{"type":"string","description":"A URI leading to a COA.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","COA_id":"string"},"$$ref":"#/components/schemas/RelatedCOA"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"coa_type":{"type":"string","description":"The type of this COA","example":"Diplomatic Actions","enum":["Diplomatic Actions","Physical Access Restrictions","Policy Actions","Internal Blocking","Playbook","Redirection","Phase","Eradication","Public Disclosure","Monitoring","Patching","Logical Access Restrictions","Redirection (Honey Pot)","Rebuilding","Perimeter Blocking","Hardening","Other","Training","Task"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"objective":{"type":"array","description":"Characterizes the objective to provide guidance on how to mitigate a security incident that has been identified.","example":["string"],"items":{"type":"string"}},"cost":{"type":"string","description":"Characterizes the estimated cost for applying this course of action.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"open_c2_coa":{"required":["action","type"],"type":"object","properties":{"type":{"type":"string","example":"structured_coa","enum":["structured_coa"]},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"action":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"alert","enum":["stop","save","delete","remediate","redirect","alert","query","augment","snapshot","update","allow","scan","investigate","modify","sync","start","pause","deny","substitute","distill","move","restart","other","detonate","response","set","notify","report","restore","get","throttle","mitigate","resume","locate","contain"]}},"additionalProperties":false,"example":{"type":"alert"},"$$ref":"#/components/schemas/ActionType"},"target":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"amp_computer_guid"},"specifiers":{"type":"string","description":"Observable types that can be acted upon.","example":"string"}},"additionalProperties":false,"example":{"type":"amp_computer_guid","specifiers":"string"},"$$ref":"#/components/schemas/TargetType"},"actuator":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"endpoint","enum":["endpoint.sensor","process.network-scanner","network.switch","network.security_manager","process.vulnerability-scanner","network.hub","network.ids","network.firewall","process","network.sense_making","process.sandbox","network.modem","process.email-service","process.dns-server","network.vpn","process.connection-scanner","network.nic","endpoint.printer","network.gateway","process.reputation-service","process.remediation-service","network","process.virtualization-service","network.ips","endpoint.smart-meter","endpoint.digital-telephone-handset","endpoint.workstation","endpoint.server","network.wap","endpoint.laptop","process.aaa-server","process.directory-service","endpoint.pos-terminal","network.bridge","other","process.file-scanner","network.proxy","endpoint","process.location-service","network.sensor","endpoint.smart-phone","network.hips","process.anti-virus-scanner","endpoint.tablet","network.guard","network.router"]},"specifiers":{"type":"array","description":"List of additional properties describing the actuator.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"type":"endpoint","specifiers":["string"]},"$$ref":"#/components/schemas/ActuatorType"},"modifiers":{"type":"object","properties":{"response":{"type":"string","example":"acknowledge","enum":["query","status","acknowledge","command-ref"]},"method":{"type":"array","example":["acl"],"items":{"type":"string","enum":["blackhole","unauthenticated","suspend","graceful","hibernate","whitelist","honeypot","immediate","spawn","blacklist","acl","segmentation","authenticated"]}},"additional_properties":{"required":["context"],"type":"object","properties":{"context":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"context":"string"},"$$ref":"#/components/schemas/AdditionalProperties"},"time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"frequency":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"duration":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"source":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"search":{"type":"string","example":"cve","enum":["vendor_bulletin","patch","signature","cve"]},"option":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"location":{"type":"string","example":"internal","enum":["internal","perimeter"]},"delay":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"destination":{"type":"string","example":"copy-to","enum":["modify-to","set-to","copy-to","move-to","save-to","restore-point","report-to"]}},"additionalProperties":false,"example":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"},"$$ref":"#/components/schemas/ModifierType"}},"additionalProperties":false,"example":{"type":"structured_coa","id":"string","action":{"type":"alert"},"target":{"type":"amp_computer_guid","specifiers":"string"},"actuator":{"type":"endpoint","specifiers":["string"]},"modifiers":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"}},"$$ref":"#/components/schemas/OpenC2COA"},"structured_coa_type":{"type":"string","example":"openc2","enum":["openc2"]},"impact":{"type":"string","description":"Characterizes the estimated impact of applying this course of action.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/COA"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCoas"}},"additionalProperties":false,"$$ref":"#/components/schemas/ModuleObserveBundle"}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleData"}},"errors":{"type":"array","items":{"required":["code","message","module_instance_id","module_type_id","type"],"type":"object","properties":{"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"code":{"type":"string"},"message":{"type":"string"},"type":{"type":"string","enum":["fatal","warning","error"]},"module":{"type":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/ErrorMessage"}}},"additionalProperties":false,"example":{"data":[{"module":"Sample Module","module_instance_id":"da033b3c-81da-4118-b73a-f03feb3adecf","module_type_id":"c84f54db-c187-4cab-8751-2b39b007ee55","data":{"verdicts":{"count":2,"docs":[{"type":"verdict","disposition":2,"observable":{"value":"https://ilo.brenz.pl/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.410Z","end_time":"2023-03-11T13:36:23.410Z"}},{"type":"verdict","disposition":2,"observable":{"value":"http://ilo.brenz.pl/favicon.ico/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.420Z","end_time":"2023-03-11T13:36:23.420Z"}}]}}}]},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundle"}},"application/transit+json":{"schema":{"type":"object","properties":{"data":{"type":"array","items":{"required":["data","module","module_instance_id","module_type_id"],"type":"object","properties":{"module":{"type":"string"},"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"data":{"type":"object","properties":{"tools":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The kind(s) of tool(s) being described.","example":["credential-exploitation"],"items":{"type":"string"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"tool","enum":["tool"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tool_version":{"type":"string","description":"The version identifier associated with the Tool.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of kill chain phases for which this Tool can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Tool"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataTools"},"indicators":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","producer","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"tags":{"type":"array","description":"Descriptors for this indicator.","example":["string"],"items":{"type":"string"}},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"producer":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","description":"The fixed value indicator","example":"indicator","enum":["indicator"]},"created":{"type":"string","format":"date-time"},"test_mechanisms":{"type":"array","description":"Test Mechanisms effective at identifying the cyber Observables specified in this cyber threat Indicator.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"composite_indicator_expression":{"required":["indicator_ids","operator"],"type":"object","properties":{"operator":{"type":"string","example":"and","enum":["not","or","and"]},"indicator_ids":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"operator":"and","indicator_ids":["string"]},"$$ref":"#/components/schemas/CompositeIndicatorExpression"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"likely_impact":{"type":"string","description":"Likely potential impact within the relevant context if this Indicator were to occur.","example":"string"},"indicator_type":{"type":"array","description":"Specifies the type or types for this Indicator.","example":["Anonymization"],"items":{"type":"string","enum":["File Hash Watchlist","Private Threat Feed","IMEI Watchlist","Malicious E-mail","Exfiltration","C2","URL Watchlist","IMSI Watchlist","Malware Artifacts","Domain Watchlist","Anonymization","Host Characteristics","IP Watchlist","Compromised PKI Certificate","Login Name"]}},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"Relevant kill chain phases indicated by this Indicator.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"negate":{"type":"boolean","description":"Specifies the absence of the pattern.","example":true},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"level of confidence held in the accuracy of this Indicator.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"specification":{"type":"object","example":{},"x-oneOf":[{"required":["judgements","required_judgements","type"],"type":"object","properties":{"type":{"type":"string","example":"Judgement","enum":["Judgement"]},"judgements":{"type":"array","example":["string"],"items":{"type":"string"}},"required_judgements":{"type":"array","example":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}],"items":{"required":["judgement_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"},"$$ref":"#/components/schemas/RelatedJudgement"}}},"additionalProperties":false,"description":"An indicator based on a list of judgements. If any of the Observables in it's judgements are encountered, than it may be matches against. If there are any required judgements, they all must be matched in order for the indicator to be considered a match.","example":{"type":"Judgement","judgements":["string"],"required_judgements":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}]},"$$ref":"#/components/schemas/JudgementSpecification"},{"required":["type","variables"],"type":"object","properties":{"type":{"type":"string","example":"ThreatBrain","enum":["ThreatBrain"]},"query":{"type":"string","example":"string"},"variables":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"description":"An indicator which runs in threatbrain...","example":{"type":"ThreatBrain","query":"string","variables":["string"]},"$$ref":"#/components/schemas/ThreatBrainSpecification"},{"required":["snort_sig","type"],"type":"object","properties":{"type":{"type":"string","example":"Snort","enum":["Snort"]},"snort_sig":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"Snort","snort_sig":"string"},"$$ref":"#/components/schemas/SnortSpecification"},{"required":["SIOC","type"],"type":"object","properties":{"type":{"type":"string","example":"SIOC","enum":["SIOC"]},"SIOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"SIOC","SIOC":"string"},"$$ref":"#/components/schemas/SIOCSpecification"},{"required":["open_IOC","type"],"type":"object","properties":{"type":{"type":"string","example":"OpenIOC","enum":["OpenIOC"]},"open_IOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which contains an XML blob of an openIOC indicator.","example":{"type":"OpenIOC","open_IOC":"string"},"$$ref":"#/components/schemas/OpenIOCSpecification"}]}},"additionalProperties":false,"$$ref":"#/components/schemas/Indicator"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIndicators"},"attack_patterns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"abstraction_level":{"type":"string","description":"The CAPEC abstraction level for patterns describing techniques to attack a system.","example":"aggregate","enum":["detailed","standard","aggregate","meta","category"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"attack-pattern","enum":["attack-pattern"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"x_mitre_platforms":{"type":"array","description":"ATT&CK Technique.Platforms.","example":["string"],"items":{"type":"string"}},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"x_mitre_data_sources":{"type":"array","description":"ATT&CK Technique.Data Sources.","example":["string"],"items":{"type":"string"}},"kill_chain_phases":{"type":"array","description":"A kill chain is a series of steps that an attacker must go through to successfully achieve their objective. The concept was originally developed by the military, but has been adapted to the cybersecurity field to describe the steps an attacker goes through to compromise a target system and achieve their goal.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"x_mitre_contributors":{"type":"array","description":"ATT&CK Technique.Contributors.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/AttackPattern"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataAttackPatterns"},"weaknesses":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Should be short and limited to the key points that define this weakness.","example":"string"},"background_details":{"type":"string","description":"Information that is relevant but not related to the nature of the weakness itself.","example":"string"},"paradigms":{"type":"array","description":"Applicable paradigms.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Paradigm name (Client Server, Mainframe)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Paradigm"}},"abstraction_level":{"type":"string","description":"Refers to the level of abstraction or granularity used to describe the weakness. It helps to categorize the vulnerability based on the level of detail provided.","example":"Base","enum":["Variant","Class","Base","Compound"]},"architectures":{"type":"array","description":"Applicable architectures.","example":[{"prevalence":"Often","name":"string","class":"Embedded"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Architecture name (ARM, x86, ...)","example":"string"},"class":{"type":"string","description":"Class of architecture","example":"Embedded"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Embedded"},"$$ref":"#/components/schemas/Architecture"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"alternate_terms":{"type":"array","description":"Indicates one or more other names used to describe this weakness.","example":[{"term":"string","description":"string"}],"items":{"required":["term"],"type":"object","properties":{"term":{"type":"string","description":"The actual alternate term.","example":"string"},"description":{"type":"string","description":"Provides context for the alternate term by which this weakness may be known.","example":"string"}},"additionalProperties":false,"example":{"term":"string","description":"string"},"$$ref":"#/components/schemas/AlternateTerm"}},"likelihood":{"type":"string","description":"Likelihood of exploit.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","description":"The fixed value weakness","example":"weakness","enum":["weakness"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"functional_areas":{"type":"array","description":"Identifies the functional area of the software in which the weakness is most likely to occur.","example":["Authentication"],"items":{"type":"string"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"modes_of_introduction":{"type":"array","description":"Information about how and when a given weakness may be introduced.","example":[{"phase":"Architecture and Design","note":"string"}],"items":{"required":["phase"],"type":"object","properties":{"phase":{"type":"string","description":"Identifies the point in the software life cycle at which the weakness may be introduced.","example":"Architecture and Design"},"note":{"type":"string","description":"Provides a typical scenario related to introduction during the given phase.","example":"string"}},"additionalProperties":false,"example":{"phase":"Architecture and Design","note":"string"},"$$ref":"#/components/schemas/ModeOfIntroduction"}},"structure":{"type":"string","description":"Defines the structural nature of the weakness.","example":"Chain","enum":["Chain","Simple","Composite"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"notes":{"type":"array","description":"Provides any additional comments about the weakness.","example":[{"content":"","id":"","note_class":"","related_entities":[],"schema_version":"1.3.18","type":"note"}],"items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}},"common_consequences":{"type":"array","description":"Refers to the typical or expected negative effects that can result from exploiting the weakness. This could include anything from unauthorized access to data, denial of service, system crashes or other things.","example":[{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"}],"items":{"required":["scopes"],"type":"object","properties":{"scopes":{"type":"array","description":"Identifies the security property that is violated.","example":["Access Control"],"items":{"type":"string"}},"impacts":{"type":"array","description":"Describes the technical impact that arises if an adversary succeeds in exploiting this weakness.","example":["Alter Execution Logic"],"items":{"type":"string"}},"likelihood":{"type":"string","description":"How likely the specific consequence is expected to be seen relative to the other consequences.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"note":{"type":"string","description":"Additional commentary about a consequence.","example":"string"}},"additionalProperties":false,"example":{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"},"$$ref":"#/components/schemas/Consequence"}},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"detection_methods":{"type":"array","description":"Identifies methods that may be employed to detect this weakness, including their strengths and limitations.","example":[{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"}],"items":{"required":["description","method"],"type":"object","properties":{"method":{"type":"string","description":"Identifies the particular detection method being described.","example":"Architecture or Design Review"},"description":{"type":"string","description":"Provides some context of how this method can be applied to a specific weakness.","example":"string"},"effectiveness":{"type":"string","description":"How effective the detection method may be in detecting the associated weakness.","example":"High"},"effectiveness_notes":{"type":"string","description":"Provides additional discussion of the strengths and shortcomings of this detection method.","example":"string"}},"additionalProperties":false,"example":{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"},"$$ref":"#/components/schemas/DetectionMethod"}},"operating_systems":{"type":"array","description":"Applicable operating systems.","example":[{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"version":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"cpe_id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"class":{"type":"string","description":"Class of Operating System.","example":"Android"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"},"$$ref":"#/components/schemas/OperatingSystem"}},"client_id":{"type":"string"},"affected_resources":{"type":"array","description":"Identifies system resources that can be affected by an exploit of this weakness.","example":["CPU"],"items":{"type":"string"}},"languages":{"type":"array","description":"Applicable Languages.","example":[{"prevalence":"Often","name":"string","class":"Assembly"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Language name (Clojure, Java, ...)","example":"string"},"class":{"type":"string","description":"Class of language.","example":"Assembly"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Assembly"},"$$ref":"#/components/schemas/Language"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"potential_mitigations":{"type":"array","description":"Describes potential mitigations associated with a weakness.","example":[{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"}],"items":{"required":["description"],"type":"object","properties":{"description":{"type":"string","description":"A description of this individual mitigation including any strengths and shortcomings of this mitigation for the weakness.","example":"string"},"phases":{"type":"array","description":"Indicates the development life cycle phase during which this particular mitigation may be applied.","example":["Architecture and Design"],"items":{"type":"string"}},"strategy":{"type":"string","description":"A general strategy for protecting a system to which this mitigation contributes.","example":"Attack Surface Reduction"},"effectiveness":{"type":"string","description":"Summarizes how effective the mitigation may be in preventing the weakness.","example":"Defense in Depth"},"effectiveness_notes":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"}},"additionalProperties":false,"example":{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"},"$$ref":"#/components/schemas/Mitigation"}},"technologies":{"type":"array","description":"Applicable technologies.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Technology name (Web Server, Web Client)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Technology"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Weakness"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataWeaknesses"},"feedbacks":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["entity_id","feedback","id","reason","schema_version","type"],"type":"object","properties":{"feedback":{"type":"integer","format":"int64","example":-1,"enum":[0,1,-1]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"feedback","enum":["feedback"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Feedback"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataFeedbacks"},"verdicts":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["disposition","observable","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"type":{"type":"string","example":"verdict","enum":["verdict"]},"created":{"type":"string","format":"date-time"},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Numeric verdict identifiers.","format":"int64","example":1,"enum":[1,4,3,2,5]},"disposition_name":{"type":"string","description":"The disposition_name field is optional, but is intended to be shown to a user. Applications must therefore remember the mapping of numbers to human words, as in: {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"client_id":{"type":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/Verdict"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVerdicts"},"campaigns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["campaign_type","description","id","schema_version","short_description","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"campaign","enum":["campaign"]},"created":{"type":"string","format":"date-time"},"campaign_type":{"type":"string","description":"String value that describes the type of campaign. For example, a campaign type could be 'Ransomware', 'Advanced Persistent Threat', 'Business Email Compromise', 'Phishing', etc. ","example":"string"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"activity":{"type":"array","description":"Used to capture specific activities or tactics associated with the campaign.\nThe 'activity' field is an array of objects, and each element represents a specific activity and time associated with the campaign. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc. By capturing these activities analysts can identify the specific tactics used by the threat actor(s) behind the campaign.","example":[{"date_time":"2016-01-01T01:01:01.000Z","description":"string"}],"items":{"required":["date_time","description"],"type":"object","properties":{"date_time":{"type":"string","description":"Specifies the date and time at which the activity occured.","format":"date-time","example":"2016-01-01T01:01:01Z"},"description":{"type":"string","description":"A description of the activity.","example":"string"}},"additionalProperties":false,"description":"Captures the specific activities or tactics associated with the entity. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc.","example":{"date_time":"2016-01-01T01:01:01.000Z","description":"string"},"$$ref":"#/components/schemas/Activity"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"array","description":"Characterizes the intended effect of this cyber threat campaign.","example":["Account Takeover"],"items":{"type":"string"}},"status":{"type":"string","description":"Indicates current Status of the Campaign. \n\nCan have one of the following values: \n\n- Ongoing: Indicates that the campaign is currently active and ongoing. For example, a mass phishing campaign that is actively targeting users is considered 'ongoing'.\n\n- Historic: Campaign has already occurred and is now in the past.\n\n- Future: This indicates that a campaign is planned or expected to occur in the future. For example, a threat actor may announce their intention to launch a specific cyberattack campaign at a future date.","example":"Future","enum":["Historic","Future","Ongoing"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Level of confidence held in the characterization of this Campaign.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"names":{"type":"array","description":"Used to capture alternate names or aliases associated with the campaign. A cyberattack campaign may have multiple names or aliases depending on the group or actor(s) behind the attack, e.g., 'Wannacry' is also known as 'WannaCrypt', 'WCry', 'Wanna Decryptor', etc.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Campaign"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCampaigns"},"actors":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","source","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"motivation":{"type":"string","description":"The reason or purpose behind the malicious activity attributed to this Actor. By understanding a threat actor's motivation, analysts can better predict the attacker's behavior and anticipate future malicious actions.","example":"Ego"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["description","related_identities"],"type":"object","properties":{"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"related_identities":{"type":"array","description":"Identifies other entity Identities related to this Identity.","example":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}],"items":{"required":["identity"],"type":"object","properties":{"identity":{"type":"string","description":"The reference (URI) of the related Identity object.","example":"string"},"confidence":{"type":"string","description":"Specifies the level of confidence in the assertion of the relationship between the two objects.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"information_source":{"type":"string","description":"Specifies the source of the information about the relationship between the two components.","example":"string"},"relationship":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes a related Identity","example":{"identity":"string","confidence":"High","information_source":"string","relationship":"string"},"$$ref":"#/components/schemas/RelatedIdentity"}}},"additionalProperties":false,"description":"Can contain information such as the name of the attacker, the group or organization they belong to, or any other identifier that can help in the attribution process.","example":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"$$ref":"#/components/schemas/Identity"},"sophistication":{"type":"string","description":"Represents the level of expertise and skill that the threat actor has displayed in their malicious activities. Can help security analysts assess the potential impact of an attacker's TTPs and determine the potential attack surface. \n\nFor example, a threat actor with a low sophistication level may primarily rely on off-the-shelf malware and attack tools, while an attacker with high sophistication may use custom tools with advanced evasion techniques, zero-day exploits, and sophisticated methods for command and control of their malware. \n\nThe sophistication level of an attacker can also be inferred based on several factors such as the complexity of attacks, the attacker's knowledge of the targeted organization's systems, and the attacker's ability to remain undetected.\n\nIf an attacker shows a high level of sophistication in reconnaissances, social engineering, and phishing, then the attacker may have a good knowledge of the targeted organization and its employees. This means that the attacker may be more successful in infiltrating the organization's network and compromising its systems.","example":"Aspirant","enum":["Aspirant","Innovator","Practitioner","Novice","Expert"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"planning_and_operational_support":{"type":"string","description":"Provides information about the resources and capabilities of the attacker that could be used to assist in planning and operations related to the threat.\n\n It can be used to describe Infrastructure, Tools, Techniques, and Capabilities used by the threat actor.","example":"string"},"type":{"type":"string","example":"actor","enum":["actor"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Represents the desired outcome or impact the threat actor is trying to achieve through their malicious activities. \n\n Helps security analysts to understand the attacker's goals beyond the immediate impact of the attack. By understanding the intended effect, analysts can draw connections between seemingly unrelated attacks and build a more complete understanding of an attacker's long-term goals and motivations.","example":"Account Takeover"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"aliases":{"type":"array","description":"A list of other names that this Threat Actor is believed to use.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"This field can help analysts decide how much trust they can put in the information provided by the threat intelligence sources.\n\nFor example, an Actor entity can have high confidence if the organization's security researchers have been tracking it for a long time and have gathered a significant amount of intelligence about it through various sources, such as analysis of malware, network traffic, and human intelligence. In contrast, low confidence may indicate the organization has only seen limited or circumstantial evidence.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Actor"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataActors"},"data_tables":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["columns","id","rows","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"columns":{"type":"array","description":"An ordered list of column definitions.","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"type":{"type":"string","example":"data-table","enum":["data-table"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"rows":{"type":"array","description":"An ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/DataTable"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataDataTables"},"notes":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataNotes"},"identity_assertions":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["assertions","id","identity","schema_version","type"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["observables"],"type":"object","properties":{"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"additionalProperties":false,"description":"Attributes for which the assertion is being made.","example":{"observables":[{"value":"1.2.3.4","type":"ip"}]},"$$ref":"#/components/schemas/IdentityCoordinates"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"identity-assertion","enum":["identity-assertion"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"assertions":{"type":"array","description":"Any known context about the identity attributes.","example":[{"name":"cisco:ctr:ad:host_domain_name","value":"string"}],"items":{"required":["name","value"],"type":"object","properties":{"name":{"type":"string","description":"An open vocabulary containing well known assertion types","example":"cisco:ctr:ad:host_domain_name"},"value":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"cisco:ctr:ad:host_domain_name","value":"string"},"$$ref":"#/components/schemas/Assertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/IdentityAssertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIdentityAssertions"},"judgements":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","disposition","disposition_name","id","observable","priority","schema_version","severity","source","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"reason_uri":{"type":"string","description":"A URI","example":"string"},"type":{"type":"string","example":"judgement","enum":["judgement"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Matches :disposition_name as in {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","format":"int64","example":1,"enum":[1,4,3,2,5]},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"disposition_name":{"type":"string","description":"String verdict identifiers.","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"priority":{"type":"integer","description":"A value 0-100 that determine the priority of a judgement. Curated feeds of black/white lists, for example known good products within your organizations, should use a 95. All automated systems should use a priority of 90, or less. Human judgements should have a priority of 100, so that humans can always override machines.","format":"int64","example":10},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]}},"additionalProperties":false,"$$ref":"#/components/schemas/Judgement"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataJudgements"},"malwares":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The type of malware being described.","example":["adware"],"items":{"type":"string"}},"abstraction_level":{"type":"string","description":"Malware abstraction level.","example":"family","enum":["family","version","variant"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"malware","enum":["malware"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of Kill Chain Phases for which this Malware can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Malware"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataMalwares"},"incidents":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","id","incident_time","schema_version","status","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"assignees":{"type":"array","description":"A set of owners assigned to this incident.","example":["string"],"items":{"type":"string"}},"meta":{"type":"object","additionalProperties":{"type":"object","description":"custom field relevant to attach meta data to.","example":{},"x-oneOf":[{"example":"string","type":"string"},{"example":10,"type":"number","format":"double"},{"example":"2016-01-01T01:01:01.000Z","type":"string","format":"date-time"},{"example":"keyword","type":"string"},{"example":true,"type":"boolean"}]},"description":"metadata associated to the incident.","example":{"keyword":{}},"$$ref":"#/components/schemas/MetaData"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"incident","enum":["incident"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"incident_time":{"required":["opened"],"type":"object","properties":{"opened":{"type":"string","description":"Time the incident was first opened.","format":"date-time","example":"2016-01-01T01:01:01Z"},"discovered":{"type":"string","description":"Time the incident was first discovered.","format":"date-time","example":"2016-01-01T01:01:01Z"},"reported":{"type":"string","description":"Time the incident was first reported.","format":"date-time","example":"2016-01-01T01:01:01Z"},"remediated":{"type":"string","description":"Time that the remediation of the damage from the incident was completed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"closed":{"type":"string","description":"Time that the incident was last closed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"rejected":{"type":"string","description":"Time that the incident was first rejected.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Relevant time values associated with this Incident.","example":{"opened":"2016-01-01T01:01:01.000Z","discovered":"2016-01-01T01:01:01.000Z","reported":"2016-01-01T01:01:01.000Z","remediated":"2016-01-01T01:01:01.000Z","closed":"2016-01-01T01:01:01.000Z","rejected":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/IncidentTime"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"discovery_method":{"type":"string","description":"Identifies how the incident was discovered.","example":"Agent Disclosure"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Specifies the suspected intended effect of this incident","example":"Account Takeover"},"categories":{"type":"array","description":"A set of categories for this incident.","example":["Attrition"],"items":{"type":"string"}},"status":{"type":"string","description":"The `status` field represents the current state of an incident within the incident management process. Its values help in tracking and reporting the progress of the incident from its discovery to its resolution.","example":"Closed","enum":["New","Closed","Open: Recovered","Closed: Other","Hold: Internal","Hold: Legal","Closed: Under Review","Rejected","Open","Restoration Achieved","Incident Reported","Closed: Suspected","Stalled","Open: Contained","Closed: Near-Miss","Hold: External","Containment Achieved","New: Processing","Closed: Confirmed Threat","Closed: False Positive","Open: Reported","Open: Investigating","Hold","New: Presented"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"promotion_method":{"type":"string","description":"Describes method for promoting an Incident, whether manually or automatically. An Incident may be created manually by a SOAR analyst or SOC operator, or through an automated correlation or aggregation rule or engine that matches a specific set of events or alerts, and promotes them to Incident(s).","example":"Automated","enum":["Automated","Manual"]},"severity":{"type":"string","description":"Represents the potential impact of an incident on an organization's security posture and business operations. It helps organizations prioritize and allocate resources for incident response based on the severity level of the incident \nIt helps analysts and incident handlers prioritize incidents by indicating the level of risk and potential impact associated with the incident. This enables organizations to allocate resources efficiently and address the most critical incidents first.\nCan also be used to generate reports and metrics for measuring the effectiveness of the incident response process and to identify trends and patterns in the threat landscape.\nIt is important to note that the `severity` field is subjective and can be interpreted differently by different organizations or analysts. Therefore, it should be used in conjunction with other intelligence attributes, such as the `confidence` field, to provide a more comprehensive view of the incident.","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"scores":{"type":"object","additionalProperties":{"type":"number","description":"Field is used to indicate the severity or impact of the threat represented by the incident.\nIt's an open-type dictionary object with score types and numeric value of the score.\n\nFor example, systems can have the following score types:\n\n- `asset` - assesses the potential damage or harm that the threat can cause to the affected asset(s). The scale ranges from 0 to 10, with 10 indicating the highest potential harm. \n\n- `global` - assesses the overall impact or significance of the threat to the organization or wider community. The scale ranges from 0 to 1000, with 1000 indicating the highest impact.\n\n- `ttp` - a measure of the threat actor's proficiency in utilizing TTPs. Typically, ranges from 0-100, with a higher score indicating a greater threat or concern.","format":"double","example":10},"description":"Used to indicate the severity or impact score of the threat represented by the incident.","example":{"asset":10},"$$ref":"#/components/schemas/IncidentScores"},"client_id":{"type":"string"},"techniques":{"type":"array","description":"Represents the specific methods or actions used by an attacker to carry out an offensive maneuver or achieve their goals.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Represents the level of certainty or trustworthiness associated with the incident. It denotes the reliability of the intelligence associated with the incident.\nThe `confidence` field can take on several values, including:\n- `info`: Indicates that the incident information is based on sources with no previous track record or there is no track record for the source reporting the incident.\n- `low`: Indicates that the incident information is based on sources with a questionable track record or there is limited information about the accuracy of the source.\n- `medium`: Indicates that the incident information is based on sources with a mixed track record or of uncertain reliability.\n- `high`: Indicates that the incident information is based on sources with a proven track record and high degree of reliability.\nThe `confidence` field can be used to indicate the level of trust and confidence that can be attributed to the incident, and it may impact how the incident is prioritized, analyzed and addressed. It can also help in the decision-making process associated with the incident response activities.\nIt is important to note that the `confidence` field is subjective and can be interpreted differently by different organizations or analysts. As such, it is often used in conjunction with other intelligence attributes, such as the `severity` field, to provide a more complete picture of the incident.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"tactics":{"type":"array","description":"Represents the offensive techniques, approaches, or procedures that an adversary may use to achieve their objectives during an attack. It helps in understanding the intent and capabilities of the adversary and can be used to identify indicators of attack (IoAs) or indicators of compromise (IoCs) that are associated with the adversary's tactics.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Incident"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIncidents"},"sightings":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","count","id","observed_time","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"relations":{"type":"array","description":"Provide any context we can about where the observable came from.","example":[{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}}],"items":{"required":["origin","related","relation","source"],"type":"object","properties":{"origin":{"type":"string","example":"string"},"origin_uri":{"type":"string","description":"A URI","example":"string"},"relation":{"type":"string","example":"Allocated"},"relation_info":{"type":"object","additionalProperties":{"type":"object","example":{}},"example":{"keyword":{}},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightingsDocsRelationsRelationInfo"},"source":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"related":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"additionalProperties":false,"description":"A relation inside a Sighting.","example":{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}},"$$ref":"#/components/schemas/ObservedRelation"}},"sensor_coordinates":{"required":["observables","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the device that made the sighting (sensor) and contains identifying observables for the sensor.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"os":"string"},"$$ref":"#/components/schemas/SensorCoordinates"},"observables":{"type":"array","description":"The object(s) of interest.","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"type":{"type":"string","example":"sighting","enum":["sighting"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"targets":{"type":"array","description":"May include one or more targets that observed the associated indicator. Targets can include network devices, host devices, or other entities that are capable of detecting indicators of compromise.\n\nCan be used to assess the scope of potential threats, helping analysts understand which devices or components of the network may be vulnerable to attack. For example, if a particular malware strain is detected on several different systems within an organization, the `targets` field may indicate which systems are affected and which may need to be isolated or patched to prevent further spread.","example":[{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"}],"items":{"required":["observables","observed_time","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the target of the sighting and contains identifying observables for the target.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"},"$$ref":"#/components/schemas/IdentitySpecification"}},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"resolution":{"type":"string","description":"Represents the disposition or actions taken on the associated threat intelligence.","example":"detected"},"internal":{"type":"boolean","description":"If `true`, indicates that the sighting was reported from internal sources, such as an organization's own internal security tools or SOC.\n Internal sightings are often considered more reliable and actionable than external sightings, which are reported from external sources and may have a lower level of trustworthiness. Internal sightings can provide more context and can help identify potential threats that are unique to a particular environment or organization.\n Internal sightings can also help organizations prioritize their security response efforts by identifying threats that are specific to their environment and may not yet be widely known.","example":false},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"count":{"type":"integer","description":"The number of times an indicator was observed within a certain period of time.\nFor example, if an IP address associated with known malicious activity is observed once within a period of time, it may indicate a low-level threat. However, if the same IP address is observed multiple times within a short time frame, it may indicate a more severe and persistent threat.\nIt can also be used to prioritize security alerts and indicate the urgency of a response. High counts indicate that an indicator is actively being used in a larger campaign, while low counts may indicate isolated incidents.","format":"int64","example":10},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"context":{"type":"object","properties":{"http_events":{"type":"array","description":"a list of `HTTPType`","example":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"items":{"required":["host","process_id","process_name","time","traffic","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"method":{"type":"string","example":"CONNECT","enum":["OPTIONS","PATCH","TRACE","HEAD","POST","CONNECT","GET","PUT"]},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"HTTPEvent","enum":["HTTPEvent"]},"host":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"query":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"encrypted":{"type":"boolean","example":true},"url_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10},"$$ref":"#/components/schemas/HTTPType"}},"process_create_events":{"type":"array","description":"a list of `ProcessCreate`","example":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"items":{"required":["process_id","process_name","time","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"parent_process_guid":{"type":"integer","format":"int64","example":10},"process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_size":{"type":"integer","format":"int64","example":10},"process_size":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"ProcessCreateEvent","enum":["ProcessCreateEvent"]},"parent_process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_creation_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"},"$$ref":"#/components/schemas/ProcessCreateType"}},"registry_delete_events":{"type":"array","description":"a list of `RegistryDeleteType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryDeleteEvent","enum":["RegistryDeleteEvent"]},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"},"$$ref":"#/components/schemas/RegistryDeleteType"}},"file_modify_events":{"type":"array","description":"a list of `FileModifyType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileModifyEvent","enum":["FileModifyEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileModifyType"}},"registry_set_events":{"type":"array","description":"a list of `RegistrySetType`","example":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_value","time","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"registry_data":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"RegistrySetEvent","enum":["RegistrySetEvent"]},"registry_data_length":{"type":"integer","format":"int64","example":10},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"},"$$ref":"#/components/schemas/RegistrySetType"}},"file_create_events":{"type":"array","description":"a list of `FileCreateType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileCreateEvent","enum":["FileCreateEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileCreateType"}},"registry_create_events":{"type":"array","description":"a list of `RegistryCreateType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryCreateEvent","enum":["RegistryCreateEvent"]}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"},"$$ref":"#/components/schemas/RegistryCreateType"}},"library_load_events":{"type":"array","description":"a list of `LibraryLoadType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"items":{"required":["dll_library_name","dll_library_path","process_id","process_name","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"LibraryLoadEvent","enum":["LibraryLoadEvent"]},"dll_library_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"dll_library_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"},"$$ref":"#/components/schemas/LibraryLoadType"}},"file_move_events":{"type":"array","description":"a list of `FileMoveType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"items":{"required":["file_name","file_path","new_name","old_name","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileMoveEvent","enum":["FileMoveEvent"]},"old_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"new_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"},"$$ref":"#/components/schemas/FileMoveType"}},"file_delete_events":{"type":"array","description":"a list of `FileDeleteType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileDeleteEvent","enum":["FileDeleteEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileDeleteType"}},"netflow_events":{"type":"array","description":"a list of `NetflowType`","example":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"items":{"required":["process_id","process_name","time","traffic","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_in":{"type":"integer","format":"int64","example":10},"process_guid":{"type":"integer","format":"int64","example":10},"process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"flow_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"NetflowEvent","enum":["NetflowEvent"]},"process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_out":{"type":"integer","format":"int64","example":10},"process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"},"$$ref":"#/components/schemas/NetflowType"}},"registry_rename_events":{"type":"array","description":"a list of `RegistryRenameType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_old_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryRenameEvent","enum":["RegistryRenameEvent"]},"registry_old_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"},"$$ref":"#/components/schemas/RegistryRenameType"}}},"additionalProperties":false,"description":"Context including the event type that best fits the type of the sighting.","example":{"http_events":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"process_create_events":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"registry_delete_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"file_modify_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_set_events":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"file_create_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_create_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"library_load_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"file_move_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"file_delete_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"netflow_events":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"registry_rename_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}]},"$$ref":"#/components/schemas/Context"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"sensor":{"type":"string","description":"The OpenC2 Actuator name that best fits the device that is creating this sighting (e.g. network.firewall)","example":"endpoint"},"data":{"required":["columns","rows"],"type":"object","properties":{"columns":{"type":"array","description":"an ordered list of column definitions","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"rows":{"type":"array","description":"an ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10}},"additionalProperties":false,"description":"An embedded data table for the Sighting.","example":{"columns":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"rows":[[{}]],"row_count":10},"$$ref":"#/components/schemas/SightingDataTable"}},"additionalProperties":false,"$$ref":"#/components/schemas/Sighting"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightings"},"relationships":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","relationship_type","schema_version","source_ref","target_ref","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"target_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"type":{"type":"string","example":"relationship","enum":["relationship"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"source_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"relationship_type":{"type":"string","example":"attributed-to"}},"additionalProperties":false,"$$ref":"#/components/schemas/Relationship"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataRelationships"},"vulnerabilities":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Various sources of vulnerability information can be used, including third-party resources like the National Vulnerability Database (NVD) and the Common Vulnerabilities and Exposures (CVE) database. The platform then analyzes this data and provides the user with relevant details such as the severity of the vulnerability, the affected systems, and remediation recommendations. \n\n Based on this information, the user can prioritize patching and other mitigation strategies to reduce the risk of potential attacks.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"}},"additionalProperties":false,"$$ref":"#/components/schemas/Vulnerability"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVulnerabilities"},"coas":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"stage":{"type":"string","description":"Specifies what stage in the cyber threat management lifecycle this Course Of Action is relevant to.","example":"Containment","enum":["Identification","Lessons Learned","Remedy","Preparation","Containment","Response","Eradication","Recovery"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"efficacy":{"type":"string","description":"Effectiveness of this course of action in achieving its targeted objective.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","example":"coa","enum":["coa"]},"created":{"type":"string","format":"date-time"},"related_COAs":{"type":"array","description":"Identifies or characterizes relationships to one or more related courses of action.","example":[{"confidence":"High","source":"string","relationship":"string","COA_id":"string"}],"items":{"required":["COA_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"COA_id":{"type":"string","description":"A URI leading to a COA.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","COA_id":"string"},"$$ref":"#/components/schemas/RelatedCOA"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"coa_type":{"type":"string","description":"The type of this COA","example":"Diplomatic Actions","enum":["Diplomatic Actions","Physical Access Restrictions","Policy Actions","Internal Blocking","Playbook","Redirection","Phase","Eradication","Public Disclosure","Monitoring","Patching","Logical Access Restrictions","Redirection (Honey Pot)","Rebuilding","Perimeter Blocking","Hardening","Other","Training","Task"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"objective":{"type":"array","description":"Characterizes the objective to provide guidance on how to mitigate a security incident that has been identified.","example":["string"],"items":{"type":"string"}},"cost":{"type":"string","description":"Characterizes the estimated cost for applying this course of action.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"open_c2_coa":{"required":["action","type"],"type":"object","properties":{"type":{"type":"string","example":"structured_coa","enum":["structured_coa"]},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"action":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"alert","enum":["stop","save","delete","remediate","redirect","alert","query","augment","snapshot","update","allow","scan","investigate","modify","sync","start","pause","deny","substitute","distill","move","restart","other","detonate","response","set","notify","report","restore","get","throttle","mitigate","resume","locate","contain"]}},"additionalProperties":false,"example":{"type":"alert"},"$$ref":"#/components/schemas/ActionType"},"target":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"amp_computer_guid"},"specifiers":{"type":"string","description":"Observable types that can be acted upon.","example":"string"}},"additionalProperties":false,"example":{"type":"amp_computer_guid","specifiers":"string"},"$$ref":"#/components/schemas/TargetType"},"actuator":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"endpoint","enum":["endpoint.sensor","process.network-scanner","network.switch","network.security_manager","process.vulnerability-scanner","network.hub","network.ids","network.firewall","process","network.sense_making","process.sandbox","network.modem","process.email-service","process.dns-server","network.vpn","process.connection-scanner","network.nic","endpoint.printer","network.gateway","process.reputation-service","process.remediation-service","network","process.virtualization-service","network.ips","endpoint.smart-meter","endpoint.digital-telephone-handset","endpoint.workstation","endpoint.server","network.wap","endpoint.laptop","process.aaa-server","process.directory-service","endpoint.pos-terminal","network.bridge","other","process.file-scanner","network.proxy","endpoint","process.location-service","network.sensor","endpoint.smart-phone","network.hips","process.anti-virus-scanner","endpoint.tablet","network.guard","network.router"]},"specifiers":{"type":"array","description":"List of additional properties describing the actuator.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"type":"endpoint","specifiers":["string"]},"$$ref":"#/components/schemas/ActuatorType"},"modifiers":{"type":"object","properties":{"response":{"type":"string","example":"acknowledge","enum":["query","status","acknowledge","command-ref"]},"method":{"type":"array","example":["acl"],"items":{"type":"string","enum":["blackhole","unauthenticated","suspend","graceful","hibernate","whitelist","honeypot","immediate","spawn","blacklist","acl","segmentation","authenticated"]}},"additional_properties":{"required":["context"],"type":"object","properties":{"context":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"context":"string"},"$$ref":"#/components/schemas/AdditionalProperties"},"time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"frequency":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"duration":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"source":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"search":{"type":"string","example":"cve","enum":["vendor_bulletin","patch","signature","cve"]},"option":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"location":{"type":"string","example":"internal","enum":["internal","perimeter"]},"delay":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"destination":{"type":"string","example":"copy-to","enum":["modify-to","set-to","copy-to","move-to","save-to","restore-point","report-to"]}},"additionalProperties":false,"example":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"},"$$ref":"#/components/schemas/ModifierType"}},"additionalProperties":false,"example":{"type":"structured_coa","id":"string","action":{"type":"alert"},"target":{"type":"amp_computer_guid","specifiers":"string"},"actuator":{"type":"endpoint","specifiers":["string"]},"modifiers":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"}},"$$ref":"#/components/schemas/OpenC2COA"},"structured_coa_type":{"type":"string","example":"openc2","enum":["openc2"]},"impact":{"type":"string","description":"Characterizes the estimated impact of applying this course of action.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/COA"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCoas"}},"additionalProperties":false,"$$ref":"#/components/schemas/ModuleObserveBundle"}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleData"}},"errors":{"type":"array","items":{"required":["code","message","module_instance_id","module_type_id","type"],"type":"object","properties":{"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"code":{"type":"string"},"message":{"type":"string"},"type":{"type":"string","enum":["fatal","warning","error"]},"module":{"type":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/ErrorMessage"}}},"additionalProperties":false,"example":{"data":[{"module":"Sample Module","module_instance_id":"da033b3c-81da-4118-b73a-f03feb3adecf","module_type_id":"c84f54db-c187-4cab-8751-2b39b007ee55","data":{"verdicts":{"count":2,"docs":[{"type":"verdict","disposition":2,"observable":{"value":"https://ilo.brenz.pl/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.410Z","end_time":"2023-03-11T13:36:23.410Z"}},{"type":"verdict","disposition":2,"observable":{"value":"http://ilo.brenz.pl/favicon.ico/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.420Z","end_time":"2023-03-11T13:36:23.420Z"}}]}}}]},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundle"}},"application/transit+msgpack":{"schema":{"type":"object","properties":{"data":{"type":"array","items":{"required":["data","module","module_instance_id","module_type_id"],"type":"object","properties":{"module":{"type":"string"},"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"data":{"type":"object","properties":{"tools":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The kind(s) of tool(s) being described.","example":["credential-exploitation"],"items":{"type":"string"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"tool","enum":["tool"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tool_version":{"type":"string","description":"The version identifier associated with the Tool.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of kill chain phases for which this Tool can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Tool"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataTools"},"indicators":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","producer","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"tags":{"type":"array","description":"Descriptors for this indicator.","example":["string"],"items":{"type":"string"}},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"producer":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","description":"The fixed value indicator","example":"indicator","enum":["indicator"]},"created":{"type":"string","format":"date-time"},"test_mechanisms":{"type":"array","description":"Test Mechanisms effective at identifying the cyber Observables specified in this cyber threat Indicator.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"composite_indicator_expression":{"required":["indicator_ids","operator"],"type":"object","properties":{"operator":{"type":"string","example":"and","enum":["not","or","and"]},"indicator_ids":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"operator":"and","indicator_ids":["string"]},"$$ref":"#/components/schemas/CompositeIndicatorExpression"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"likely_impact":{"type":"string","description":"Likely potential impact within the relevant context if this Indicator were to occur.","example":"string"},"indicator_type":{"type":"array","description":"Specifies the type or types for this Indicator.","example":["Anonymization"],"items":{"type":"string","enum":["File Hash Watchlist","Private Threat Feed","IMEI Watchlist","Malicious E-mail","Exfiltration","C2","URL Watchlist","IMSI Watchlist","Malware Artifacts","Domain Watchlist","Anonymization","Host Characteristics","IP Watchlist","Compromised PKI Certificate","Login Name"]}},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"Relevant kill chain phases indicated by this Indicator.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"negate":{"type":"boolean","description":"Specifies the absence of the pattern.","example":true},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"level of confidence held in the accuracy of this Indicator.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"specification":{"type":"object","example":{},"x-oneOf":[{"required":["judgements","required_judgements","type"],"type":"object","properties":{"type":{"type":"string","example":"Judgement","enum":["Judgement"]},"judgements":{"type":"array","example":["string"],"items":{"type":"string"}},"required_judgements":{"type":"array","example":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}],"items":{"required":["judgement_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"},"$$ref":"#/components/schemas/RelatedJudgement"}}},"additionalProperties":false,"description":"An indicator based on a list of judgements. If any of the Observables in it's judgements are encountered, than it may be matches against. If there are any required judgements, they all must be matched in order for the indicator to be considered a match.","example":{"type":"Judgement","judgements":["string"],"required_judgements":[{"confidence":"High","source":"string","relationship":"string","judgement_id":"string"}]},"$$ref":"#/components/schemas/JudgementSpecification"},{"required":["type","variables"],"type":"object","properties":{"type":{"type":"string","example":"ThreatBrain","enum":["ThreatBrain"]},"query":{"type":"string","example":"string"},"variables":{"type":"array","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"description":"An indicator which runs in threatbrain...","example":{"type":"ThreatBrain","query":"string","variables":["string"]},"$$ref":"#/components/schemas/ThreatBrainSpecification"},{"required":["snort_sig","type"],"type":"object","properties":{"type":{"type":"string","example":"Snort","enum":["Snort"]},"snort_sig":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"Snort","snort_sig":"string"},"$$ref":"#/components/schemas/SnortSpecification"},{"required":["SIOC","type"],"type":"object","properties":{"type":{"type":"string","example":"SIOC","enum":["SIOC"]},"SIOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which runs in snort...","example":{"type":"SIOC","SIOC":"string"},"$$ref":"#/components/schemas/SIOCSpecification"},{"required":["open_IOC","type"],"type":"object","properties":{"type":{"type":"string","example":"OpenIOC","enum":["OpenIOC"]},"open_IOC":{"type":"string","example":"string"}},"additionalProperties":false,"description":"An indicator which contains an XML blob of an openIOC indicator.","example":{"type":"OpenIOC","open_IOC":"string"},"$$ref":"#/components/schemas/OpenIOCSpecification"}]}},"additionalProperties":false,"$$ref":"#/components/schemas/Indicator"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIndicators"},"attack_patterns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"abstraction_level":{"type":"string","description":"The CAPEC abstraction level for patterns describing techniques to attack a system.","example":"aggregate","enum":["detailed","standard","aggregate","meta","category"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"attack-pattern","enum":["attack-pattern"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"x_mitre_platforms":{"type":"array","description":"ATT&CK Technique.Platforms.","example":["string"],"items":{"type":"string"}},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"x_mitre_data_sources":{"type":"array","description":"ATT&CK Technique.Data Sources.","example":["string"],"items":{"type":"string"}},"kill_chain_phases":{"type":"array","description":"A kill chain is a series of steps that an attacker must go through to successfully achieve their objective. The concept was originally developed by the military, but has been adapted to the cybersecurity field to describe the steps an attacker goes through to compromise a target system and achieve their goal.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"x_mitre_contributors":{"type":"array","description":"ATT&CK Technique.Contributors.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/AttackPattern"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataAttackPatterns"},"weaknesses":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Should be short and limited to the key points that define this weakness.","example":"string"},"background_details":{"type":"string","description":"Information that is relevant but not related to the nature of the weakness itself.","example":"string"},"paradigms":{"type":"array","description":"Applicable paradigms.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Paradigm name (Client Server, Mainframe)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Paradigm"}},"abstraction_level":{"type":"string","description":"Refers to the level of abstraction or granularity used to describe the weakness. It helps to categorize the vulnerability based on the level of detail provided.","example":"Base","enum":["Variant","Class","Base","Compound"]},"architectures":{"type":"array","description":"Applicable architectures.","example":[{"prevalence":"Often","name":"string","class":"Embedded"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Architecture name (ARM, x86, ...)","example":"string"},"class":{"type":"string","description":"Class of architecture","example":"Embedded"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Embedded"},"$$ref":"#/components/schemas/Architecture"}},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"alternate_terms":{"type":"array","description":"Indicates one or more other names used to describe this weakness.","example":[{"term":"string","description":"string"}],"items":{"required":["term"],"type":"object","properties":{"term":{"type":"string","description":"The actual alternate term.","example":"string"},"description":{"type":"string","description":"Provides context for the alternate term by which this weakness may be known.","example":"string"}},"additionalProperties":false,"example":{"term":"string","description":"string"},"$$ref":"#/components/schemas/AlternateTerm"}},"likelihood":{"type":"string","description":"Likelihood of exploit.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","description":"The fixed value weakness","example":"weakness","enum":["weakness"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"functional_areas":{"type":"array","description":"Identifies the functional area of the software in which the weakness is most likely to occur.","example":["Authentication"],"items":{"type":"string"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"modes_of_introduction":{"type":"array","description":"Information about how and when a given weakness may be introduced.","example":[{"phase":"Architecture and Design","note":"string"}],"items":{"required":["phase"],"type":"object","properties":{"phase":{"type":"string","description":"Identifies the point in the software life cycle at which the weakness may be introduced.","example":"Architecture and Design"},"note":{"type":"string","description":"Provides a typical scenario related to introduction during the given phase.","example":"string"}},"additionalProperties":false,"example":{"phase":"Architecture and Design","note":"string"},"$$ref":"#/components/schemas/ModeOfIntroduction"}},"structure":{"type":"string","description":"Defines the structural nature of the weakness.","example":"Chain","enum":["Chain","Simple","Composite"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"notes":{"type":"array","description":"Provides any additional comments about the weakness.","example":[{"content":"","id":"","note_class":"","related_entities":[],"schema_version":"1.3.18","type":"note"}],"items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}},"common_consequences":{"type":"array","description":"Refers to the typical or expected negative effects that can result from exploiting the weakness. This could include anything from unauthorized access to data, denial of service, system crashes or other things.","example":[{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"}],"items":{"required":["scopes"],"type":"object","properties":{"scopes":{"type":"array","description":"Identifies the security property that is violated.","example":["Access Control"],"items":{"type":"string"}},"impacts":{"type":"array","description":"Describes the technical impact that arises if an adversary succeeds in exploiting this weakness.","example":["Alter Execution Logic"],"items":{"type":"string"}},"likelihood":{"type":"string","description":"How likely the specific consequence is expected to be seen relative to the other consequences.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"note":{"type":"string","description":"Additional commentary about a consequence.","example":"string"}},"additionalProperties":false,"example":{"scopes":["Access Control"],"impacts":["Alter Execution Logic"],"likelihood":"High","note":"string"},"$$ref":"#/components/schemas/Consequence"}},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"detection_methods":{"type":"array","description":"Identifies methods that may be employed to detect this weakness, including their strengths and limitations.","example":[{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"}],"items":{"required":["description","method"],"type":"object","properties":{"method":{"type":"string","description":"Identifies the particular detection method being described.","example":"Architecture or Design Review"},"description":{"type":"string","description":"Provides some context of how this method can be applied to a specific weakness.","example":"string"},"effectiveness":{"type":"string","description":"How effective the detection method may be in detecting the associated weakness.","example":"High"},"effectiveness_notes":{"type":"string","description":"Provides additional discussion of the strengths and shortcomings of this detection method.","example":"string"}},"additionalProperties":false,"example":{"method":"Architecture or Design Review","description":"string","effectiveness":"High","effectiveness_notes":"string"},"$$ref":"#/components/schemas/DetectionMethod"}},"operating_systems":{"type":"array","description":"Applicable operating systems.","example":[{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"version":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"cpe_id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"class":{"type":"string","description":"Class of Operating System.","example":"Android"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","version":"string","cpe_id":"string","class":"Android"},"$$ref":"#/components/schemas/OperatingSystem"}},"client_id":{"type":"string"},"affected_resources":{"type":"array","description":"Identifies system resources that can be affected by an exploit of this weakness.","example":["CPU"],"items":{"type":"string"}},"languages":{"type":"array","description":"Applicable Languages.","example":[{"prevalence":"Often","name":"string","class":"Assembly"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Language name (Clojure, Java, ...)","example":"string"},"class":{"type":"string","description":"Class of language.","example":"Assembly"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string","class":"Assembly"},"$$ref":"#/components/schemas/Language"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"potential_mitigations":{"type":"array","description":"Describes potential mitigations associated with a weakness.","example":[{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"}],"items":{"required":["description"],"type":"object","properties":{"description":{"type":"string","description":"A description of this individual mitigation including any strengths and shortcomings of this mitigation for the weakness.","example":"string"},"phases":{"type":"array","description":"Indicates the development life cycle phase during which this particular mitigation may be applied.","example":["Architecture and Design"],"items":{"type":"string"}},"strategy":{"type":"string","description":"A general strategy for protecting a system to which this mitigation contributes.","example":"Attack Surface Reduction"},"effectiveness":{"type":"string","description":"Summarizes how effective the mitigation may be in preventing the weakness.","example":"Defense in Depth"},"effectiveness_notes":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"}},"additionalProperties":false,"example":{"description":"string","phases":["Architecture and Design"],"strategy":"Attack Surface Reduction","effectiveness":"Defense in Depth","effectiveness_notes":"string"},"$$ref":"#/components/schemas/Mitigation"}},"technologies":{"type":"array","description":"Applicable technologies.","example":[{"prevalence":"Often","name":"string"}],"items":{"required":["prevalence"],"type":"object","properties":{"prevalence":{"type":"string","description":"Defines the different regularities that guide the applicability of platforms.","example":"Often","enum":["Undetermined","Sometimes","Often","Rarely"]},"name":{"type":"string","description":"Technology name (Web Server, Web Client)","example":"string"}},"additionalProperties":false,"example":{"prevalence":"Often","name":"string"},"$$ref":"#/components/schemas/Technology"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Weakness"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataWeaknesses"},"feedbacks":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["entity_id","feedback","id","reason","schema_version","type"],"type":"object","properties":{"feedback":{"type":"integer","format":"int64","example":-1,"enum":[0,1,-1]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"feedback","enum":["feedback"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Feedback"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataFeedbacks"},"verdicts":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["disposition","observable","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"type":{"type":"string","example":"verdict","enum":["verdict"]},"created":{"type":"string","format":"date-time"},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Numeric verdict identifiers.","format":"int64","example":1,"enum":[1,4,3,2,5]},"disposition_name":{"type":"string","description":"The disposition_name field is optional, but is intended to be shown to a user. Applications must therefore remember the mapping of numbers to human words, as in: {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"client_id":{"type":"string"},"judgement_id":{"type":"string","description":"A URI leading to a judgement.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/Verdict"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVerdicts"},"campaigns":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["campaign_type","description","id","schema_version","short_description","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"campaign","enum":["campaign"]},"created":{"type":"string","format":"date-time"},"campaign_type":{"type":"string","description":"String value that describes the type of campaign. For example, a campaign type could be 'Ransomware', 'Advanced Persistent Threat', 'Business Email Compromise', 'Phishing', etc. ","example":"string"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"activity":{"type":"array","description":"Used to capture specific activities or tactics associated with the campaign.\nThe 'activity' field is an array of objects, and each element represents a specific activity and time associated with the campaign. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc. By capturing these activities analysts can identify the specific tactics used by the threat actor(s) behind the campaign.","example":[{"date_time":"2016-01-01T01:01:01.000Z","description":"string"}],"items":{"required":["date_time","description"],"type":"object","properties":{"date_time":{"type":"string","description":"Specifies the date and time at which the activity occured.","format":"date-time","example":"2016-01-01T01:01:01Z"},"description":{"type":"string","description":"A description of the activity.","example":"string"}},"additionalProperties":false,"description":"Captures the specific activities or tactics associated with the entity. Examples of activities may include malicious software delivery, command and control communication, network reconnaissance, data exfiltration, etc.","example":{"date_time":"2016-01-01T01:01:01.000Z","description":"string"},"$$ref":"#/components/schemas/Activity"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"array","description":"Characterizes the intended effect of this cyber threat campaign.","example":["Account Takeover"],"items":{"type":"string"}},"status":{"type":"string","description":"Indicates current Status of the Campaign. \n\nCan have one of the following values: \n\n- Ongoing: Indicates that the campaign is currently active and ongoing. For example, a mass phishing campaign that is actively targeting users is considered 'ongoing'.\n\n- Historic: Campaign has already occurred and is now in the past.\n\n- Future: This indicates that a campaign is planned or expected to occur in the future. For example, a threat actor may announce their intention to launch a specific cyberattack campaign at a future date.","example":"Future","enum":["Historic","Future","Ongoing"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Level of confidence held in the characterization of this Campaign.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"names":{"type":"array","description":"Used to capture alternate names or aliases associated with the campaign. A cyberattack campaign may have multiple names or aliases depending on the group or actor(s) behind the attack, e.g., 'Wannacry' is also known as 'WannaCrypt', 'WCry', 'Wanna Decryptor', etc.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Campaign"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCampaigns"},"actors":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","short_description","source","title","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"motivation":{"type":"string","description":"The reason or purpose behind the malicious activity attributed to this Actor. By understanding a threat actor's motivation, analysts can better predict the attacker's behavior and anticipate future malicious actions.","example":"Ego"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["description","related_identities"],"type":"object","properties":{"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"related_identities":{"type":"array","description":"Identifies other entity Identities related to this Identity.","example":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}],"items":{"required":["identity"],"type":"object","properties":{"identity":{"type":"string","description":"The reference (URI) of the related Identity object.","example":"string"},"confidence":{"type":"string","description":"Specifies the level of confidence in the assertion of the relationship between the two objects.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"information_source":{"type":"string","description":"Specifies the source of the information about the relationship between the two components.","example":"string"},"relationship":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes a related Identity","example":{"identity":"string","confidence":"High","information_source":"string","relationship":"string"},"$$ref":"#/components/schemas/RelatedIdentity"}}},"additionalProperties":false,"description":"Can contain information such as the name of the attacker, the group or organization they belong to, or any other identifier that can help in the attribution process.","example":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"$$ref":"#/components/schemas/Identity"},"sophistication":{"type":"string","description":"Represents the level of expertise and skill that the threat actor has displayed in their malicious activities. Can help security analysts assess the potential impact of an attacker's TTPs and determine the potential attack surface. \n\nFor example, a threat actor with a low sophistication level may primarily rely on off-the-shelf malware and attack tools, while an attacker with high sophistication may use custom tools with advanced evasion techniques, zero-day exploits, and sophisticated methods for command and control of their malware. \n\nThe sophistication level of an attacker can also be inferred based on several factors such as the complexity of attacks, the attacker's knowledge of the targeted organization's systems, and the attacker's ability to remain undetected.\n\nIf an attacker shows a high level of sophistication in reconnaissances, social engineering, and phishing, then the attacker may have a good knowledge of the targeted organization and its employees. This means that the attacker may be more successful in infiltrating the organization's network and compromising its systems.","example":"Aspirant","enum":["Aspirant","Innovator","Practitioner","Novice","Expert"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"planning_and_operational_support":{"type":"string","description":"Provides information about the resources and capabilities of the attacker that could be used to assist in planning and operations related to the threat.\n\n It can be used to describe Infrastructure, Tools, Techniques, and Capabilities used by the threat actor.","example":"string"},"type":{"type":"string","example":"actor","enum":["actor"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Represents the desired outcome or impact the threat actor is trying to achieve through their malicious activities. \n\n Helps security analysts to understand the attacker's goals beyond the immediate impact of the attack. By understanding the intended effect, analysts can draw connections between seemingly unrelated attacks and build a more complete understanding of an attacker's long-term goals and motivations.","example":"Account Takeover"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"aliases":{"type":"array","description":"A list of other names that this Threat Actor is believed to use.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"This field can help analysts decide how much trust they can put in the information provided by the threat intelligence sources.\n\nFor example, an Actor entity can have high confidence if the organization's security researchers have been tracking it for a long time and have gathered a significant amount of intelligence about it through various sources, such as analysis of malware, network traffic, and human intelligence. In contrast, low confidence may indicate the organization has only seen limited or circumstantial evidence.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Actor"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataActors"},"data_tables":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["columns","id","rows","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"columns":{"type":"array","description":"An ordered list of column definitions.","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"type":{"type":"string","example":"data-table","enum":["data-table"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"rows":{"type":"array","description":"An ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/DataTable"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataDataTables"},"notes":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["content","id","note_class","related_entities","schema_version","type"],"type":"object","properties":{"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"content":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"note_class":{"type":"string","example":"keyword"},"type":{"type":"string","example":"note","enum":["note"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"author":{"type":"string","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"related_entities":{"type":"array","example":[{"entity_type":"string","entity_id":"string"}],"items":{"required":["entity_id","entity_type"],"type":"object","properties":{"entity_type":{"type":"string","example":"string"},"entity_id":{"type":"string","description":"A URI leading to an entity.","example":"string"}},"additionalProperties":false,"example":{"entity_type":"string","entity_id":"string"},"$$ref":"#/components/schemas/NoteRelatedEntity"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Note"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataNotes"},"identity_assertions":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["assertions","id","identity","schema_version","type"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"required":["observables"],"type":"object","properties":{"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}}},"additionalProperties":false,"description":"Attributes for which the assertion is being made.","example":{"observables":[{"value":"1.2.3.4","type":"ip"}]},"$$ref":"#/components/schemas/IdentityCoordinates"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"identity-assertion","enum":["identity-assertion"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"assertions":{"type":"array","description":"Any known context about the identity attributes.","example":[{"name":"cisco:ctr:ad:host_domain_name","value":"string"}],"items":{"required":["name","value"],"type":"object","properties":{"name":{"type":"string","description":"An open vocabulary containing well known assertion types","example":"cisco:ctr:ad:host_domain_name"},"value":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"cisco:ctr:ad:host_domain_name","value":"string"},"$$ref":"#/components/schemas/Assertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/IdentityAssertion"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIdentityAssertions"},"judgements":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","disposition","disposition_name","id","observable","priority","schema_version","severity","source","type","valid_time"],"type":"object","properties":{"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"observable":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"reason_uri":{"type":"string","description":"A URI","example":"string"},"type":{"type":"string","example":"judgement","enum":["judgement"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"disposition":{"type":"integer","description":"Matches :disposition_name as in {1 \"Clean\", 2 \"Malicious\", 3 \"Suspicious\", 4 \"Common\", 5 \"Unknown\"}","format":"int64","example":1,"enum":[1,4,3,2,5]},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"reason":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"disposition_name":{"type":"string","description":"String verdict identifiers.","example":"Clean","enum":["Common","Unknown","Suspicious","Malicious","Clean"]},"priority":{"type":"integer","description":"A value 0-100 that determine the priority of a judgement. Curated feeds of black/white lists, for example known good products within your organizations, should use a 95. All automated systems should use a priority of 90, or less. Human judgements should have a priority of 100, so that humans can always override machines.","format":"int64","example":10},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]}},"additionalProperties":false,"$$ref":"#/components/schemas/Judgement"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataJudgements"},"malwares":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","labels","schema_version","short_description","title","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"labels":{"type":"array","description":"The type of malware being described.","example":["adware"],"items":{"type":"string"}},"abstraction_level":{"type":"string","description":"Malware abstraction level.","example":"family","enum":["family","version","variant"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"malware","enum":["malware"]},"created":{"type":"string","format":"date-time"},"x_mitre_aliases":{"type":"array","description":"ATT&CK Software.aliases.","example":["string"],"items":{"type":"string"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"kill_chain_phases":{"type":"array","description":"The list of Kill Chain Phases for which this Malware can be used.","example":[{"kill_chain_name":"string","phase_name":"string"}],"items":{"required":["kill_chain_name","phase_name"],"type":"object","properties":{"kill_chain_name":{"type":"string","description":"The name of the kill chain.","example":"string"},"phase_name":{"type":"string","description":"The name of the phase in the kill chain.","example":"string"}},"additionalProperties":false,"description":"The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.","example":{"kill_chain_name":"string","phase_name":"string"},"$$ref":"#/components/schemas/KillChainPhase"}},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"$$ref":"#/components/schemas/Malware"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataMalwares"},"incidents":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","id","incident_time","schema_version","status","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"assignees":{"type":"array","description":"A set of owners assigned to this incident.","example":["string"],"items":{"type":"string"}},"meta":{"type":"object","additionalProperties":{"type":"object","description":"custom field relevant to attach meta data to.","example":{},"x-oneOf":[{"example":"string","type":"string"},{"example":10,"type":"number","format":"double"},{"example":"2016-01-01T01:01:01.000Z","type":"string","format":"date-time"},{"example":"keyword","type":"string"},{"example":true,"type":"boolean"}]},"description":"metadata associated to the incident.","example":{"keyword":{}},"$$ref":"#/components/schemas/MetaData"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"type":{"type":"string","example":"incident","enum":["incident"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"incident_time":{"required":["opened"],"type":"object","properties":{"opened":{"type":"string","description":"Time the incident was first opened.","format":"date-time","example":"2016-01-01T01:01:01Z"},"discovered":{"type":"string","description":"Time the incident was first discovered.","format":"date-time","example":"2016-01-01T01:01:01Z"},"reported":{"type":"string","description":"Time the incident was first reported.","format":"date-time","example":"2016-01-01T01:01:01Z"},"remediated":{"type":"string","description":"Time that the remediation of the damage from the incident was completed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"closed":{"type":"string","description":"Time that the incident was last closed.","format":"date-time","example":"2016-01-01T01:01:01Z"},"rejected":{"type":"string","description":"Time that the incident was first rejected.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Relevant time values associated with this Incident.","example":{"opened":"2016-01-01T01:01:01.000Z","discovered":"2016-01-01T01:01:01.000Z","reported":"2016-01-01T01:01:01.000Z","remediated":"2016-01-01T01:01:01.000Z","closed":"2016-01-01T01:01:01.000Z","rejected":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/IncidentTime"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"discovery_method":{"type":"string","description":"Identifies how the incident was discovered.","example":"Agent Disclosure"},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"intended_effect":{"type":"string","description":"Specifies the suspected intended effect of this incident","example":"Account Takeover"},"categories":{"type":"array","description":"A set of categories for this incident.","example":["Attrition"],"items":{"type":"string"}},"status":{"type":"string","description":"The `status` field represents the current state of an incident within the incident management process. Its values help in tracking and reporting the progress of the incident from its discovery to its resolution.","example":"Closed","enum":["New","Closed","Open: Recovered","Closed: Other","Hold: Internal","Hold: Legal","Closed: Under Review","Rejected","Open","Restoration Achieved","Incident Reported","Closed: Suspected","Stalled","Open: Contained","Closed: Near-Miss","Hold: External","Containment Achieved","New: Processing","Closed: Confirmed Threat","Closed: False Positive","Open: Reported","Open: Investigating","Hold","New: Presented"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"promotion_method":{"type":"string","description":"Describes method for promoting an Incident, whether manually or automatically. An Incident may be created manually by a SOAR analyst or SOC operator, or through an automated correlation or aggregation rule or engine that matches a specific set of events or alerts, and promotes them to Incident(s).","example":"Automated","enum":["Automated","Manual"]},"severity":{"type":"string","description":"Represents the potential impact of an incident on an organization's security posture and business operations. It helps organizations prioritize and allocate resources for incident response based on the severity level of the incident \nIt helps analysts and incident handlers prioritize incidents by indicating the level of risk and potential impact associated with the incident. This enables organizations to allocate resources efficiently and address the most critical incidents first.\nCan also be used to generate reports and metrics for measuring the effectiveness of the incident response process and to identify trends and patterns in the threat landscape.\nIt is important to note that the `severity` field is subjective and can be interpreted differently by different organizations or analysts. Therefore, it should be used in conjunction with other intelligence attributes, such as the `confidence` field, to provide a more comprehensive view of the incident.","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"scores":{"type":"object","additionalProperties":{"type":"number","description":"Field is used to indicate the severity or impact of the threat represented by the incident.\nIt's an open-type dictionary object with score types and numeric value of the score.\n\nFor example, systems can have the following score types:\n\n- `asset` - assesses the potential damage or harm that the threat can cause to the affected asset(s). The scale ranges from 0 to 10, with 10 indicating the highest potential harm. \n\n- `global` - assesses the overall impact or significance of the threat to the organization or wider community. The scale ranges from 0 to 1000, with 1000 indicating the highest impact.\n\n- `ttp` - a measure of the threat actor's proficiency in utilizing TTPs. Typically, ranges from 0-100, with a higher score indicating a greater threat or concern.","format":"double","example":10},"description":"Used to indicate the severity or impact score of the threat represented by the incident.","example":{"asset":10},"$$ref":"#/components/schemas/IncidentScores"},"client_id":{"type":"string"},"techniques":{"type":"array","description":"Represents the specific methods or actions used by an attacker to carry out an offensive maneuver or achieve their goals.","example":["string"],"items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","description":"Represents the level of certainty or trustworthiness associated with the incident. It denotes the reliability of the intelligence associated with the incident.\nThe `confidence` field can take on several values, including:\n- `info`: Indicates that the incident information is based on sources with no previous track record or there is no track record for the source reporting the incident.\n- `low`: Indicates that the incident information is based on sources with a questionable track record or there is limited information about the accuracy of the source.\n- `medium`: Indicates that the incident information is based on sources with a mixed track record or of uncertain reliability.\n- `high`: Indicates that the incident information is based on sources with a proven track record and high degree of reliability.\nThe `confidence` field can be used to indicate the level of trust and confidence that can be attributed to the incident, and it may impact how the incident is prioritized, analyzed and addressed. It can also help in the decision-making process associated with the incident response activities.\nIt is important to note that the `confidence` field is subjective and can be interpreted differently by different organizations or analysts. As such, it is often used in conjunction with other intelligence attributes, such as the `severity` field, to provide a more complete picture of the incident.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"tactics":{"type":"array","description":"Represents the offensive techniques, approaches, or procedures that an adversary may use to achieve their objectives during an attack. It helps in understanding the intent and capabilities of the adversary and can be used to identify indicators of attack (IoAs) or indicators of compromise (IoCs) that are associated with the adversary's tactics.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"$$ref":"#/components/schemas/Incident"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataIncidents"},"sightings":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["confidence","count","id","observed_time","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"relations":{"type":"array","description":"Provide any context we can about where the observable came from.","example":[{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}}],"items":{"required":["origin","related","relation","source"],"type":"object","properties":{"origin":{"type":"string","example":"string"},"origin_uri":{"type":"string","description":"A URI","example":"string"},"relation":{"type":"string","example":"Allocated"},"relation_info":{"type":"object","additionalProperties":{"type":"object","example":{}},"example":{"keyword":{}},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightingsDocsRelationsRelationInfo"},"source":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"},"related":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"additionalProperties":false,"description":"A relation inside a Sighting.","example":{"origin":"string","origin_uri":"string","relation":"Allocated","relation_info":{"keyword":{}},"source":{"value":"1.2.3.4","type":"ip"},"related":{"value":"1.2.3.4","type":"ip"}},"$$ref":"#/components/schemas/ObservedRelation"}},"sensor_coordinates":{"required":["observables","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the device that made the sighting (sensor) and contains identifying observables for the sensor.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"os":"string"},"$$ref":"#/components/schemas/SensorCoordinates"},"observables":{"type":"array","description":"The object(s) of interest.","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"type":{"type":"string","example":"sighting","enum":["sighting"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"targets":{"type":"array","description":"May include one or more targets that observed the associated indicator. Targets can include network devices, host devices, or other entities that are capable of detecting indicators of compromise.\n\nCan be used to assess the scope of potential threats, helping analysts understand which devices or components of the network may be vulnerable to attack. For example, if a particular malware strain is detected on several different systems within an organization, the `targets` field may indicate which systems are affected and which may need to be isolated or patched to prevent further spread.","example":[{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"}],"items":{"required":["observables","observed_time","type"],"type":"object","properties":{"type":{"type":"string","description":"The sensor/actuator name that best fits a device.","example":"endpoint"},"observables":{"type":"array","example":[{"value":"1.2.3.4","type":"ip"}],"items":{"required":["type","value"],"type":"object","properties":{"value":{"type":"string","description":"The value of the observable.","example":"1.2.3.4"},"type":{"type":"string","description":"The type of observable.","example":"ip","enum":["file_path","mac_address","trend_micro_id","cybereason_id","process_args","s1_agent_id","device","hostname","certificate_common_name","serial_number","meraki_network_id","url","certificate_serial","meraki_org_id","cisco_cm_id","registry_key","process_path","darktrace_id","process_username","cortex_agent_id","orbital_node_id","process_uid","ngfw_name","user","certificate_issuer","ipv6","email","cisco_uc_id","sha256","crowdstrike_id","sha1","registry_name","md5","ip","domain","email_subject","imei","ngfw_id","amp_computer_guid","ms_machine_id","mutex","processor_id","swc_device_id","registry_path","odns_identity","odns_identity_label","cisco_mid","process_name","pki_serial","meraki_node_sn","email_messageid","imsi","user_agent","process_hash","file_name"]}},"additionalProperties":false,"description":"A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might appear in a data feed of bad IPs, or bad Domains. These do not exist as objects within the CTIA storage model, so you never create an observable.","example":{"value":"1.2.3.4","type":"ip"},"$$ref":"#/components/schemas/Observable"}},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"os":{"type":"string","example":"string"}},"additionalProperties":false,"description":"Describes the target of the sighting and contains identifying observables for the target.","example":{"type":"endpoint","observables":[{"value":"1.2.3.4","type":"ip"}],"observed_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"os":"string"},"$$ref":"#/components/schemas/IdentitySpecification"}},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"resolution":{"type":"string","description":"Represents the disposition or actions taken on the associated threat intelligence.","example":"detected"},"internal":{"type":"boolean","description":"If `true`, indicates that the sighting was reported from internal sources, such as an organization's own internal security tools or SOC.\n Internal sightings are often considered more reliable and actionable than external sightings, which are reported from external sources and may have a lower level of trustworthiness. Internal sightings can provide more context and can help identify potential threats that are unique to a particular environment or organization.\n Internal sightings can also help organizations prioritize their security response efforts by identifying threats that are specific to their environment and may not yet be widely known.","example":false},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"count":{"type":"integer","description":"The number of times an indicator was observed within a certain period of time.\nFor example, if an IP address associated with known malicious activity is observed once within a period of time, it may indicate a low-level threat. However, if the same IP address is observed multiple times within a short time frame, it may indicate a more severe and persistent threat.\nIt can also be used to prioritize security alerts and indicate the urgency of a response. High counts indicate that an indicator is actively being used in a larger campaign, while low counts may indicate isolated incidents.","format":"int64","example":10},"severity":{"type":"string","example":"Critical","enum":["Medium","Info","Unknown","None","High","Critical","Low"]},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"context":{"type":"object","properties":{"http_events":{"type":"array","description":"a list of `HTTPType`","example":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"items":{"required":["host","process_id","process_name","time","traffic","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"method":{"type":"string","example":"CONNECT","enum":["OPTIONS","PATCH","TRACE","HEAD","POST","CONNECT","GET","PUT"]},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"HTTPEvent","enum":["HTTPEvent"]},"host":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"query":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"encrypted":{"type":"boolean","example":true},"url_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10},"$$ref":"#/components/schemas/HTTPType"}},"process_create_events":{"type":"array","description":"a list of `ProcessCreate`","example":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"items":{"required":["process_id","process_name","time","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"parent_process_guid":{"type":"integer","format":"int64","example":10},"process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_size":{"type":"integer","format":"int64","example":10},"process_size":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_disposition":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"ProcessCreateEvent","enum":["ProcessCreateEvent"]},"parent_process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_creation_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"process_args":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"},"$$ref":"#/components/schemas/ProcessCreateType"}},"registry_delete_events":{"type":"array","description":"a list of `RegistryDeleteType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryDeleteEvent","enum":["RegistryDeleteEvent"]},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"},"$$ref":"#/components/schemas/RegistryDeleteType"}},"file_modify_events":{"type":"array","description":"a list of `FileModifyType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileModifyEvent","enum":["FileModifyEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileModifyType"}},"registry_set_events":{"type":"array","description":"a list of `RegistrySetType`","example":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_value","time","type"],"type":"object","properties":{"process_guid":{"type":"integer","format":"int64","example":10},"registry_data":{"type":"string","description":"String with at most 5000 characters.","example":"string"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"RegistrySetEvent","enum":["RegistrySetEvent"]},"registry_data_length":{"type":"integer","format":"int64","example":10},"registry_value":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"},"$$ref":"#/components/schemas/RegistrySetType"}},"file_create_events":{"type":"array","description":"a list of `FileCreateType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileCreateEvent","enum":["FileCreateEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileCreateType"}},"registry_create_events":{"type":"array","description":"a list of `RegistryCreateType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"items":{"required":["process_id","process_name","registry_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryCreateEvent","enum":["RegistryCreateEvent"]}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"},"$$ref":"#/components/schemas/RegistryCreateType"}},"library_load_events":{"type":"array","description":"a list of `LibraryLoadType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"items":{"required":["dll_library_name","dll_library_path","process_id","process_name","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"LibraryLoadEvent","enum":["LibraryLoadEvent"]},"dll_library_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"dll_library_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"},"$$ref":"#/components/schemas/LibraryLoadType"}},"file_move_events":{"type":"array","description":"a list of `FileMoveType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"items":{"required":["file_name","file_path","new_name","old_name","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileMoveEvent","enum":["FileMoveEvent"]},"old_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"new_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"},"$$ref":"#/components/schemas/FileMoveType"}},"file_delete_events":{"type":"array","description":"a list of `FileDeleteType`","example":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"items":{"required":["file_name","file_path","process_id","process_name","time","type"],"type":"object","properties":{"file_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"type":{"type":"string","example":"FileDeleteEvent","enum":["FileDeleteEvent"]},"file_path":{"type":"string","description":"String with at most 2048 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"failed":{"type":"boolean","example":false}},"additionalProperties":false,"example":{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false},"$$ref":"#/components/schemas/FileDeleteType"}},"netflow_events":{"type":"array","description":"a list of `NetflowType`","example":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"items":{"required":["process_id","process_name","time","traffic","type"],"type":"object","properties":{"parent_process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_in":{"type":"integer","format":"int64","example":10},"process_guid":{"type":"integer","format":"int64","example":10},"process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"traffic":{"required":["destination_ip","destination_port","direction","protocol","source_ip","source_port"],"type":"object","properties":{"destination_host_name":{"type":"string","example":"string"},"protocol":{"type":"integer","description":"The IP [protocol id](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)","format":"int64","example":10},"source_ip":{"type":"string","example":"string"},"destination_subnet":{"type":"string","example":"string"},"destination_ip":{"type":"string","example":"string"},"source_subnet":{"type":"string","example":"string"},"destination_port":{"type":"integer","format":"int64","example":10},"direction":{"type":"string","example":"incoming","enum":["incoming","outgoing"]},"source_port":{"type":"integer","format":"int64","example":10}},"additionalProperties":false,"example":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"$$ref":"#/components/schemas/Traffic"},"flow_time":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"parent_process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"NetflowEvent","enum":["NetflowEvent"]},"process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_path":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_id":{"type":"integer","format":"int64","example":10},"parent_process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_account":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"parent_process_account_type":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_id":{"type":"integer","format":"int64","example":10},"parent_process_hash":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"byte_count_out":{"type":"integer","format":"int64","example":10},"process_args":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"},"$$ref":"#/components/schemas/NetflowType"}},"registry_rename_events":{"type":"array","description":"a list of `RegistryRenameType`","example":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}],"items":{"required":["process_id","process_name","registry_key","registry_old_key","time","type"],"type":"object","properties":{"time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"process_id":{"type":"integer","format":"int64","example":10},"process_name":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"process_guid":{"type":"integer","format":"int64","example":10},"process_username":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"registry_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"type":{"type":"string","example":"RegistryRenameEvent","enum":["RegistryRenameEvent"]},"registry_old_key":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"},"$$ref":"#/components/schemas/RegistryRenameType"}}},"additionalProperties":false,"description":"Context including the event type that best fits the type of the sighting.","example":{"http_events":[{"process_guid":10,"traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"method":"CONNECT","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"HTTPEvent","host":"string","process_name":"string","process_id":10,"process_username":"string","query":"string","encrypted":true,"url_port":10}],"process_create_events":[{"parent_process_name":"string","process_guid":10,"parent_process_guid":10,"process_disposition":"string","parent_process_size":10,"process_size":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_disposition":"string","type":"ProcessCreateEvent","parent_process_username":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","parent_creation_time":"2016-01-01T01:01:01.000Z","process_args":"string"}],"registry_delete_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryDeleteEvent","registry_value":"string"}],"file_modify_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileModifyEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_set_events":[{"process_guid":10,"registry_data":"string","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"RegistrySetEvent","registry_data_length":10,"registry_value":"string","registry_key":"string","process_name":"string","process_id":10,"process_username":"string"}],"file_create_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileCreateEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"registry_create_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryCreateEvent"}],"library_load_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","type":"LibraryLoadEvent","dll_library_name":"string","dll_library_path":"string"}],"file_move_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileMoveEvent","old_name":"string","file_path":"string","process_name":"string","process_id":10,"process_username":"string","new_name":"string"}],"file_delete_events":[{"file_name":"string","process_guid":10,"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"type":"FileDeleteEvent","file_path":"string","process_name":"string","process_id":10,"process_username":"string","failed":false}],"netflow_events":[{"parent_process_name":"string","byte_count_in":10,"process_guid":10,"process_path":"string","traffic":{"destination_host_name":"string","protocol":10,"source_ip":"string","destination_subnet":"string","destination_ip":"string","source_subnet":"string","destination_port":10,"direction":"incoming","source_port":10},"flow_time":"2016-01-01T01:01:01.000Z","time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"parent_process_account":"string","type":"NetflowEvent","process_account_type":"string","parent_process_path":"string","parent_process_id":10,"parent_process_args":"string","process_name":"string","process_account":"string","parent_process_account_type":"string","process_hash":"string","process_id":10,"parent_process_hash":"string","process_username":"string","byte_count_out":10,"process_args":"string"}],"registry_rename_events":[{"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"process_id":10,"process_name":"string","process_guid":10,"process_username":"string","registry_key":"string","type":"RegistryRenameEvent","registry_old_key":"string"}]},"$$ref":"#/components/schemas/Context"},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"observed_time":{"required":["start_time"],"type":"object","properties":{"start_time":{"type":"string","description":"Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If the observation was made over a period of time, than this field indicates the end of that period.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"Period of time when a cyber observation is valid. `start_time` must come before `end_time` (if specified).","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ObservedTime"},"sensor":{"type":"string","description":"The OpenC2 Actuator name that best fits the device that is creating this sighting (e.g. network.firewall)","example":"endpoint"},"data":{"required":["columns","rows"],"type":"object","properties":{"columns":{"type":"array","description":"an ordered list of column definitions","example":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"items":{"required":["name","type"],"type":"object","properties":{"name":{"type":"string","example":"string"},"type":{"type":"string","example":"integer","enum":["url","string","observable","number","integer","markdown"]},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"required":{"type":"boolean","description":"If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.","example":true},"short_description":{"type":"string","example":"string"}},"additionalProperties":false,"example":{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"},"$$ref":"#/components/schemas/ColumnDefinition"}},"rows":{"type":"array","description":"an ordered list of rows","example":[[{}]],"items":{"type":"array","items":{"type":"object"}}},"row_count":{"type":"integer","description":"The number of rows in the data table.","format":"int64","example":10}},"additionalProperties":false,"description":"An embedded data table for the Sighting.","example":{"columns":[{"name":"string","type":"integer","description":"string","required":true,"short_description":"string"}],"rows":[[{}]],"row_count":10},"$$ref":"#/components/schemas/SightingDataTable"}},"additionalProperties":false,"$$ref":"#/components/schemas/Sighting"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataSightings"},"relationships":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","relationship_type","schema_version","source_ref","target_ref","type"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"target_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"type":{"type":"string","example":"relationship","enum":["relationship"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"source_ref":{"type":"string","description":"A URI leading to an entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"relationship_type":{"type":"string","example":"attributed-to"}},"additionalProperties":false,"$$ref":"#/components/schemas/Relationship"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataRelationships"},"vulnerabilities":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["description","id","schema_version","type"],"type":"object","properties":{"description":{"type":"string","description":"Various sources of vulnerability information can be used, including third-party resources like the National Vulnerability Database (NVD) and the Common Vulnerabilities and Exposures (CVE) database. The platform then analyzes this data and provides the user with relevant details such as the severity of the vulnerability, the affected systems, and remediation recommendations. \n\n Based on this information, the user can prioritize patching and other mitigation strategies to reduce the risk of potential attacks.","example":"string"},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"}},"additionalProperties":false,"$$ref":"#/components/schemas/Vulnerability"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataVulnerabilities"},"coas":{"required":["count","docs"],"type":"object","properties":{"count":{"type":"number","format":"double"},"docs":{"uniqueItems":true,"type":"array","items":{"required":["id","schema_version","type","valid_time"],"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"valid_time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"stage":{"type":"string","description":"Specifies what stage in the cyber threat management lifecycle this Course Of Action is relevant to.","example":"Containment","enum":["Identification","Lessons Learned","Remedy","Preparation","Containment","Response","Eradication","Recovery"]},"schema_version":{"type":"string","description":"CTIM schema version for this entity.","example":"1.3.18"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"efficacy":{"type":"string","description":"Effectiveness of this course of action in achieving its targeted objective.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"type":{"type":"string","example":"coa","enum":["coa"]},"created":{"type":"string","format":"date-time"},"related_COAs":{"type":"array","description":"Identifies or characterizes relationships to one or more related courses of action.","example":[{"confidence":"High","source":"string","relationship":"string","COA_id":"string"}],"items":{"required":["COA_id"],"type":"object","properties":{"confidence":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"source":{"type":"string","example":"string"},"relationship":{"type":"string","example":"string"},"COA_id":{"type":"string","description":"A URI leading to a COA.","example":"string"}},"additionalProperties":false,"example":{"confidence":"High","source":"string","relationship":"string","COA_id":"string"},"$$ref":"#/components/schemas/RelatedCOA"}},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"coa_type":{"type":"string","description":"The type of this COA","example":"Diplomatic Actions","enum":["Diplomatic Actions","Physical Access Restrictions","Policy Actions","Internal Blocking","Playbook","Redirection","Phase","Eradication","Public Disclosure","Monitoring","Patching","Logical Access Restrictions","Redirection (Honey Pot)","Rebuilding","Perimeter Blocking","Hardening","Other","Training","Task"]},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"objective":{"type":"array","description":"Characterizes the objective to provide guidance on how to mitigate a security incident that has been identified.","example":["string"],"items":{"type":"string"}},"cost":{"type":"string","description":"Characterizes the estimated cost for applying this course of action.","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"client_id":{"type":"string"},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"open_c2_coa":{"required":["action","type"],"type":"object","properties":{"type":{"type":"string","example":"structured_coa","enum":["structured_coa"]},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"action":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"alert","enum":["stop","save","delete","remediate","redirect","alert","query","augment","snapshot","update","allow","scan","investigate","modify","sync","start","pause","deny","substitute","distill","move","restart","other","detonate","response","set","notify","report","restore","get","throttle","mitigate","resume","locate","contain"]}},"additionalProperties":false,"example":{"type":"alert"},"$$ref":"#/components/schemas/ActionType"},"target":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"amp_computer_guid"},"specifiers":{"type":"string","description":"Observable types that can be acted upon.","example":"string"}},"additionalProperties":false,"example":{"type":"amp_computer_guid","specifiers":"string"},"$$ref":"#/components/schemas/TargetType"},"actuator":{"required":["type"],"type":"object","properties":{"type":{"type":"string","example":"endpoint","enum":["endpoint.sensor","process.network-scanner","network.switch","network.security_manager","process.vulnerability-scanner","network.hub","network.ids","network.firewall","process","network.sense_making","process.sandbox","network.modem","process.email-service","process.dns-server","network.vpn","process.connection-scanner","network.nic","endpoint.printer","network.gateway","process.reputation-service","process.remediation-service","network","process.virtualization-service","network.ips","endpoint.smart-meter","endpoint.digital-telephone-handset","endpoint.workstation","endpoint.server","network.wap","endpoint.laptop","process.aaa-server","process.directory-service","endpoint.pos-terminal","network.bridge","other","process.file-scanner","network.proxy","endpoint","process.location-service","network.sensor","endpoint.smart-phone","network.hips","process.anti-virus-scanner","endpoint.tablet","network.guard","network.router"]},"specifiers":{"type":"array","description":"List of additional properties describing the actuator.","example":["string"],"items":{"type":"string"}}},"additionalProperties":false,"example":{"type":"endpoint","specifiers":["string"]},"$$ref":"#/components/schemas/ActuatorType"},"modifiers":{"type":"object","properties":{"response":{"type":"string","example":"acknowledge","enum":["query","status","acknowledge","command-ref"]},"method":{"type":"array","example":["acl"],"items":{"type":"string","enum":["blackhole","unauthenticated","suspend","graceful","hibernate","whitelist","honeypot","immediate","spawn","blacklist","acl","segmentation","authenticated"]}},"additional_properties":{"required":["context"],"type":"object","properties":{"context":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"context":"string"},"$$ref":"#/components/schemas/AdditionalProperties"},"time":{"type":"object","properties":{"start_time":{"type":"string","description":"If not present, the valid time position of the indicator does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"},"end_time":{"type":"string","description":"If end_time is not present, then the valid time position of the object does not have an upper bound.","format":"date-time","example":"2016-01-01T01:01:01Z"}},"additionalProperties":false,"description":"The time range during which this Indicator is considered valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"frequency":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"duration":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"source":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"search":{"type":"string","example":"cve","enum":["vendor_bulletin","patch","signature","cve"]},"option":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"location":{"type":"string","example":"internal","enum":["internal","perimeter"]},"delay":{"type":"string","description":"Schema definition for all date or timestamp values. Serialized as a string, the field should follow the rules of the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) standard.","format":"date-time","example":"2016-01-01T01:01:01Z"},"destination":{"type":"string","example":"copy-to","enum":["modify-to","set-to","copy-to","move-to","save-to","restore-point","report-to"]}},"additionalProperties":false,"example":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"},"$$ref":"#/components/schemas/ModifierType"}},"additionalProperties":false,"example":{"type":"structured_coa","id":"string","action":{"type":"alert"},"target":{"type":"amp_computer_guid","specifiers":"string"},"actuator":{"type":"endpoint","specifiers":["string"]},"modifiers":{"response":"acknowledge","method":["acl"],"additional_properties":{"context":"string"},"time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"frequency":"string","duration":"2016-01-01T01:01:01.000Z","source":"string","search":"cve","option":"string","id":"string","location":"internal","delay":"2016-01-01T01:01:01.000Z","destination":"copy-to"}},"$$ref":"#/components/schemas/OpenC2COA"},"structured_coa_type":{"type":"string","example":"openc2","enum":["openc2"]},"impact":{"type":"string","description":"Characterizes the estimated impact of applying this course of action.","example":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/COA"}}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleDataDataCoas"}},"additionalProperties":false,"$$ref":"#/components/schemas/ModuleObserveBundle"}},"additionalProperties":false,"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundleData"}},"errors":{"type":"array","items":{"required":["code","message","module_instance_id","module_type_id","type"],"type":"object","properties":{"module_instance_id":{"type":"string"},"module_type_id":{"type":"string"},"module_instance_state":{"type":"string"},"code":{"type":"string"},"message":{"type":"string"},"type":{"type":"string","enum":["fatal","warning","error"]},"module":{"type":"string"}},"additionalProperties":false,"$$ref":"#/components/schemas/ErrorMessage"}}},"additionalProperties":false,"example":{"data":[{"module":"Sample Module","module_instance_id":"da033b3c-81da-4118-b73a-f03feb3adecf","module_type_id":"c84f54db-c187-4cab-8751-2b39b007ee55","data":{"verdicts":{"count":2,"docs":[{"type":"verdict","disposition":2,"observable":{"value":"https://ilo.brenz.pl/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.410Z","end_time":"2023-03-11T13:36:23.410Z"}},{"type":"verdict","disposition":2,"observable":{"value":"http://ilo.brenz.pl/favicon.ico/","type":"url"},"disposition_name":"Malicious","valid_time":{"start_time":"2023-02-09T13:36:23.420Z","end_time":"2023-03-11T13:36:23.420Z"}}]}}}]},"$$ref":"#/components/schemas/DeliberateEnvelopedObserveBundle"}}}},"401":{"description":"A `NormalizedError` including a `trace_id`","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"invalid_request","error_description":"No JWT found in HTTP Authorization header"},"$$ref":"#/components/schemas/NormalizedError-401"}},"application/x-yaml":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"invalid_request","error_description":"No JWT found in HTTP Authorization header"},"$$ref":"#/components/schemas/NormalizedError-401"}},"application/edn":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"invalid_request","error_description":"No JWT found in HTTP Authorization header"},"$$ref":"#/components/schemas/NormalizedError-401"}},"application/transit+json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"invalid_request","error_description":"No JWT found in HTTP Authorization header"},"$$ref":"#/components/schemas/NormalizedError-401"}},"application/transit+msgpack":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"invalid_request","error_description":"No JWT found in HTTP Authorization header"},"$$ref":"#/components/schemas/NormalizedError-401"}}}},"500":{"description":"A `NormalizedError` including a `trace_id`","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"unknown server error","error_description":"An unknown error has occurred during the enrichment","trace_id":"2e790e2c-e7fe-42ed-a18b-7413d9f1f4b0"},"$$ref":"#/components/schemas/NormalizedError-500"}},"application/x-yaml":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"unknown server error","error_description":"An unknown error has occurred during the enrichment","trace_id":"2e790e2c-e7fe-42ed-a18b-7413d9f1f4b0"},"$$ref":"#/components/schemas/NormalizedError-500"}},"application/edn":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"unknown server error","error_description":"An unknown error has occurred during the enrichment","trace_id":"2e790e2c-e7fe-42ed-a18b-7413d9f1f4b0"},"$$ref":"#/components/schemas/NormalizedError-500"}},"application/transit+json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"unknown server error","error_description":"An unknown error has occurred during the enrichment","trace_id":"2e790e2c-e7fe-42ed-a18b-7413d9f1f4b0"},"$$ref":"#/components/schemas/NormalizedError-500"}},"application/transit+msgpack":{"schema":{"type":"object","properties":{"error":{"type":"string"},"error_description":{"type":"string"},"error_uri":{"type":"string"},"trace_id":{"type":"string"},"schema.core.AnythingSchema@3c6f0b88":{"type":"object"}},"additionalProperties":{"type":"object"},"example":{"error":"unknown server error","error_description":"An unknown error has occurred during the enrichment","trace_id":"2e790e2c-e7fe-42ed-a18b-7413d9f1f4b0"},"$$ref":"#/components/schemas/NormalizedError-500"}}}}},"x-no-doc":false,"x-codegen-request-body-name":"Observables","security":[{"oAuth2":["integration:read","private-intel:read","profile:read","inspect:read","users:read","invite:read","enrich:read","oauth:read","response:read","global-intel:read","ao:read","playbook:read"]}],"method":"post","path":"/iroh/iroh-enrich/deliberate/observables"}}