6.9 Module Summary
Module 6 Summary
What you learned
This module taught you KQL from first principles to investigation-ready fluency. You progressed from writing your first SigninLogs query to constructing complex cross-table correlations, building reusable query libraries, and completing 5 investigation scenarios from scratch.
Skills checklist
After completing this module, you should be able to say:
- I can write a KQL query from a blank editor for any investigation scenario
- I understand the pipe model and can read any KQL query by following the data flow
- I use
wherewith the correct comparison operators (hasovercontains,infor lists) - I use
projectat the end of queries and understand why column order matters - I use
extendto add computed columns (time classification, IP categorization, JSON extraction) - I use
letfor both simple parameterization and sub-query patterns - I use
summarizewithcount,dcount,make_set,arg_max, and other aggregation functions - I use
bin()for time-series grouping andrenderfor visualization - I use
unionto combine tables andjoin(inner, leftouter, leftanti) to correlate tables - I can extract data from strings using
split(),extract(), andparse - I know the 6 security-specific KQL patterns (failed-then-succeeded, first-time-seen, impossible travel, anomalous volume, IOC sweep, entity timeline)
- I have started building a parameterized, commented query library
- I can debug failing queries systematically using line elimination
- I can optimize slow queries by reordering filters and choosing the right operators
SC-200 exam objectives covered
Domain 1 — Manage a SOC Environment:
- Query logs in Microsoft Sentinel (covered in 6.1-6.4)
Domain 4 — Manage Security Threats:
- Identify threats by using KQL (covered in 6.1-6.5)
- Create custom hunting queries by using KQL (covered in 6.5-6.8)
KQL is also embedded in:
- Domain 2: Analytics rules are KQL queries (Module 9 builds on this)
- Domain 3: Investigation queries use KQL (Modules 11-13 build on this)
Bridge to Module 7
Module 7 (Configure Your Microsoft Sentinel Environment) uses the KQL skills you just built. You will query workspace data, configure watchlists (which are queryable with KQL), and integrate threat intelligence that you will correlate using KQL joins. The workspace configuration itself does not require KQL — but verifying it works does. Every validation query in Module 7 uses operators you learned here.
If you are following the recommended build order (Module 6 → Module 1), Module 1 (Mitigate Threats Using Microsoft Defender XDR) puts your KQL skills to work immediately in the Defender XDR Advanced Hunting interface.