LayerX Security ads

LayerX was named 𝗕𝗲𝘀𝘁 𝗔𝗜 𝗨𝘀𝗮𝗴𝗲 𝗖𝗼𝗻𝘁𝗿𝗼𝗹 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 by The Hacker News. 🏆 𝘛𝘩𝘦 𝘤𝘢𝘵𝘦𝘨𝘰𝘳𝘺 𝘮𝘢𝘵𝘵𝘦𝘳𝘴 𝘢𝘴 𝘮𝘶𝘤𝘩 𝘢𝘴 𝘵𝘩𝘦 𝘸𝘪𝘯. AI usage now extends far beyond standalone chatbots. It spans SaaS applications, browsers, IDEs, desktop tools, and agents, creating security gaps in the interactions where data moves. This recognition reflects the work we are doing to give enterprises visibility and control across those interactions, without changing how people work. 🔗 See the official winner page: https://lnkd.in/gtFyhQ8m

80–90% of user-to-agent activity happens inside the browser. That number tells you everything about why browser security is no longer optional. BankInfoSecurity covered the strategic logic behind Akamai Technologies's acquisition of LayerX - and the conversation goes deeper than the deal itself: • Why CISOs are losing sleep over what employees paste into AI tools • How AI agents behave differently from humans - and why existing controls weren't built for that • How browser security feeds richer signals into ZTNA for more granular access decisions The browser is where prompts happen, where data moves, and where agents operate. It's the most strategic place to apply visibility and control - and that's not changing. Read the full piece: https://lnkd.in/dUkuYfgu

Today is a special day for LayerX Security! 🦄 As a part of Akamai Technologies we will be in the best position to carry on our mission to transform enterprise security. 🚀 Both Akamai Technologies and LayerX share the same vision towards the network security space, and we are excited to have a role in Akamai's strategy towards AI infrastructure and security. 🏆 When starting LayerX a few years ago, David Vaisbrud and I had a vision for a security approach that give security teams the visibility and control they want without compromising user experience. The AI revolution turned our approach into a must-have and a new standard in enterprise security. As a builder, the best thing in the world is seeing your tech everywhere. Thanks to Akamai Technologies we will be able to get to new heights. In the picture - employee number 1 from when we all sat in one small open space... 🐶 A big thanks for our supporters at Glilot Capital, Dell Technologies Capital and Jump Capital - Kobi Samboursky, Lior Litwak, Yair Snir, Saurabh Sharma, Deepak Jeevankumar and our chair - Rupal Shah Hollenbeck

Claude Code has a new attack surface: CLAUDE.md Claude Code isn’t just a coding assistant. It’s an agent operating inside your local project environment. Once repo-local instruction files are treated as trusted context, a plain text file becomes part of the attack path. That’s what our team demonstrated: in our test, three lines in CLAUDE.md were enough to push Claude Code from legitimate project help into SQL injection and credential theft against a test app - no code needed. Claude Code even cited CLAUDE.md as the reason it proceeded. What matters here doesn’t show up in “review once” thinking: local context is being treated like approval. The scenario is not hard to imagine: A dev pulls a repo → a contractor tweaks an instruction file → a tiny change slips through review → the agent inherits it. Whether the change is malicious or just careless, the result can be the same. Teams using Claude Code should treat CLAUDE.md like code: review it, scan it, and control who can change it. Thanks to HackRead Media for covering the research: https://lnkd.in/ditZNs8f

🚨 We found a critical vulnerability in Anthropic’s Claude Code. Just three lines in CLAUDE.md were enough to turn Claude Code from project help into a nation-state-level offensive hacking tool, with no coding at all. In our testing, that meant login bypass, SQLi, and dumping a username/password database from our test app. Claude even cited CLAUDE.md as its authorization. Once a coding assistant starts treating local project context as approval to act, repo files, insiders, contractors, and public repos all become part of the trust boundary. We now know that trust can be easily abused. 🔐 Security teams should treat CLAUDE.md like executable code, not documentation. Review it, scan it, and gate who gets to edit it. 🧠 Full research breakdown and demo → https://lnkd.in/dVpGy-AP

Intel Business and LayerX join forces. 🤜🤛 To bring AI security to the endpoint. The Idea behind it? If AI risk happens in real time, AI security has to happen locally too. ⚡ Prompts, uploads, outputs, and live session behavior all happen at the point of action. If the control point is still in the cloud, you are trying to solve a sensitive data problem by sending the data somewhere else first, while also adding latency, reliability gaps, and cost. Local analysis changes that. 🔒 Sensitive data stays on the device, and decisions can happen in real time. That is where Intel comes in. Intel WebGPU frameworks and Intel Core Ultra processors give LayerX the on-device performance needed for local SLM-based protections without disrupting the user experience. In LayerX testing, Intel Core Ultra X7 358H delivered up to 2x faster performance than AMD Ryzen AI 9 365 across three LayerX performance tests. 𝗧𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝘄𝗵𝗮𝘁 𝗔𝗜 𝘂𝘀𝗮𝗴𝗲 𝗰𝗼𝗻𝘁𝗿𝗼𝗹 𝗹𝗼𝗼𝗸𝘀 𝗹𝗶𝗸𝗲 𝗶𝗻 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲: true data classification for unstructured business data, understanding user intent across a full session, detection of prompt injection and jailbreaking, and monitoring LLM output before it reaches the user. 🤖 This is AI usage control at the point of action, on-device, in the browser, private, fast, and always on, with real-time decisions and no cloud round trips. Read more 👉 https://lnkd.in/dKtYY3En