Integration pairs
Two named tools, and what actually happens between them. Newest check first.
Pair Partial CrowdStrike Falcon and Splunk Falcon detection, incident and audit data streams into Splunk reliably through an add-on CrowdStrike writes and supports itself. Sending an instruction back the other way is not part of it, and the ingest side has a throughput ceiling and an appId rule that will cost you data if you ignore them.
Checked Pair Partial Okta and Jira Cloud SCIM provisioning from Okta to an Atlassian organization is real, documented on both sides and does create, update and deactivate accounts. It is not a complete offboarding control on its own, it requires a paid Atlassian Guard Standard subscription plus Okta Lifecycle Management, and the failure modes cluster around domain verification and group naming.
Checked Pair Partial Okta and Splunk Okta System Log data gets into Splunk two different ways and both are first-party documented. Neither one is complete on its own: the push path is Splunk Cloud only and loses anything it drops, and the pull path is throttled and stops at 90 days. Most serious deployments run both, one for live data and one for backfill.
Checked Pair Partial Splunk and Jira Cloud Jira Cloud's API will happily create the ticket. Splunk's built-in webhook alert action cannot be the thing that calls it, because it has no documented way to send a credential. Every working version of this integration is an add-on or a custom alert action sitting between the two, and that is code someone has to own.
Checked