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
Writing Suricata and Snort Rules names the question, such as a protocol and a port you already log, and the sensor you administer. This page does not explain how to cause the traffic, and it does not include a content match. You do not load the rule during the reading, and you do not disable the sensor.
Write the system you administer, the name of this change, and the time. A second change waits until this line has been read back.
The browser tool drafts text or reads a paste you already hold. It does not log in, it does not scan, and it does not apply.
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. A sample password is replaced.
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 sensor you administer.
- Write the question in one sentence.
- Say the rule has no payload.
- Do not load the rule.
- Do not disable the sensor.
- Stop.
Mistakes that outlive the statement
Writing Suricata and Snort Rules goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A payload copied into the rule.
- The rule loaded during the reading.
- The sensor disabled to test a line.
- A network you do not administer named as the target.
Decisions to write down
One decision for Writing Suricata and Snort Rules: The sensor is yours. The question is one sentence. No payload is in the note. Nothing is loaded. And the sensor stays on.
Checks before you call it done
Confirm this before you call the change done: The sensor is written. The question is one sentence. No payload is in the note. Nothing was loaded. And a second person can say the sensor stayed on. If one of those fails, stop.
# Rule plan. No payload. Do not load the rule. Do not disable the sensor.
Before you leave the system
Writing Suricata and Snort Rules 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.