Showing 1–5 of 5 articles
How to write a security note people can trust
A useful security note makes its claims checkable and its next step clear. State what is known, identify the source, label uncertainty, and tell the reader who needs to do what.
Read the visual guide
How to show that you deleted someone’s data
A completed deletion ticket is not proof that every copy was removed. Record the systems searched, actions taken, justified retention, and how backups or restoration affect the result.
Read the visual guide
How long to keep security logs
Retention is an operational decision about which events must remain available, for how long, and at what cost and sensitivity. Connect the window to incident questions and real search capability.
Read the visual guide
How to handle a security report from someone you do not know
A report from an unfamiliar person may identify a real issue. Provide a controlled route to receive it, assess the evidence, and decide the next step without encouraging unnecessary testing.
Read the visual guide
How to write a security note a board can use
A board needs to understand the decision, its consequence, and the uncertainty around it. Replace a long list of tools with a concise account of risk, options, ownership, and evidence.
Read the visual guide