<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Founder</title>
    <description>The latest articles on DEV Community by Founder (@john_81b0116c51b419add424).</description>
    <link>https://dev.to/john_81b0116c51b419add424</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4131669%2Ff7bcbb4a-f364-418f-823d-56859fc64985.webp</url>
      <title>DEV Community: Founder</title>
      <link>https://dev.to/john_81b0116c51b419add424</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/john_81b0116c51b419add424"/>
    <language>en</language>
    <item>
      <title>Filed public security issue on CrewAI (#8621). Agent loop lacks cryptographic signatures (SOC2 blocker). CrewAI scores 0/100. I built the open-source fix. Proof here: https://nti-leaderboard.vercel.app</title>
      <dc:creator>Founder</dc:creator>
      <pubDate>Mon, 26 Oct 2026 14:36:29 +0000</pubDate>
      <link>https://dev.to/john_81b0116c51b419add424/filed-public-security-issue-on-crewai-8621-agent-loop-lacks-cryptographic-signatures-soc2-3mk9</link>
      <guid>https://dev.to/john_81b0116c51b419add424/filed-public-security-issue-on-crewai-8621-agent-loop-lacks-cryptographic-signatures-soc2-3mk9</guid>
      <description>&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
      &lt;div class="c-embed__body flex items-center justify-between"&gt;
        &lt;a href="https://nti-leaderboard.vercel.app" rel="noopener noreferrer" class="c-link fw-bold flex items-center"&gt;
          &lt;span class="mr-2"&gt;nti-leaderboard.vercel.app&lt;/span&gt;
          

        &lt;/a&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;


</description>
    </item>
    <item>
      <title>The Missing Layer: Why AI Agents Need a Post-Quantum Trust Standard</title>
      <dc:creator>Founder</dc:creator>
      <pubDate>Sat, 24 Oct 2026 17:36:46 +0000</pubDate>
      <link>https://dev.to/john_81b0116c51b419add424/the-missing-layer-why-ai-agents-need-a-post-quantum-trust-standard-3mgd</link>
      <guid>https://dev.to/john_81b0116c51b419add424/the-missing-layer-why-ai-agents-need-a-post-quantum-trust-standard-3mgd</guid>
      <description>&lt;p&gt;The Silent Crisis in AI Agent Execution&lt;/p&gt;

&lt;p&gt;As autonomous AI agents transition from experimental chat interfaces to operational infrastructure—executing database queries, issuing API requests, and managing cloud environments—a fundamental security vulnerability has emerged: the lack of non-repudiable tool execution chains.&lt;/p&gt;

&lt;p&gt;When a multi-agent system issues a financial wire, executes a database migration, or modifies access control lists, traditional logging captures what happened, but cannot cryptographically prove who authorized it or whether the tool call payload was tampered with in transit.&lt;/p&gt;

&lt;p&gt;In high-consequence enterprise environments, unverified tool execution creates three primary failure modes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Indirect Prompt Injection Exploitation: Adversaries manipulate context documents to inject unauthorized tool calls that execute under the application's service credentials.&lt;/li&gt;
&lt;li&gt;Audit Trail Repudiation: Incident response teams cannot verify whether a logged tool execution originated from a legitimate agent turn or a rogue sub-agent.&lt;/li&gt;
&lt;li&gt;Quantum Vulnerability Horizon: As RSA and ECDSA signatures near retirement ahead of post-quantum migration mandates (NIST FIPS 203/204/205), traditional JWTs and API tokens fail long-term compliance requirements.&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;The NTI Architecture: A 5-Pillar Trust Framework&lt;/p&gt;

&lt;p&gt;The Neutral Trust Infrastructure (NTI) specification defines an open trust layer designed to cryptographically bind agent execution turns, user identity, and tool invocation parameters.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Post-Quantum Envelope Signing: Every tool call argument payload is signed using post-quantum signature schemes (e.g., ML-DSA / Dilithium).&lt;/li&gt;
&lt;li&gt;Agent Identity Binding: Cryptographically ties user session contexts to agent execution sub-routines.&lt;/li&gt;
&lt;li&gt;Payload Digest Verification: Verifies tool output integrity before returning results back into LLM context.&lt;/li&gt;
&lt;li&gt;Immutable Event Logging: Generates hash-linked, tamper-evident audit traces for SecOps compliance.&lt;/li&gt;
&lt;li&gt;Zero-Trust Interoperability: Operates transparently across Python, Node.js, and Rust frameworks.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can read the full specification, which is actively being discussed in the W3C AI Agent Protocol Community Group, here: NTI-1 Spec&lt;/p&gt;




&lt;p&gt;One-Command Hardening: nti-scanner --fix&lt;/p&gt;

&lt;p&gt;Integrating cryptographic trust into existing codebases does not require re-architecting your application. Using the open-source Python CLI, developers can scan and automatically attach NTI compliance wrappers to execution handlers:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Install the scanner&lt;/span&gt;
pip &lt;span class="nb"&gt;install &lt;/span&gt;nti-scanner

&lt;span class="c"&gt;# Scan repository for unsigned tool execution handlers&lt;/span&gt;
nti-scanner scan ./src

&lt;span class="c"&gt;# Apply automated NTI compliance middleware wrappers&lt;/span&gt;
nti-scanner &lt;span class="nt"&gt;--fix&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;Automated Pipeline Enforcement: GitHub Marketplace Action&lt;/p&gt;

&lt;p&gt;To enforce agent trust controls across engineering teams, add the NTI Security Gate to your GitHub Actions workflow. You can find it in the GitHub Marketplace:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;AI Agent Security &amp;amp; Compliance Gate&lt;/span&gt;

&lt;span class="na"&gt;on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;pull_request&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;branches&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;[&lt;/span&gt; &lt;span class="nv"&gt;main&lt;/span&gt; &lt;span class="pi"&gt;]&lt;/span&gt;

&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;nti-trust-check&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;runs-on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ubuntu-latest&lt;/span&gt;
    &lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;actions/checkout@v4&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Run NTI Security Gate&lt;/span&gt;
        &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;abisheakp197/nti-scan-action@v1.0.0&lt;/span&gt;
        &lt;span class="na"&gt;with&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
          &lt;span class="na"&gt;fail-on-vulnerability&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Build verifiable AI agents. Inspect the ecosystem and live registry at nti-registry.vercel.app.&lt;/p&gt;




</description>
      <category>ai</category>
      <category>security</category>
      <category>opensource</category>
      <category>cryptocurrency</category>
    </item>
    <item>
      <title>The World Is Automating Rapidly. We Are Building the Trust Infrastructure That Controls It.</title>
      <dc:creator>Founder</dc:creator>
      <pubDate>Fri, 18 Sep 2026 14:03:32 +0000</pubDate>
      <link>https://dev.to/john_81b0116c51b419add424/the-world-is-automating-rapidly-we-are-building-the-trust-infrastructure-that-controls-it-40mi</link>
      <guid>https://dev.to/john_81b0116c51b419add424/the-world-is-automating-rapidly-we-are-building-the-trust-infrastructure-that-controls-it-40mi</guid>
      <description>&lt;p&gt;Every major tech era—cloud, online payments, mobile operating systems—was defined by the core infrastructure built beneath it.&lt;br&gt;
We are entering a world dominated by autonomous AI agents, robotics, software execution, and automated machine-to-machine interactions. But this multi-trillion-dollar transition faces a critical flaw: a total lack of deterministic security and trust. Probabilistic safety prompts cannot guarantee control when machines execute financial transactions or high-stakes commands.&lt;br&gt;
The Opportunity: Building the Next Infrastructure Giant&lt;br&gt;
We are building Neutral Trust Infrastructure (NTI)—a high-barrier, commercially protected cryptographic gateway for autonomous systems.&lt;br&gt;
Instead of soft guidelines, NTI uses Ed25519 capabilities, Merkle chains, TEE hardware enclaves, and Rust-based zero-knowledge virtual machines (zkVMs) to create an unbreachable mathematical fence. It determines what autonomous systems can verify, block, and execute.&lt;br&gt;
This is not a temporary side project or an ordinary utility crate. This is the foundational protocol layer designed to secure future machine commerce—built from day one to scale into an enterprise infrastructure powerhouse alongside industry giants.&lt;br&gt;
Why Join as a Core Developer?&lt;br&gt;
Great infrastructure isn't built by huge committees at the start—it's forged by top engineers who recognize ground-floor opportunities before the rest of the market catches on.&lt;br&gt;
Elite Systems Engineering: Natively written in high-performance Rust for ultra-low latency and total memory safety.&lt;br&gt;
Uncompromising Security: Combining zero-knowledge execution proofs (zkVM) with immutable cryptographic audit chains.&lt;br&gt;
Commercially Protected Open Source: Protected under the PolyForm Shield license to secure IP and build long-term enterprise value while maintaining an open developer ecosystem.&lt;br&gt;
Get Involved Today&lt;br&gt;
The foundation is live, public, and moving fast. We are opening initial architecture tasks for developers who want to contribute core code and help shape a high-value technology startup from the ground up.&lt;br&gt;
📌 GitHub Repository: &lt;a href="https://github.com/abisheakp197/Neutral-Trust-Infrastructure" rel="noopener noreferrer"&gt;https://github.com/abisheakp197/Neutral-Trust-Infrastructure&lt;/a&gt;&lt;br&gt;
🏷️ Look for issues tagged good first issue and help wanted.&lt;br&gt;
If you have the technical drive to build the security stack governing the automated world, pick an issue, open a pull request, or join our technical discussions today&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>opensource</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
