Mean Time to Detect (MTTD) measures the elapsed time between the occurrence or beginning of a security incident and its detection by the organization, according to its defined measurement methodology.
Scheduling security detections to execute only once per hour can introduce substantial detection latency.
For example, if suspicious activity occurs immediately after a scheduled detection completes, the next execution may not occur for nearly sixty minutes.
Additional delays can arise from ingestion latency, search execution time, queueing, and downstream alert processing.
Splunk Enterprise Security allows detection engineers to configure search frequency through cron schedules and specify the time ranges used by scheduled detections.
The appropriate frequency depends on the detection ' s criticality, ingestion characteristics, computational cost, and operational requirements.
High-priority scenarios may require shorter scheduling intervals or near-real-time processing, while less urgent analytical searches may appropriately use longer intervals.
Option A can improve search efficiency by reducing irrelevant processing, provided important detection evidence is preserved.
Option C supports consistent analysis across heterogeneous sources, potentially reducing investigation and correlation delays.
Option D generally reduces data-delivery latency by transmitting endpoint telemetry continuously rather than relying on periodic collection.
Therefore, hourly batch-based detection execution is the option most likely to increase MTTD.
Official reference / study topic: Splunk Enterprise Security, Specify the Time to Run Detections, cron scheduling and time ranges.
===============
Submit