# Phillip Shoemaker

Phillip Shoemaker writes about cybersecurity, digital identity, and how to make AI systems safer and more accountable. Shoemaker is the author of *Unbreakable: Secure Your Digital Life in a World Built to Breach You*.

- Profile: https://b2binfluencer.marketing/creators/phillip-shoemaker/
- LinkedIn: https://www.linkedin.com/in/shoemaker
- Topics: artificial-intelligence, cybersecurity, agentic-ai, ai-agent-security
- Based on 22 dated posts, latest 2026-10-07

## Summary

Most useful for thought leadership on AI agent identity, delegated authority, and auditability.

- Best for: Cybersecurity or AI governance brand seeking commentary, byline, webinar, or conference content.
- Not for: Consumer brand paid performance influencer campaign needing guaranteed reach and conversion tracking.
- Check first: Confirm audience composition data, comparable-post results, and whether they accept sponsorships.

### Takeaways

- AI agents need distinct identities, limited authority, and records of what they do.
- An agent's objective and its authority are separate decisions.
- Deepfake defenses should verify permission for an action, not rely on recognizing a face.

## Main ideas

- **AI agents need their own identity, not a borrowed login**: Shoemaker argues that enterprise identity was designed for two groups: people and machines. AI agents authenticate like machines but behave in ways machine accounts never did. They choose tools, change plans, delegate tasks, spend money, write code and act on someone else's behalf. An API key cannot answer the questions that matter: which agent is this, who created it, which person or organization does it represent, what authority was it given, when does that authority expire, and what has it already done? Shoemaker's position: every consequential agent should carry a distinct identity, an accountable principal, explicit delegated authority, purpose-bound permissions, short-lived credentials, complete auditability and immediate revocation.
- **What an agent wants to do and what it is allowed to do are separate decisions**: Across several posts, Shoemaker makes the same architectural point: intent and authority should not be decided by the same system. Agents constantly consume untrusted material such as email, websites, documents, CRM records and support tickets. That material can change what an agent thinks it should do; it should never change what the agent is permitted to do. Shoemaker proposes an authorization layer outside the model that checks each action against rules—public resources only, read-only access, no authentication bypass, no exploiting misconfigurations, and human review when access looks unintended—then blocks and logs anything that crosses the line. The intelligent system can be creative; the access-control system should not be.
- **Trust is becoming an engineering discipline, not a marketing slogan**: Shoemaker's broadest argument is that technology has been judged by what it can do, but AI is forcing a different measure: how dependable it is. Verifying where content came from, proving it has not been altered, identifying who approved it, and distinguishing a model's contribution from a person's become product requirements, not legal or public-relations problems. Shoemaker points to a pattern: encryption arrived before e-commerce took off, identity management before enterprises trusted the cloud, and secure app ecosystems before people stored their lives on phones. In the same vein, they argue AI's obstacle is confidence rather than intelligence: organizations need to know whether they can verify what happened, explain a decision, audit it months later, and prove who or what started an action.
- **Deepfakes attack human recognition, so the fix belongs in authorization**: Shoemaker separates three questions that are usually collapsed into one. “Who does this look like?” is recognition. “Who can cryptographically prove control of an identity?” is authentication. “Is that person allowed to act?” is authorization. Deepfake fraud targets recognition, using a familiar face and voice to trigger a payment. That's why Shoemaker argues that training employees to spot synthetic pixels puts them in an arms race against generative AI they will lose. The better goal is to make the face irrelevant to the transaction: a payment request needs authorization, a second approver, a destination account verified through its own channel, and a record of evidence tied to that specific action.
- **Detecting a fake is not the same as clearing the rights behind it**: On synthetic media, Shoemaker draws a line between evaluating an artifact after it exists and deciding permission before anything is generated. Detection asks whether shadows are consistent or audio matches the environment. Authorization asks whether this is a protected likeness, who controls it, whether the use is permitted and what restrictions apply. Shoemaker considers detection necessary because criminals will not ask permission, but argues that legitimate platforms should be able to check permission first, the way banks authorize transfers rather than only investigating fraud afterwards.
- **An agent's identity can persist while its permissions expire**: Shoemaker compares always-on agents to employees who accumulate access with every role change, except forgotten permissions held by autonomous software can still be exercised. Their proposal is temporary authority: the agent's identity, memory and objective can persist, but permissions run on a clock. Access is granted for a period and renewed only if still needed; message sends are capped, spending gets a budget with an end date, and changes such as a model upgrade, a new tool, growing memory or delegation switched on trigger a fresh review. Shoemaker also insists that goals and authority stay separate.
- **Record what an agent did, not what it thought**: Shoemaker frames accountability as three layers: identity says who acted, authorization says what that actor was allowed to do, and accounting says what it actually did. When an agent goes beyond its instructions, the user, developer, model provider and operator can each truthfully say the action was not theirs. The factual record therefore has to stand on its own. Shoemaker advises logging consequential actions—a resource accessed, a credential used, data sent somewhere, money spent, another agent created, or a request blocked—rather than every internal thought, which creates its own privacy and security problems.
- **The valuable skill is knowing what not to automate**: Not all of Shoemaker's writing is about agents and fraud. In one post, they argue that the companies creating the most value over the next decade will not be those that automate the most, but those that understand where people still create disproportionate value. AI already handles summarizing, drafting, translating, writing code, organizing data and finding patterns well, and keeps improving. The moments that stay human are not about intelligence but about accountability, judgment and trust. Shoemaker argues that AI may raise the value of curiosity, taste, integrity, leadership, persuasion and the willingness to take responsibility when something goes wrong.

## Work to read

- [Yesterday, something happened in cybersecurity that I think we'll look back on as an important architectural shift.](https://www.linkedin.com/posts/shoemaker_yesterday-something-happened-in-cybersecurity-activity-7501298404027736064-JB2S)
- [We Are Entering the Era of 'Trust Engineering'](https://www.linkedin.com/posts/shoemaker_we-are-entering-the-era-of-trust-engineering-activity-7490080145144463360-A8Ee)
- [California's attorney general has subpoenaed OpenAI over cybersecurity incidents involving its AI agents.](https://www.linkedin.com/posts/shoemaker_californias-attorney-general-has-subpoenaed-activity-7512649726366838784-60GU)
- [OpenAI introduced Dots this week, a class of always-on AI agents that pursue goals across apps over time.](https://www.linkedin.com/posts/shoemaker_openai-introduced-dots-this-week-a-class-activity-7511546833517690880-0oC-)
- [Your face is becoming a username. That's a problem.](https://www.linkedin.com/posts/shoemaker_your-face-is-becoming-a-username-thats-activity-7508172920721166338-m5c9)
- [AI Doesn't Have a Trust Problem. Businesses Do.](https://www.linkedin.com/posts/shoemaker_ai-doesnt-have-a-trust-problem-businesses-activity-7485136504017547264-6Kur)
- [Your company spends six figures on security tools. Then someone on your team takes a deepfake call from the 'CFO' and wires the money anyway.](https://www.linkedin.com/posts/shoemaker_your-company-spends-six-figures-on-security-activity-7508563293716803584-MjKd)

## Brand relationships

- **Apple** (employment)
- **Wiley** (disclosed_partnership)
- **Barnes & Noble** (mention)
- **Amazon** (mention)
- **FOX 5 DC** (mention)

## Partnerships

The posts describe a bulk-book offer, not a sponsorship program. Phillip Shoemaker sells *Unbreakable: Secure Your Digital Life in a World Built to Breach You* (Wiley) with speaking, coaching, and workshop add-ons tied to copy counts; buyers arrange orders by direct message. The posts disclose no sponsored posts, newsletter sponsorships, affiliate arrangements, public rate card, media kit, or inquiry form. If you’re considering a sponsorship, ask whether Shoemaker accepts them and request rates and terms. The book is also sold through Amazon and other booksellers. One post promotes a Barnes & Noble member pre-order discount code, a retailer promotion rather than a partnership route.

## Alternatives

- Amit Sinha: Amit Sinha is the stronger alternative when a campaign needs a named product and platform answer to the same agent-identity need. Their posts explain an AI Agent Passport that cryptographically binds an agent's workload identity to scoped authorization, accountable ownership, expiration, renewal, revocation, and audit evidence, as well as an NVIDIA OpenShell checkpoint that enforces what an agent can access and do. For a cybersecurity vendor or AI-governance buyer seeking co-authored thought leadership on verifiable identity, PKI, runtime attestation, policy-bound authority, and a kill switch, this offers a concrete architecture and partnership narrative rather than a general argument.
- Steven Wolfe Pereira: Steven Wolfe Pereira is the stronger alternative for campaigns aimed at boards, audit committees, and governance leaders rather than security architects. Their posts cover persistent personal and specialist agents, delegated authority for procurement, invoice processing, customer support, and contracting, and the questions management should answer before granting an agent consequential authority: what it can decide, which actions need human approval, who owns mistakes, what evidence records approvals, and who can suspend access. They also write about independent evaluation as operating infrastructure, including evaluator independence, access, transparency, board communication, and governance by evidence.
- Craig McLuckie: Craig McLuckie is the stronger alternative for campaigns focused on MCP security, platform engineering, and enterprise deployment architecture. Their posts describe conversations with more than forty enterprise platform teams about responsible MCP deployment and concrete problems: identity passthrough, OAuth token exchange, on-behalf-of tokens, virtual MCP server composition, least-privilege tool execution, provenance, audit trails at the mediation point, egress control, and silent capability drift. For campaigns about securing agent tool access or evaluating MCP platforms for a large enterprise, they offer operational specifics and an infrastructure-layer argument absent from Shoemaker's posts.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/