Some of the fields are not captured by the Intelligence in Mission Control

Available Languages

Updated:September 29, 2026

Document ID:SPLK046897

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Mission Control

Description

In the Mission Control Incident, some of the fields from the incident are not captured as the "observables" in the Intelligence section.

Investigation

As per the documentation, the Observables that should be extracted from the MC incident are given below,

risk_object
threat_object
threat_match_value
host
orig_host
dvc
dest
src
src_user
user

But the observables couldn't extract the following fields from the MC incident.

risk_object
threat_object
threat_match_value

The observables extracted only the dest, host, dvc as shown above.

Resolution

This issue has been identified as known issue and it's getting fixed in the upcoming version.

Workaround:

As the observables are dependent on the lookup which contain the feeds from the external sources.

Lookup: tim_iocs
Macro: `tim_iocs_library`

The value of the IOC from the incident can be included in the SPL with the lookup as shown below, see Threat Object in screenshot investigation section:

|`tim_iocs_library` | search observable_value="193b4833d3da1d8515a87972f5fbe51c817d550f06edda078d11a6e18c18aca1"