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
Urgency, a sender name that does not match the address, and a link that does not match the sender are the flags. The checker reads text you paste. It does not request the URL.
You do not click, you do not reply, and you do not forward the live link into a wide chat. Report it the way your organisation already says.
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. It is not a password you keep.
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.
- Paste text you may hold.
- Read the flags.
- Write one sentence.
- Do not open the link.
- Stop.
Mistakes that outlive the statement
Spotting Phishing Emails goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- The link opened.
- The message answered.
- The page used to write a phish.
Decisions to write down
One decision for Spotting Phishing Emails: The link was not opened. The note has no live lure. And the report path is the one you already have.
Checks before you call it done
Confirm this before you call the change done: The flags are written. No link was opened. No reply was sent. No lure was written. And the mailbox is yours. If one of those fails, stop.
# Red flags only. Do not open the link. Do not write a lure.
# 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. It is not a password you keep.Before you leave the system
Spotting Phishing Emails 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.