This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Splunk SPL to KQL Conversion Guide converts a detection you already hold. The SPL to KQL starter is a partial rewrite. Check the table and the summarize before anyone saves it.
You do not convert a rule you do not own, and you do not save the sketch as a production alert during the reading. The page does not add an attack and does not run the query.
The browser tool drafts text. It does not connect to the SIEM.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you publish because a draft included them.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the system named in the ticket. Read the draft, then the system, then decide.
Rollback is the file, the record, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Write the system, domain, or log source, and confirm you administer it.
- Save the current file, record, or export before any draft is applied.
- Read the draft and delete every line this ticket did not name.
- Replace a sample password, a sample exclude, example.com, and any secret.
- Apply nothing during the reading.
- Read the result back and compare it with the ticket.
- Stop. The next change is a different page.
Mistakes that outlive the statement
spl-kql conversion goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Pasting a draft you did not read.
- The wrong system.
- A secret in the ticket or in git.
- Two changes in one window.
- No copy saved before the change.
- A documentation address or example.com left in a record you publish.
- Disabling a firewall, antivirus, or tamper protection to make a check pass.
- Calling the generator output a finished production change.
- Saving a partial rewrite as a production alert.
- Converting a rule you do not own.
- Running the sketch during the reading.
Decisions to write down
One decision for spl-kql conversion: The source detection is one you hold. The rewrite is partial until the fields are mapped. The destination is the platform in the title. Nothing was enabled during the reading. And the page was not used to build an attack.
Checks before you call it done
Confirm this before you call the change done: The source rule is named. The sketch was read. Fields are still marked unmapped, or a person mapped them. Nothing was enabled. No secret is in the note. And a second person can say which index or table is next. If one of those fails, stop.
# Partial conversion. Map every field.
# Do not enable this during the reading.
# The SPL to KQL starter is a partial rewrite. Check the table and the summarize before anyone saves it.
# 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you publish because a draft included them.Before you leave the system
Splunk SPL to KQL Conversion Guide ends when the system in the note is the system in the ticket. If it is not, stop.
The draft stays a draft until a person has read the names in it. A generator does not log in, does not scan, and does not send mail.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you publish because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save. A sample password is replaced. It is not a password you keep.
One change is the window. If two things move and the result is wrong, you will not know which one did it.
If the same step fails twice, stop for the day. Restore the copy you took first.
A second person reads the scope aloud. If they cannot find it in the ticket, the note is not done.
This page is a planning guide. It is not legal advice, not an audit opinion, not a vendor manual, and not the text of a standard. You do not disable a security control to make a check pass. You do not use the page against a system you do not administer.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.