Federated Search for Security Teams // query.ai

Joined January 2018
777 Photos and videos
Security Architects when that SIEM renewal starts creeping up...
2
Your threat intel is fast. Your data is scattered across a dozen tools, 3 query languages, and a cold archive you can't search. That's the threat hunting tax. Query federates the hunt. One query, every source, in place. No ingestion. hubs.li/Q04kXn4g0 #threathunting
25
The Query App for Splunk just got another new update. Latest version available for download via Splunkbase for all Query/Splunk users. Got Splunk but need to extend it to more data w/o the $$? The Query App for Splunk can help. No ingest required. hubs.li/Q04kQdM-0
1
7
Available via Splunkbase: splunkbase.splunk.com/app/46…

3
23 minutes of Workers time. 20 queries. 6-10 hours saved. 120 overnight alerts collapsed to 5 named kill chains. This isn't AI replacing analysts. It's federation across all your data turning a morning queue into a morning briefing. Full case breakdown: hubs.li/Q04kBW5Q0
5
What every vendor selling ingest-based pricing tells you Hang in there while we centralize your data. While the migration finishes. While the bill racks up. Or: query across all your data w/o moving any of it The good thing already happened. It's just not on the renewal quote.
8
Still haven't solved your Splunk cost problem? We get it. What if you could keep Splunk, extend it to more data, AND fix the cost? The Query App for Splunk lets you use any Security Data Mesh source from inside Splunk. Same tool, lower bill. Wanna see? hubs.li/Q04j-CJv0
4
No detection rule fired. The hunt found 9 compromised hosts. Query Workers ran a 7-day Living-off-the-Land hunt across Windows, Linux & AWS — banking trojan, keylogger, staged wiper, all pre-detonation. Full audit trail: hubs.li/Q04jVFq10 #SIEM #cybersecurity
15
More time is spent pulling data than analyzing it. Each Query Worker automates a SecOps job across every connected source, builds the evidence chain, and flags what it couldn’t verify. Your analysts make the call. Full investigation gallery: hubs.li/Q04jFFw50 #AISOC
17
When it was a short week but you work in security
1
Query puts your security data to work. 50 connectors. Unified data model. No pipelines to build or maintain. Centralize the insights, not the data. hubs.li/Q04jb0kj0
4
'Detection coverage gaps' aren't detection problems. They're ingestion problems. S3 logs, SaaS audit trails, EDR data tiered to cold — invisible to your SIEM, invisible to your rules. Federated Detections runs the logic where data lives. No ETL. hubs.li/Q04hSZWP0
3
Your AI Security Agents trying to reach the security data they actually need but you slapped them on top of a single repo because centralization
6
We gave a Query Worker one prompt: “hunt for OAuth app-consent abuse” 35 mins later: • 25 federated queries • 5 production-ready detections • 3 critical telemetry gaps identified across Entra/JumpCloud/AWS That’s AI-native threat hunting on the security data mesh #AISOC
20
A Query Worker ran a threat hunt across 5 AWS accounts Azure from one prompt. 12 queries later it found: • Read-only roles stopping CloudTrail • New IAM users created • Unauthorized admin policy attachments Then it generated detections a remediation plan automatically.
6
What does it cost to index 6 months of CrowdStrike telemetry into Splunk? More than storing it in S3 and searching it with Query. A lot more. Dhiraj Sharan walks through how one customer did exactly that: hubs.li/Q04fT7H80 #cybersecurity #SecDataOps #federatedsearch
23
Are your SIEM retention periods driven by licensing pressure or investigative need? 20-question self-assessment to find out what your security data architecture is actually costing you: hubs.li/Q04fSBMf0 #SIEM #cybersecurity #SecDataOps
9
3 ?'s you should ask your AI security vendor • Can you see the actual query syntax? • Can you independently rerun searches/verify results? • Can you see what failed? Matt Eberhart on why "explainable AI" usually isn't: hubs.li/Q04fT6wx0 #AISOC #cybersecurity #SIEM
16
Here's a Worker running a threat hunt for OAuth app-consent abuse across Entra, JumpCloud, and AWS. Result? Thirty-five minutes. Structured hypothesis, 25 queries across three platforms, five detections ready for soak, and a gap inventory that makes the next hunt better.
11
Sarah Paulson bravely protesting her SIEM bill at the 2026 Met Gala
49