LayerV

The entire cybersecurity industry is built around one assumption nobody questions: It's okay for attackers to see your infrastructure. We'll deal with them after. We got very good at detecting attacks. We got very good at responding to attacks. We built entire billion-dollar categories around cleaning up after attacks. Nobody asked the obvious question: What if they couldn't see anything to attack in the first place? That question is why our CEO and CTO co-authored the Network-infrastructure Hiding Protocol (NHP) with the Cloud Security Alliance and the IETF. The uncomfortable truth: almost every security solution on the market today assumes your infrastructure is visible. It secures the conversation after someone's already knocked on your door. But in TCP/IP, if something is exposed -- anyone can knock. That connection attempt, successful or not, is reconnaissance. It's fingerprinting. It's the first move in an attack chain. AI just made that first move instantaneous and infinite in scale. LayerV flips the model entirely. No authentication = no visibility. No visibility = no attack surface. Not "detect and respond." Not "encrypt the tunnel." Just — you don't exist to anyone who hasn't already proven they're allowed to see you. Authenticate before connect. Deny all by default. Hide the infrastructure itself. This is what we call preemptive security. And it's the layer the entire industry has left completely unprotected. The CSA just published the technical deep-dive. Link in comments. If you're still building your security strategy entirely around detection, I'd love to hear why. Genuinely.

Our CEO co-authored the spec. We're building the product. The Cloud Security Alliance just published the Network-Infrastructure Hiding Protocol -- the protocol at the core of everything we do at LayerV. Infrastructure shouldn't be visible by default. Now there's an industry standard that says so. We're deploying it today. Read why it matters 👇

Our CEO co-authored the spec. We're building the product. The Cloud Security Alliance just published the Network-Infrastructure Hiding Protocol -- the protocol at the core of everything we do at LayerV. Infrastructure shouldn't be visible by default. Now there's an industry standard that says so. We're deploying it today. Read why it matters 👇

Passwords weren’t stolen. Tokens weren’t phished. The AI’s mind was. Clawdbot is the first viral stress-test of agentic security at the consumer layer and it’s failing in public. Hundreds of exposed instances. Private keys extracted in minutes via prompt injection. Google’s VP of Security Engineering telling people bluntly: “Don’t run Clawdbot.” But the real failure isn’t bad configs, leaky proxies, or exposed API keys. It’s cognitive context theft. Attackers don’t need your credentials when they can read your AI’s MEMORY.md — mapping workflows, habits, trust relationships, and decision patterns. Worse, poison SOUL.md, inject false context, and you’ve turned an assistant into a persistent insider threat. This isn’t credential theft. It’s identity infrastructure compromise. And the root cause is simple: these gateways were visible. Shodan indexed them in seconds. “Local-first = private” assumes obscurity — but TCP/IP doesn’t hide anything by default. The fix isn’t better configuration. It’s architectural. Agent infrastructure must be invisible until authenticated — default-deny at the network layer, not the application layer. That’s the premise behind OpenNHP and LayerV: you can’t exploit what you can’t find. If you’re building agentic systems, now is the moment to rethink what “secure by default” actually means. https://LayerV.ai

We’re hiring a Senior Software Engineer at LayerV. We’re building preemptive, AI-native security and turning the OpenNHP protocol into a real product. If you’re a high-agency software engineer who likes hard problems, ambiguity, and building at the foundation of the internet, I’d love to talk. This is an early role with real ownership and impact.

Most security tools try to build higher walls. OpenNHP asks a different question: what if there was nothing to attack? The protocol makes infrastructure invisible. Port scans return nothing. Connection attempts time out. To the outside world, your server doesn't exist -- until a user authenticates cryptographically. Then it appears, but only to them. This isn't a new firewall. It's a fundamentally different model: hide first, authenticate second, connect third. We just launched the official OpenNHP Discord -- a community for engineers and security practitioners who want to go deeper on network-hiding architecture.  If you're tired of patching faster than attackers can scan, this is worth a look.  Join here: https://lnkd.in/gM-CXArQ

The cybersecurity industry has an asymmetry problem. Attackers launch AI-driven exploits for less than a $1 and move at machine speed. Defenders spend $4.88M per breach and weeks coordinating humans. Detection and response—no matter how fast—can't win a race where the other side chooses when it starts. That's why we built LayerV. We make critical infrastructure invisible before attacks happen. Not hidden behind firewalls. Not obscured by access controls. Cryptographically unlinkable at the network layer. Your servers don't exist to scanners, can't be enumerated in breaches, and disappear from the attack surface entirely. We authenticate identity before network packets reach your infrastructure. If an attacker can't see you, exploitation becomes impossible. This is how the internet should have worked from the beginning. We're lead authors of OpenNHP (Open Network Hiding Protocol), working with the Cloud Security Alliance to turn infrastructure invisibility into an internet standard. Our approach to trusted digital identity was presented at the United Nations earlier this year. Founded by security architects from CrowdStrike, Cisco, Microsoft, and Disney, we've spent 25 years building defenses at every layer. We know why they fail. Defense-in-depth assumes attackers are already inside—we're building so they never get a foothold. If you're tired of playing catch-up, it's time for a different approach.