| Atlas | Federated Atlas Deployments to Splunk Cloud do not function on Splunk V10.4.1 due to Splunk removing the '/services/data/federated/provider' endpoint which supports the federated deployment. | Investigating | Bug ticket submitted to Splunk |
| Atlas | Dashboards will not load properly when Splunk is running on a Windows machine on Splunk v10.4.1 | Resolved in V5.0.8 | |
| Atlas Navigation | Atlas Power Tools lack navigation bars in Splunk 10.4 | Resolved in V5.0.7 | |
| Atlas Assessment | Some roles may get issues related to pre-flight checks. | Investigating | Try scheduling an Assessment instead of a manual execution. |
| Atlas Data Hub | Data Hub Utilization not capturing full utilization and correctly labeling by category (Ad-hoc, Scheduled, Dashboard) on modal. | Resolved in V5.0.6 | |
| Atlas Data Hub | Data Backfill may not execute as intended | Resolved in V5.0.6 | Manually launch the Backfill searches from the Splunk Searches and Reports page. Contact EOD. |
| Atlas Logging | Atlas Logging may not capture page hits | Resolved in V5.0.0 | |
| Search Hub | After configuring Search Hub on new environments, Schedule Recommendations may not have details until the environment populates 24 hours later | Known Behavior | |
| STIG Compliance | After an upgrade of the STIG Compliance element, the STIG Library may need to be manually updated on clustered search head deployments. This may be noticeable when you don't see any data in the STIG Library or the new version is not present. | Workaround Identified | Workaround: Update the STIG Library with the desired version using the process documented. |