Expertise
See the system. Understand the stakes.
My work begins with relationships: between components, people, assumptions and consequences. Security modeling brings that wider view into focus.
The security perspective
Architecture is a series of decisions.
A system can meet a checklist and still carry risks at its boundaries. I look at how information moves, who can act, what the design assumes, and what happens when those assumptions fail.
Security modeling and threat modeling have distinct roles in that work. Together with architecture review and risk analysis, they help turn a complicated technical picture into clear priorities.
Security modeling
Build a coherent view of the system, its environment, dependencies and security objectives. Connect architecture and operational decisions with their wider consequences.
Threat modeling & scenario analysis
Examine trust boundaries, misuse cases and plausible attack paths. Use scenarios to challenge assumptions and identify where controls or design changes matter.
Architecture & design review
Review identity, access, data flows and dependencies across cloud, APIs and enterprise platforms. Translate exposure into practical security requirements and mitigation choices.
AI & emerging technology
Explore model and agent boundaries, sensitive data, delegated permissions and human oversight. Keep proposed mitigations connected to the way a system is actually used.
Risk communication & technical learning
Make findings understandable to engineers, decision-makers and learners. Explain trade-offs, document assumptions and help teams carry the reasoning into their next decision.
Intelligence & strategic inquiry
My studies in security, intelligence and diplomacy inform research into national security, strategic judgment and institutional preparedness. This perspective connects technical cyber risk with wider political and organizational questions.
How I approach a question
Understand. Challenge. Clarify.
Understand the context
Clarify the system, the people it serves, the constraints and the decisions that need to be made.
Challenge the assumptions
Trace dependencies and trust boundaries. Explore how a design behaves under plausible adverse conditions.
Clarify the way forward
Explain the exposure, the options and the reasoning behind a recommendation. Make the next decision actionable.