Enterprise Security Engineering
How identity, endpoints, email, data protection, and detection have to work together after the product is deployed and someone has to operate it.
SPEAKING
Speaking & Technical Presentations
I enjoy helping technical and non-technical audiences better understand cybersecurity, engineering, and the systems that shape modern organizations. My goal is to make complex ideas understandable without oversimplifying them.
Topics I enjoy discussing
These are problems I have worked on, studied, or continued to build around. I would rather narrow a session to a useful question than cover a broad subject at conference speed.
I shape the examples and technical depth around what the people in the room are trying to understand.
01 02 Identity & Access Management
How Conditional Access, privileged access, passkeys, certificates, and recovery paths fit together, including the support and ownership work behind them.
03 AI Security & Governance
How organizations can adopt AI without losing track of data handling, access, third parties, and accountable decisions.
04 Human-Centered Cybersecurity
What changes when security design starts with actual workflows, support burden, and failure recovery instead of assuming the user is the problem.
05 Secure Software Engineering
What building APIs, authorization flows, data models, and tests has taught me about assumptions that policy and architecture diagrams can hide.
06 Risk, Architecture & Systems Thinking
How I work through trust boundaries, dependencies, failure modes, and ownership before choosing a product or writing a standard.
07 Explaining Technical Risk
How to give executives, legal, compliance, and engineering teams enough technical context to make a decision without replacing uncertainty with fear or jargon.
How I approach technical communication
I start with the problem, the people affected, and the decision in front of them. Then I add the technical depth the room needs. I use examples from actual engineering work, name constraints and uncertainty, and leave room for questions rather than presenting a neat answer where one does not exist.
- Start with the problem
- Explain the decision, not only the technology
- Use real constraints and examples
- Say what is known and what is uncertain
- Adjust the depth to the room
- Leave time for questions
- Treat security as engineering work
Audiences I enjoy serving
I have had to explain the same security decision to engineers, executives, legal and compliance partners, and people responsible for daily operations. Each group needs different context, but nobody benefits from being talked down to.
I am most useful when the audience wants to work through a real problem rather than receive a polished sales presentation.
- Executive leadership
- Engineering organizations
- IT professionals
- Cybersecurity practitioners
- Colleges and universities
- Veteran organizations
- Community organizations