Showing 1–4 of 4 articles
What a security finding should contain
A useful finding gives its owner enough information to understand and verify the problem. Identify the affected asset, safe evidence, practical consequence, and a correction with a clear completion test.
Read the visual guide
Secure defaults people will leave switched on
A protective default is effective when people can complete real work without disabling it. Build a usable route for legitimate exceptions and test the resulting behavior.
Read the visual guide
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
Plugin and package risk: check the dependency you actually deploy
A useful dependency brings another project’s code into your environment. Review its source, maintenance, permissions, version, and update path before making it part of a critical service.
Read the visual guide