107 days ago · Tech · hide · Fediverse post

Part 4 of the Blue Team Fundamentals track in my CybersecKyle Security How-To Series uses one small system to connect architecture, abuse paths, controls, and tests before the design becomes expensive to change.Threat modeling often fails under a scope called “the whole business.” The diagram grows, every dependency leads to another meeting, and the people building the next release leave without a decision. A useful first model can fit on one page if the target and the questions are narrow enough.OWASP’s Threat Modeling Cheat Sheet organizes the work around four questions: what are we working on, what can go wrong, what will we do about it, and did we do a good enough job? The framework is intentionally methodology-neutral. STRIDE, attack trees, misuse cases, and other methods can add rigor later; the first job is to understand the actual system.Choose a decision-sized targetGood targets have an owner and a boundary:The newsletter signup and unsubscribe flowThe personal-site…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town