Lyrie.ai Wants A Piece Of CrowdStrike's $90B Empire: Inside The First Batch Of Anthropic's CVP

2026-05-14 · Source: HackerNoon · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Cybersecurity & Data Privacy, Emerging Technologies & Innovation · Depth: Advanced, long

Summary

Dubai-based OTT Cybersecurity LLC, operating as Lyrie.ai, has announced three coordinated initiatives to address critical security gaps in the emerging AI agentic era. These include a real-time zero-day disclosure system for global enterprise infrastructure, acceptance into Anthropic's inaugural Cyber Verification Program (CVP), and the public release of the Agent Trust Protocol (ATP). The ATP is an open cryptographic standard designed for AI agent identity, scope, attestation, delegation, and revocation, aiming to become a foundational internet standard. This move comes as data indicates a dramatic collapse in time-to-exploit for vulnerabilities, from 745 days in 2020 to 44 days in 2025, with 32% of known exploited vulnerabilities in H1 2025 being exploited on or before CVE publication. Lyrie.ai positions itself to unify threat intelligence and identity controls, a departure from traditional cybersecurity models.

Key takeaway

For CTOs and VPs of Engineering deploying autonomous AI agents, Lyrie.ai's Agent Trust Protocol (ATP) offers a critical, missing identity and authorization layer. You should assess ATP's potential to standardize agent security within your enterprise, especially given the accelerating pace of zero-day exploits. Integrating such a protocol could significantly reduce breach risks and operational vulnerabilities associated with unverified AI agent actions.

Key insights

Lyrie.ai introduces a comprehensive security framework for AI agents, combining real-time threat intelligence with a cryptographic identity protocol.

Principles

• AI security is foundational, not an add-on.
• Real-time intelligence flips attacker advantage.
• Open standards drive ecosystem adoption.

Method

Lyrie.ai's autonomous threat intelligence engine continuously monitors global infrastructure and agent-to-agent communication to identify zero-days, generating disclosure and remediation packages within hours of discovery.

In practice

• Implement ATP for AI agent identity verification.
• Prioritize real-time vulnerability monitoring.
• Evaluate vendors offering unified AI security.

Topics

• AI Agent Security
• Agent Trust Protocol
• Zero-Day Exploits
• Real-Time Threat Intelligence
• Anthropic Cyber Verification Program

Code references

• OTT-Cybersecurity-LLC/lyrie-ai

Best for: CTO, VP of Engineering/Data, Executive, AI Security Engineer, AI Architect, Director of AI/ML

Related on AIssential

• Securing the Swarm: Governance, Attack Surfaces, and Zero-Trust Architectures in Multi-Agent AI Environments — Securing multi-agent AI demands a shift from internal model alignment to external cryptographic controls and zero-trust governance.
• TrustedARI: Towards Trust-Native Agentic Routing Infrastructure for Agentic AI — TrustedARI secures AI agent interactions with external services via novel cryptographic protocols, ensuring privacy and verifiable transactions.
• ALERT: Why Big Tech Is Panicking - Anthropic's 'Mythos' Finds Zero-Day Bugs No One Knew Existed — AI models like Anthropic's Methos can detect zero-day vulnerabilities, initiating a critical cyber arms race.
• Zero Trust Doesn't Fully Solve the Agentic AI Problem — Agentic AI's autonomous nature creates security gaps that Zero Trust alone cannot fully address.
• 🗞️ Anthropic launched Claude Code Security to scan your code repositories for bugs and suggest security patches. — AI is advancing in code security, robotics platforms, and developer tools, yet faces challenges in user adoption and intellectual property protection.
• Why AI Agents Break Zero Trust at the Last Mile — The "agentic last mile" is a security gap between AI agents and legacy systems, risking identity and context loss.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by HackerNoon.