Blog

A leadership philosophy shaped by lacrosse, Auth0 values, and real-world security work.

The Future of the Economy with AI Embedded Into Everyday Work From Housekeeping Robots to AI Lawyers: A Glimpse into 2045 The march of artificial intelligence (AI) into nearly every aspect of work is no longer speculative — it is inevitable. Over the next 20 years, as AI evolves from a niche tool to an omnipresent worker, the economy, labor markets, and the very idea of “work” will undergo profound transformation. ...

The Future Isn’t Coming — It’s Already Here Several leading AI and research companies are actively exploring the deployment of AI-powered “employees” within enterprise environments. These aren’t your typical chatbots — they’re fully autonomous agents with persistent memory, role-based access, credentials, and the ability to perform tasks independently, often with system-level permissions. Now ask yourself: Is your risk program ready to onboard a non-human employee? Why This Matters for GRC Let’s cut through the hype and get real about what this means for Governance, Risk, and Compliance. ...

Why I Decided to Build My Blog In an world where platforms like Substack, Medium, and LinkedIn dominate the content landscape, you might wonder—why bother coding your blog? For me, it came down to three things: Ownership: Full control over my content, design, and data Learning: Improving my coding skills, even starting simple Creative Freedom: No platform restrictions I wanted a clean, fast, no-bloat experience that I could fully control, learn, update, and evolve over time. Step 1: Choosing Hugo I chose Hugo, a popular static site generator, because: ...

Introduction PCI DSS 4.0 introduces Requirement 11.6.1, a new expectation to secure the client side of e-commerce environments. This isn’t a minor update. It is a hard reality check where organizations must detect unauthorized changes directly in consumers’ browsers. Traditional server-side protections are no longer enough. What PCI DSS 11.6.1 Requires Requirement 11.6.1 mandates that organizations: Implement mechanisms to detect and alert on unauthorized changes to payment page content and scripts as they load in the consumer’s browser. Specifically, address client-side security, where the user interacts with the page — not just what resides on the server. Evaluate these controls either continuously or at least once every seven days, unless a targeted risk analysis justifies an alternate frequency. Simply, companies must now actively monitor what customers see and interact with, not just what was deployed from their servers. ...