Better Leaders. Better Results.
“The way a team plays as a whole determines its success.” — Babe Ruth I created software (and other solutions) at Microsoft for several years. It’s nice now and then to take a look back, and really figure out the core of what worked (and what didn’t). I reviewed my model for how I shipped …
Here is a map of the Information Technology Infrastructure Library (ITIL) v3. ITIL v3 is organized by ITIL stages, processes, and sub-processes. Via Wikipedia: “ITIL describes procedures, tasks and checklists that are not organization-specific, used by an organization for establishing a minimum level of competency.” You can find an explanation of the ITIL processes at …
I see a lot of confusion over terms when it comes to threat modeling. The terms matter because they shape focus. For example if you confuse threats with attacks, you’ve limited what you’re looking for. There are the terms we used when we created our How To Threat Model Web Applications: Asset. An asset is …
Here’s my trying to explain threat modeling (actually core modeling) to a customer … My core theme of the modeling is this: Define what good looks like (e.g. objectives) Establish boundaries of good (constraints, goals — what can’t happen, what needs to happen, what’s nice to happen) Identify tests for success (define criteria … entry …
When people ask me my take on model-driven approaches, I think of two ends of the spectrum — human and the machine. Model for Humans For humans, I find using a whiteboard (whiteboard modeling) works well — it’s universal. Model for Machines For machines, I find speaking closer to the code is a good thing …
