TargetRecord A TargetRecord is a Sighting that has no threat or observables associated with it, it's a way of saying they saw a set of observables together as a Target.
Property | Type | Description | Required? |
---|---|---|---|
id | String | Globally unique URI identifying this object. | ✓ |
schema_version | String | CTIM schema version for this entity. | ✓ |
source | MedStringString | Represents the source of the intelligence that led to the creation of the entity. | ✓ |
targets | Target Object List | ✓ | |
type | TargetRecordTypeIdentifierString | ✓ | |
description | MarkdownString | A description of object, which may be detailed. | |
external_ids | String List | 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. 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. | |
external_references | ExternalReference Object List | Specifies a list of external references which refers to non-CTIM information. Similar to external_ids field with major differences: - 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. - 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. | |
language | ShortStringString | 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. For 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. | |
revision | Integer | A monotonically increasing revision, incremented each time the object is changed. | |
short_description | MedStringString | A single line, short summary of the object. | |
source_uri | String | URI of the source of the intelligence that led to the creation of the entity. | |
timestamp | Inst (Date) | The time this object was created at, or last modified. | |
title | ShortStringString | A short title for this object, used as primary display and reference value. | |
tlp | TLPString | TLP stands for Traffic Light Protocol, which indicates precisely how a resource is intended to be shared, replicated, copied, etc. It 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. For 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. |
A description of object, which may be detailed.
This entry is optional
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. 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.
Specifies a list of external references which refers to non-CTIM information.
Similar to external_ids
field with major differences:
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.
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.
Globally unique URI identifying this object.
This entry is required
https://www.domain.com/ctia/judgement/judgement-de305d54-75b4-431b-adb2-eb6b9e546014
for a Judgement. This ID type compares to the STIX id field. The optional STIX idref field is not used.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.
For 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.
This entry is optional
A monotonically increasing revision, incremented each time the object is changed.
This entry is optional
CTIM schema version for this entity.
This entry is required
A single line, short summary of the object.
This entry is optional
Represents the source of the intelligence that led to the creation of the entity.
This entry is required
URI of the source of the intelligence that led to the creation of the entity.
This entry is optional
The time this object was created at, or last modified.
This entry is optional
A short title for this object, used as primary display and reference value.
This entry is optional
TLP stands for Traffic Light Protocol, which indicates precisely how a resource is intended to be shared, replicated, copied, etc.
It 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.
For 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.
This entry is optional
This entry is required
ExternalReference 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.
Property | Type | Description | Required? |
---|---|---|---|
source_name | MedStringString | The source within which the external-reference is defined (system, registry, organization, etc.) | ✓ |
description | MarkdownString | ||
external_id | String | An identifier for the external reference content. | |
hashes | String List | Specifies a dictionary of hashes for the contents of the url. | |
url | String | A URL reference to an external resource. |
This entry is optional
An identifier for the external reference content.
Specifies a dictionary of hashes for the contents of the url.
The source within which the external-reference is defined (system, registry, organization, etc.)
This entry is required
A URL reference to an external resource.
This entry is optional
Target Schema for TargetRecord Targets
Property | Type | Description | Required? |
---|---|---|---|
observables | Observable Object List | ✓ | |
observed_time | ObservedTime Object | ✓ | |
type | SensorString | ✓ | |
internal | Boolean | Is it internal to our network? | |
os | String | Source Operating System where TargetRecord was originated. | |
sensor | String | The OpenC2 Actuator name that best fits the device that is creating this TargetRecord (e.g.: network.firewall, etc.) | |
source_uri | String |
Is it internal to our network?
Source Operating System where TargetRecord was originated.
The OpenC2 Actuator name that best fits the device that is creating this TargetRecord (e.g.: network.firewall, etc.)
This entry is optional
This entry is required
ObservedTime Period of time when a cyber observation is valid. start_time
must come before end_time
(if specified).
Property | Type | Description | Required? |
---|---|---|---|
start_time | Inst (Date) | Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period. | ✓ |
end_time | Inst (Date) | If the observation was made over a period of time, than this field indicates the end of that period. |
If the observation was made over a period of time, than this field indicates the end of that period.
This entry is optional
Time of the observation. If the observation was made over a period of time, than this field indicates the start of that period.
This entry is required
Observable 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.
Property | Type | Description | Required? |
---|---|---|---|
type | ObservableTypeIdentifierString | ✓ | |
value | String | ✓ |
This entry is required
Can you improve this documentation? These fine people already did:
Ag Ibragimov, Guillaume Erétéo, Mark Herman, Guillaume ERETEO, jyoverma & Matthieu SprunckEdit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close