Agent identity & access
Treat an agent as an actor with an owner, a purpose, and permissions that can be inspected and revoked. Follow what it can do across connected systems.
Who owns the agent and the access behind it?
Read this topic →Cybersecurity for accountable leaders
Practical security reading for the decisions that cannot wait: agent access, AI defense, and incident response. Clear ownership before the pressure arrives.
Choose your next question
Treat an agent as an actor with an owner, a purpose, and permissions that can be inspected and revoked. Follow what it can do across connected systems.
Who owns the agent and the access behind it?
Read this topic →Connect model behavior to application controls. Focus on the data, tools, and business actions that turn a bad answer into a consequential incident.
What could a manipulated answer actually cause?
Read this topic →Prepare decision-makers as well as responders. Establish authority, credible communications, and recovery criteria before an incident compresses the timeline.
Who can make the next critical decision?
Read this topic →From the archive, refreshed
Original titles and article paths, revisited with current guidance and practical next steps. Each edition shows what was refreshed and when.
A connected agent needs an accountable owner and a bounded identity. Start with what it can reach, then test what it is allowed to do.
Defend the application around the model: the inputs it trusts, the data it reaches, and the actions it can take.
A response plan is a decision system. Rehearse authority, communication, and recovery, not just the technical investigation.
Turn a broad security score into a specific business scenario, an evidence-based estimate, and a decision someone owns.
Revisit seven ransomware assumptions with a practical recovery checklist, updated for current leadership discussions.
Translate recovery ambitions into business priorities, decision authority, tested dependencies, and measurable evidence.
Seven practical decisions turn recovery targets into a service the business can actually resume.
MFA protects sign-in, while application consent creates another access decision. Review both before trusting connected tools.
Give employees a useful approved route for AI work, with clear boundaries for data, integrations, and consequential decisions.
Improve patching speed by removing ownership and validation delays while keeping priority tied to actual exposure.
Voice impersonation changes what a familiar call can prove. Build verification into urgent payments, access changes, and sensitive requests.
Treat the software delivery pipeline as privileged infrastructure, with explicit trust boundaries from source changes to production.
A practical reading room
Explore the decisions behind the technology. Each reading path connects a refreshed article, clear questions, and a focused brief for event organizers.
About this publication →Bring the conversation to your event
Use these topic briefs to plan a focused leadership discussion, then explore relevant speaking resources.