Get one Actor by ID - Cisco XDR APIs

{"type":"api","title":"Get one Actor by ID","meta":{"id":"/apps/pubhub/media/cisco-xdr-api-docs/f4e065ff5977829c89df289df08411f83205f526/2c61df32-bc97-34af-969d-a2ce06b8e459","info":{"title":"CTIA","description":"A Threat Intelligence API service\n\n This API provides a mechanism for making Judgements on the Disposition\n of Observables, which are then distilled into a final Verdict. A\n Disposition is a statement regarding the malicious, or otherwise,\n nature of an Observable.\n\n The Judgements can be grouped into Indicators, which can be associated\n with Campaigns, Actors and TTPs. Feedback can be given on specific\n Judgements, indicating agreement or disagreement, or clarification.\n\n When an Observable with a malicious Verdict is seen, it can be recorded as\n a Sighting, and the Relations that Observable had with other Observables can\n be recorded as well.\n\n We support a pre-defined set of Observable Types. Each Observable Type has a\n specific form of natural identifier, its ID, which is almost always\n the default way it is represented when observed in the wild.\n\n * Ipv4/IPv6 -- 192.168.1.1\n * Domain/Hostname -- foo.com, www.bar.com\n * SHA256 -- the sha256 checksum of a file, or other data blob\n * MD5 -- the md5 checksum of a file, or other data blob\n * SHA1 -- the sha1 checksum of a file, or other data blob\n * URL -- A minimal form of the URL\n\n The Verdict is derived from all of the Judgements on that Observable which\n have not yet expired. The highest priority Judgement becomes the\n active verdict. If there is more than one Judgement with that\n priority, than Clean disposition has priority over all others, then\n Malicious disposition, and so on down to Unknown.\n\n \u003ca href='/doc/README.md'\u003eCTIA Documentation\u003c/a\u003e","contact":{"name":"Cisco Security Business Group -- Advanced Threat ","url":"http://github.com/threatgrid/ctia","email":"cisco-intel-api-support@cisco.com"},"license":{"name":"All Rights Reserved","url":""},"version":"2.24.0"},"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":"Actor","description":"Actor operations"},{"name":"Asset","description":"Asset operations"},{"name":"Asset Mapping","description":"Asset Mapping operations"},{"name":"Asset Properties","description":"Asset Properties operations"},{"name":"Attack Pattern","description":"Attack Pattern operations"},{"name":"Campaign","description":"Campaign operations"},{"name":"Casebook","description":"Casebook operations"},{"name":"COA","description":"COA operations"},{"name":"Event","description":"Events operations"},{"name":"Feed","description":"Feed operations"},{"name":"Incident","description":"Incident operations"},{"name":"Indicator","description":"Indicator operations"},{"name":"Judgement","description":"Judgement operations"},{"name":"Malware","description":"Malware operations"},{"name":"Relationship","description":"Relationship operations"},{"name":"Sighting","description":"Sighting operations"},{"name":"Target Record","description":"Target Record operations"},{"name":"Tool","description":"Tool operations"}],"x-parser-conf":{"serverConfig":"select","overview":{"markdownPath":"reference/private-intel/overview.md","uri":"private-intel-ctia-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://private.intel.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: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":["Actor"],"summary":"Get one Actor by ID","description":"Requires capability read-actor.","parameters":[{"name":"id","in":"path","required":true,"schema":{"type":"string"}},{"name":"fields","in":"query","style":"form","explode":true,"schema":{"type":"array","items":{"type":"string","enum":["motivation","valid_time.start_time","sophistication","schema_version","revision","source","valid_time.end_time","title","source_uri","intended_effect","language","id","tlp","timestamp","actor_types"]}}}],"responses":{"200":{"description":"","content":{"application/json":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"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":"Period of time when a cyber observation is valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"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":{"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"},"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"},"authorized_users":{"type":"array","items":{"type":"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"}},"groups":{"type":"array","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"]},"owner":{"type":"string"},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"description":"Describes malicious actors or adversaries related to a cyber attack.","example":{"description":"string","motivation":"Ego","valid_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"identity":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"sophistication":"Aspirant","schema_version":"1.3.18","revision":10,"planning_and_operational_support":"string","type":"actor","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","intended_effect":"Account Takeover","language":"string","id":"string","tlp":"green","aliases":["string"],"timestamp":"2016-01-01T01:01:01.000Z","confidence":"High","actor_types":["Cyber Espionage Operations"]},"$$ref":"#/components/schemas/PartialActor"}},"application/x-yaml":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"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":"Period of time when a cyber observation is valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"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":{"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"},"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"},"authorized_users":{"type":"array","items":{"type":"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"}},"groups":{"type":"array","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"]},"owner":{"type":"string"},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"description":"Describes malicious actors or adversaries related to a cyber attack.","example":{"description":"string","motivation":"Ego","valid_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"identity":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"sophistication":"Aspirant","schema_version":"1.3.18","revision":10,"planning_and_operational_support":"string","type":"actor","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","intended_effect":"Account Takeover","language":"string","id":"string","tlp":"green","aliases":["string"],"timestamp":"2016-01-01T01:01:01.000Z","confidence":"High","actor_types":["Cyber Espionage Operations"]},"$$ref":"#/components/schemas/PartialActor"}},"application/edn":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"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":"Period of time when a cyber observation is valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"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":{"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"},"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"},"authorized_users":{"type":"array","items":{"type":"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"}},"groups":{"type":"array","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"]},"owner":{"type":"string"},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"description":"Describes malicious actors or adversaries related to a cyber attack.","example":{"description":"string","motivation":"Ego","valid_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"identity":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"sophistication":"Aspirant","schema_version":"1.3.18","revision":10,"planning_and_operational_support":"string","type":"actor","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","intended_effect":"Account Takeover","language":"string","id":"string","tlp":"green","aliases":["string"],"timestamp":"2016-01-01T01:01:01.000Z","confidence":"High","actor_types":["Cyber Espionage Operations"]},"$$ref":"#/components/schemas/PartialActor"}},"application/transit+json":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"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":"Period of time when a cyber observation is valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"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":{"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"},"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"},"authorized_users":{"type":"array","items":{"type":"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"}},"groups":{"type":"array","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"]},"owner":{"type":"string"},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"description":"Describes malicious actors or adversaries related to a cyber attack.","example":{"description":"string","motivation":"Ego","valid_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"identity":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"sophistication":"Aspirant","schema_version":"1.3.18","revision":10,"planning_and_operational_support":"string","type":"actor","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","intended_effect":"Account Takeover","language":"string","id":"string","tlp":"green","aliases":["string"],"timestamp":"2016-01-01T01:01:01.000Z","confidence":"High","actor_types":["Cyber Espionage Operations"]},"$$ref":"#/components/schemas/PartialActor"}},"application/transit+msgpack":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"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":"Period of time when a cyber observation is valid.","example":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"$$ref":"#/components/schemas/ValidTime"},"identity":{"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":{"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"},"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"},"authorized_users":{"type":"array","items":{"type":"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"}},"groups":{"type":"array","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"]},"owner":{"type":"string"},"actor_types":{"type":"array","example":["Cyber Espionage Operations"],"items":{"type":"string"}}},"additionalProperties":false,"description":"Describes malicious actors or adversaries related to a cyber attack.","example":{"description":"string","motivation":"Ego","valid_time":{"start_time":"2016-01-01T01:01:01.000Z","end_time":"2016-01-01T01:01:01.000Z"},"identity":{"description":"string","related_identities":[{"identity":"string","confidence":"High","information_source":"string","relationship":"string"}]},"sophistication":"Aspirant","schema_version":"1.3.18","revision":10,"planning_and_operational_support":"string","type":"actor","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","intended_effect":"Account Takeover","language":"string","id":"string","tlp":"green","aliases":["string"],"timestamp":"2016-01-01T01:01:01.000Z","confidence":"High","actor_types":["Cyber Espionage Operations"]},"$$ref":"#/components/schemas/PartialActor"}}}}},"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":"get","path":"/ctia/actor/{id}"}}