# John Jeremiah

John Jeremiah shares cybersecurity content on LinkedIn, including posts about API security, security automation, and security operations frameworks.

- Profile: https://b2binfluencer.marketing/creators/john-jeremiah/
- LinkedIn: https://www.linkedin.com/in/johnjeremiah
- LinkedIn followers: 3,440
- Topics: artificial-intelligence, cybersecurity, zero-trust
- Based on 11 dated posts, latest 2026-10-04

## Summary

John Jeremiah is most useful for accessible thought leadership on API security, security automation and security operations.

- Best for: A security automation or API security vendor hosting a thought leadership webinar.
- Not for: A named reviewer for head-to-head SOAR lab tests with raw benchmarks and guaranteed audience results.
- Check first: Ask for job title, original analysis examples, and recent reach and engagement data.

### Takeaways

- Slow automation is described as a security team's biggest vulnerability.
- A 2025 report says 81% prioritize automation but only 6% have mature programs.
- A SOC framework defines terms before describing how teams choose based on size, industry and risks.

## Main ideas

- **Slow automation is the vulnerability, and time to automation is the metric to manage**: John Jeremiah argues that understaffed security teams are overwhelmed while attackers keep accelerating, and that the problem is not a lack of automation tools but how long it takes to put them to work. Traditional SOAR platforms get singled out because they demand coding and scripting before workflows run, which keeps response slow. The proposed alternative is to measure Time to Automation and use AI-driven workflows to collapse that time. The specific numbers come from a linked blog by Traceable co-founder and chief executive Gil Barak, not from the post itself: an expected cybersecurity talent gap of 85 million workers by 2030, and a claim that faster automation cuts response times by 99.999%.
- **Automation is framed as the answer to the security skills gap**: John Jeremiah treats staffing shortfalls as the entry point for automation arguments. The claim runs: repetitive tasks are moved off human analysts, fewer manual interventions mean faster and more accurate threat detection, and companies that do this improve security while cutting costs. This is the same staff-pressure logic as the Time to Automation post, but expressed as cost and workload relief rather than as a response-time metric.
- **Adoption is stuck between stated priority and real maturity**: The argument is that security leaders already agree automation matters, and the gap is operational. Most organisations call automation a top strategic priority, yet few describe their programs as mature. Deployment friction and the absence of continuous optimisation are presented as the actual blockers, with centralised teams and AI agents for threat detection as emerging responses. The figures belong to the BlinkOps 2025 State of AI-Driven Security Automation report, based on a survey of more than 1,000 security decision-makers.
- **Fundamentals still matter: a SOC framework decides whether response is organised or reactive**: On day-to-day operations, the position is more instructional than argumentative: threats arrive through phishing, weak passwords and software flaws, and teams need a structure to catch them early. A SOC framework is described as a blueprint for staying organised, setting priorities and reacting faster; without one, operations become messy, slow and reactive. Framework choice depends on company size, industry and risk rather than on one best option.
- **Pair live demonstration with expert explanation when presenting security technology**: Across the posts, a recurring delivery priority is to show and discuss claims about security products, not just announce them. Product demonstrations are paired with expert talks on the same subject, and the chosen topics — API security, Zero Trust, fraud — reflect where John Jeremiah expects buyer attention to sit.

## Work to read

- [Slow automation is a security team's biggest vulnerability](https://www.linkedin.com/posts/johnjeremiah_slow-automation-is-now-a-security-teams-activity-7305266513781936129-Agem)
- [2025 State of AI-Driven Security Automation report findings](https://www.linkedin.com/posts/johnjeremiah_the-2025-state-of-ai-driven-security-automation-activity-7351721365332271105-qJXR)
- [What a SOC framework is and how to choose one](https://www.linkedin.com/posts/johnjeremiah_hackers-are-always-looking-for-ways-in-whether-activity-7306352923154735104-Fi-z)
- [Is automation the answer to the cybersecurity skills gap?](https://www.linkedin.com/posts/johnjeremiah_is-automation-the-answer-to-the-cybersecurity-activity-7307789136218763264-cA_1)
- [Black Hat USA 2023 booth programme](https://www.linkedin.com/posts/johnjeremiah_join-traceable-at-black-hat-usa-2023-activity-7092881877908209664-tWfX)

## Brand relationships

- **Traceable** (employment)
- **BlinkOps** (employment)

## Partnerships

John Jeremiah's posts do not mention a creator-side partnership program, sponsorship policy, rate card, or booking route. They mostly promote companies and events from a Traceable team perspective: an invitation to meet the team at Black Hat USA 2023 for product demos, booth talks, and prizes; a pointer to a Traceable co-founder's blog on security automation speed; a pointer to a SOC framework blog; a summary of BlinkOps' 2025 State of AI-Driven Security Automation report with a download link; and a note about a Traceable sales director joining a Cybovate panel on the cybersecurity skills gap. The posts show co-marketing with employers and industry events, but not paid formats or terms. Ask directly about available formats, scope, and terms.

## Alternatives

- Anuj Goel: Choose Anuj Goel over John Jeremiah when the webinar centers on operationalizing threat intelligence with AI agents, not the adoption speed of security automation. Their posts address which AI agents actually deliver results, naming four practical tests: contextualizing a threat against the organization's own assets, environment, and priorities; deciding whether a newly disclosed vulnerability creates meaningful risk; prioritizing intelligence instead of deepening analyst fatigue; and carrying intelligence from what an analyst knows to what the organization has acted on. The second post adds a concrete vendor example: Cyware's partnership with Armis from ServiceNow to enrich external threat feeds with customer-specific asset context and operationalize them into Agentic AI workflows. That makes this a tighter fit for a vendor webinar that wants to demonstrate AI agents working on real operational problems rather than re-explain the automation backlog.
- Jonathan Baker: Choose Jonathan Baker over John Jeremiah when the webinar should center on prioritization and proof rather than automation adoption. Their posts offer a usable four-action spine: map crown jewels through the adversaries relevant to industry, geography, and technology; validate defenses against documented TTPs rather than generic scenarios; inventory AI exposure, including agents, automation frameworks, and MCP servers; and accelerate detection engineering so alert triage, SIEM correlation, and containment can run at AI-augmented attack speed. The threat-debt post sharpens that into a memorable claim: findings in a backlog are not dangerous on their own; they become dangerous when they line up into a path an adversary can walk. For a vendor webinar, that supports a segment on choosing what to fix first with evidence rather than patch volume.
- Muli Motola: Choose Muli Motola over John Jeremiah when the webinar's topic is identity and access management as the breach path, not API security and automation. Their posts frame a differentiated CISO conversation: unauthorized data access as the nightmare scenario; the point that unauthorized access can itself be a reportable incident and trigger GDPR fines even without exfiltration; the dual requirement to keep unauthorized users out while preserving authorized investigation and legal access; and the operational risks from privileged access and overlooked legacy systems. The Identity Nightmares interview series gives the webinar a ready-made format: a named practitioner tells a failure story and draws out lessons.

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