# Fritz Abelard

Fritz Abelard is a Technical Success Manager at Snyk who works with enterprise customers on developer security. Their posts focus on applying DevSecOps to AI-assisted software development and emerging security risks.

- Profile: https://b2binfluencer.marketing/creators/fritz-abelard/
- LinkedIn: https://www.linkedin.com/in/fritzabelard
- LinkedIn followers: 1,499
- Topics: artificial-intelligence, supply-chain, cybersecurity, ai-security
- Based on 13 dated posts, latest 2026-10-10

## Summary

Fritz Abelard is most useful for practitioner explainers on DevSecOps and security risks in AI-assisted software development.

- Best for: A security education or training brand selling to engineering leaders, with a practitioner explainer and checklist.
- Not for: A challenger developer-security vendor wanting independent, scored comparisons and criticism of incumbent tooling.
- Check first: Confirm scope, deliverables, approval, rates, and audience survey results before contacting them.

### Takeaways

- Security belongs where code is written, not added after release.
- Treat AI output as a draft and keep a human in the loop.
- Agentic AI needs its own threat vocabulary and checks, including prompt injection and MCP exploits.

## Main ideas

- **Security belongs where code is written, not after release**: Abelard argues that as AI moves through the software lifecycle, bolting security on after the fact stops working. Teams adopting AI coding assistants are trying multiple tools at once to speed up delivery, creating attack paths that legacy security tools were not designed to catch. The response they describe is what they call secure at inception: protection embedded in the coding loop, making security invisible in the way a customer said it should be—present, but not something developers have to stop and operate.
- **Treat AI output as a draft; keep a human in the loop**: Abelard argues that AI is a powerful collaborator, not an infallible authority, whether it is writing content, speeding up routine work or generating code. AI excels at boilerplate, synthesis and brainstorming; human expertise supplies final verification and domain-specific context. Model output can also fall back on oversimplified patterns that sound plausible, making a deliberate verification loop more useful than blanket trust or distrust.
- **Agentic AI needs its own threat vocabulary and checks**: Abelard names specific vulnerability classes and the mitigations released against them, rather than discussing AI risk in general terms. They argue that agentic systems, where models call tools and act in the development loop, open attack surfaces that existing static and runtime analysis do not cover. The posts introduce each threat alongside the response, giving readers both the risk and the check.
- **Technical success managers should back platforms, not point solutions**: Away from product news, Abelard argues that the strongest technical success managers choose employers whose roadmaps pull customers deeper into an ecosystem instead of solving one problem and stalling. In a point-solutions business, the role stays shallow and expertise does not compound; on a platform, the work accumulates. They frame this as a career decision with a consequence for companies, too: firms that treat technical success managers as replaceable parts are losing people who are already being recruited elsewhere.

## Work to read

- [Fritz Abelard on the LiteLLM supply-chain attack and Snyk’s agent-security response](https://www.linkedin.com/posts/fritzabelard_security-update-suspected-supply-chain-incident-activity-7443312800791240704-4uH8)
- [Treat AI output as a draft: human-in-the-loop verification](https://www.linkedin.com/posts/fritzabelard_ai-contentcreation-enhancedproductivity-activity-7364392356550234112-3JMT)
- [Explaining Toxic Flows and MCP-scan for agentic AI](https://www.linkedin.com/posts/fritzabelard_unmasking-the-toxic-flow-analysis-a-principled-activity-7355993102311964673-CNj0)
- [Secure At Inception: using MCP to protect AI coding assistants](https://www.linkedin.com/posts/fritzabelard_securingai-devex-development-activity-7359608580800458752-kXOe)
- [The technical success manager talent war](https://www.linkedin.com/posts/fritzabelard_technicalsuccessmanager-aidevsecops-mondayminddrift-activity-7424249562397257728-5XeW)

## Brand relationships

- **Snyk** (employment)
- **Invariant Labs** (mention)

## Partnerships

The seven posts show Abelard working inside Snyk and discussing the employer’s products, research and industry incidents, alongside personal commentary on technical customer success careers. Snyk announcements reflect their role there, not disclosed paid placements for outside brands. With roughly 1,500 LinkedIn followers on the listed account—a small audience by creator-marketing standards—Abelard may suit a focused campaign. Before planning, ask them directly about scope, deliverables, approval, available formats and costs; none are stated in the posts.

## Alternatives

- Motti Sorani: Choose Sorani when the campaign centers on remediation and proving security value, not naming new attack classes. Both posts argue that detection and visibility are only step one, and that the hard problem is the "last mile" — fixing vulnerabilities at scale without slowing development — using telecom's last-mile investment as an analogy. For a CTO-facing explanation of where checks belong in an AI build pipeline, that is a closer match to what a training vendor sells: a workflow that gets findings closed, not another alert source. Sorani also describes their route into offensive security through studying and generating computer viruses, giving a brand a usable origin story for an explainer opening.
- Ricardo Camacho: Choose Camacho when the buyer's AI-code risk sits inside embedded or regulated hardware products rather than web and cloud software. The posts cover cybersecurity across the full lifecycle of software-defined vehicles — telematics, ECU communications, over-the-air updates — and name the standard in play, ISO/SAE 21434. Camacho lays out the verification stack in concrete terms: static analysis early, dynamic analysis and fuzz testing during execution, penetration testing to validate defenses, secure coding, security gates in CI/CD, and AI-assisted verification with human oversight. For a CTO whose engineers ship firmware on long product lifecycles, that process-level answer meets their need more directly than commentary on AI coding tools.
- Jim Manico: Choose Manico when the campaign wants a stated position rather than a survey. Their argument is that AI agents are collapsing the economics of both finding and fixing vulnerabilities, that standalone scanners, SAST, DAST, IAST and CVE tooling will increasingly be displaced by AI-native capability, and that standards such as OWASP ASVS and AISVS matter more, not less, because they define what has to be verified. Manico also takes on the "AI cyber is BS" position directly, citing an in-progress attack on RubyGems by automated package publishing. For a CTO deciding whether to reorganize security work around continuous verification, that is the stronger provocation, and the standards framing gives a training vendor curriculum hooks for a checklist.

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