Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Organizations are not choosing between AI adoption and data security. Rather, they are discovering, often after the fact, that these two priorities are pulling in opposite directions. The engineering team has been using GitHub Copilot for six months. Finance is running variance analysis through ChatGPT. Legal is pasting contract language into Gemini for redlining. According to Cyberhaven Labs research, 39.7% of the data employees share with AI tools is sensitive.

Speakers made it clear that agentic AI is already operating across enterprise workflows. Learn why identity must govern ownership, permissions, actions, and accountability.

Adversaries are using AI to launch cyber attacks in record time, forcing security teams to measure responses in seconds instead of hours or days. Detecting these attacks is increasingly difficult. Phishing campaigns built by large language models (LLMs) achieve click-through rates 4.5x higher than traditional methods.1 Public sector organizations are at an inflection point with cybersecurity. Most security stacks in place today weren’t built for this level of speed.

There isn't a CIO on the planet not worried about AI spend right now. CFOs are increasingly nervous, too. For fear of falling behind, many companies have pushed their employees to use AI as aggressively as possible. The edict was clear: "Move fast, we'll figure out the bill later." And for the most part, it worked: AI has been genuinely transformational for the teams that leaned in. But the costs are real: we’ve heard countless horror stories of huge bills and painful overages on token spend.

The era of "typing into a box" is over. For years, we viewed artificial intelligence as a digital assistant—a sophisticated autocomplete tool that waited for human input. But according to Martin Kraemer, KnowBe4’s CISO Advisor for Europe and the Middle East, that dynamic has shifted. We have moved from asking AI questions to giving AI jobs. In a recent webinar, Martin explores the transition from AI tools to AI agents.

NVIDIA NIM (NVIDIA Inference Microservices) packages production-ready AI models into optimized containers for enterprise deployment. Your developers need them. Your coding agents pull them. And until now, they pulled them directly from NVIDIA’s NGC registry, bypassing the supply chain controls you’ve spent years building. JFrog AI Catalog now brings NVIDIA NIM models under the same governance as every other artifact in your organization, with no separate registry and no governance gap.

Bringing artificial intelligence into the office is a bit like adopting a hyper-energetic, brilliant, but chaotic intern. It can supercharge productivity, but if left unsupervised, it can accidentally delete the company database or invite a lawsuit. While the benefits of workplace AI are heavily advertised, deploying it without a safety net introduces significant vulnerabilities. Here’s a comprehensive breakdown of the risks businesses face when integrating AI into their daily operations.

Walking the floor at Infosecurity Europe this week, it was impossible to avoid the subject of AI. Every conversation seemed to touch on it in some way. Vendors were demonstrating AI-powered detection capabilities, security teams were discussing governance frameworks, and practitioners were debating how best to secure the models, agents and data pipelines that are rapidly becoming part of everyday enterprise operations.