Showing 1–12 of 13 articles
Page 1 of 2
How to threat-model a small product in one sitting
Start with one important journey through your product. Follow the data, identities, and trust boundaries, then ask what misuse could cause a meaningful consequence.
Read the visual guide
How to run a short security exercise with eight people
A short exercise can reveal whether people know who decides, who contacts whom, and how recovery would begin. Use a realistic scenario and finish with a small, owned action list.
Read the visual guide
Who should have administrator rights on a work laptop
Administrator access changes what software can do to a device. Limit routine privilege while giving staff a clear, workable route for approved installation and support.
Read the visual guide
How long a shared file link should stay open
A sharing link should serve a specific task and audience. Named recipients, suitable permissions, and an expiry date can reduce access that continues after the work is done.
Read the visual guide
How staff should report a suspicious email
People report more effectively when the route is easy to find and the response is clear. Ask for the message and what happened after it, without encouraging further interaction.
Read the visual guide
How to roll out a password manager to a small company
A team vault needs an ownership model as well as an app. Decide what is personal, what the organization owns, and how access will be removed when someone leaves.
Read the visual guide
How to remove access when someone leaves
A person’s access may extend beyond their main account. Use a planned sequence to protect information, close sessions and tokens, and transfer legitimate ownership without losing critical work.
Read the visual guide
What to decide before you buy a security monitoring tool
A monitoring product creates value only when the right data reaches it and someone can act on its findings. Start with concrete detection stories and a bounded pilot.
Read the visual guide
How a team of five can patch without stopping the work
A workable patch routine names an owner, prioritizes exposed and important systems, and checks the affected workflow after an update. Keep exceptions visible rather than indefinitely postponed.
Read the visual guide
How a small team proves it can restore a backup
A backup job marked successful does not prove that people can resume work. Restore a representative sample into a safe environment and check the data, access, and dependencies.
Read the visual guide
What DMARC does for a small company’s email
DMARC connects your domain’s email authentication results to a published policy. A successful rollout starts with a complete list of legitimate senders and careful delivery checks.
Read the visual guide
How a small club loses money through a fake treasurer email
A volunteer group can lose money through a plausible payment request, especially during a change of treasurer. Keep account ownership, payment verification, and a second review explicit.
Read the visual guide