1. Pause the request, then verify separately
Rehearsal example: a message says that your service will stop unless you sign in immediately. Write down the requested action, the claimed sender and what you do not yet know. Use a fictional example rather than uploading a private message to the community.
The U.S. Federal Trade Commission recommends contacting a known organization through a phone number or website you already know is real, rather than the details in a suspicious message. Record where you obtained that independent route. A polished logo or an urgent tone is not identity verification.
2. Make the fallback concrete
Choose one service or household coordination task for this exercise. On a private paper copy, note the official help route and where you would find it if the original message disappeared. Keep passwords, recovery codes and sensitive documents out of a public discussion or this website’s manual checklist.
For the fictional service-interruption example, rehearse finding the organization’s own status or support page. Write “not yet verified” when you cannot establish a fact. Do not turn a missing page or lost connection into a claim that AI caused an incident. The useful result is a repeatable checking method.
3. Keep one reference and maintain account habits
Download the reading sheet, locate the real file and open it. Check the date. Practise reopening it without internet when safe, then note which external links still require a connection. A screenshot or a saved sheet is a dated reference; it cannot keep current incident information up to date by itself.
Canada’s Get Cyber Safe recommends distinct, strong credentials and multi-factor authentication. Review those settings through the account’s real service and support instructions. The Protect Me worksheet does not change them for you. If a real account is compromised, use that provider’s current recovery process rather than treating a rehearsal as a repair.
ORIGINAL WORKSHEET
Pause · verify · keep
Use fictional examples here. Fill any private contact details only on your own paper copy.
| Step | What I checked | What remains unknown |
|---|---|---|
| Request | ________ | ________ |
| Independent contact route | ________ | ________ |
| Saved reference and date | ________ | ________ |
Save it. Then test it.
One reading file, 5.9 KB. No maps, external images, scripts or personal records. External source links still need internet.
Checks remain only during this visit. They do not certify readiness, safe equipment or successful delivery. The saved worksheet has blank prompts.
Save on this computer, or copy the completed download to a compatible USB drive. Reopen from that location for the offline test.
READ THE BASIS
Sources, dates and limits
A manual learning exercise, not malware detection, guaranteed AI protection, incident attribution or emergency dispatch. The checklist does not inspect your phone or prove account security. Use current official support for a real incident.
Source links checked 2026-10-19. The organization and sample worksheets are original editorial work. A source check is not a qualified review or a physical-device test. Downloaded files are dated snapshots; use current local guidance and equipment instructions.
- FTC — Recognize and avoid phishing scamsUnited States consumer guidance
- Get Cyber Safe — Secure your accountsCanada account-security guidance
CONTINUE WHEN IT IS USEFUL
Use the matching Prepper task
Review practical references and mark only the guidance you have actually read. Review marks are manual.
Open the Rogue AI protection guides →The installed product is Prepper. AI Rogue is a section inside it. An article or website release does not verify a public store listing, an update received by your phone, live LoRa messaging or an OS lock.