Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

As artificial intelligence becomes deeply woven into daily workflows, employees are adopting unapproved AI apps at an unprecedented pace. According to Teramind’s Shadow AI Behavior Report, a staggering 89% of workplace AI usage occurs outside enterprise-governed channels, leaving 86% of organizations blind as to how corporate data flows in and out of these tools.

The same quantification run supports two conversations that happen weeks apart. One with a board asking whether the organization is managing cyber risk sensibly. One with an underwriter deciding what to charge for it. ‍ Most guidance treats these as a formatting problem, where the board version gets charts and the submission gets detail.

Colorado passed the first comprehensive state AI law in May 2024, and organizations spent the following year building impact assessment processes against it. Those obligations never took effect. The statute was delayed twice, blocked by a federal court, then repealed and replaced by a narrower framework before its own effective date arrived. ‍ Anyone who built a compliance program to that specific statute prepared for a regime that never existed.

Here is a deal that almost died for the wrong reason. The customer said, “We need Hyper-V.” The partner logged it as a technical requirement, qualified the opportunity out of any VMware conversation, and moved on. Reasonable enough. That is what a stated requirement is supposed to mean. Except it was not technical. When someone finally asked why Hyper-V, the answer had nothing to do with the hypervisor.

CTEM scoping isn’t about putting everything you can scan into scope. It’s about defining what matters most to the business and keeping that definition current as your environment changes. Get scoping right, and every stage that follows—from discovery to prioritization and mobilization—becomes more focused, relevant, and effective. Continuous Threat Exposure Management breaks down into five stages: scoping, discovery, prioritization, validation, and mobilization.

Compare Google Authenticator and YubiKey to understand how each authentication method works, their security strengths, phishing resistance, deployment considerations, and which option is best for your organization. Passwords alone are no longer enough. Multi-factor authentication (MFA) is now the baseline but not all MFA methods are equally secure. Two of the most commonly compared options are Google Authenticator, a free smartphone app, and YubiKey, a physical hardware security key.

83% of organizations reported moderate or major delays from manual compliance work in 2026, while 53% said one full-time employee's worth of effort is spent on evidence collection, according to the 2026 State of Continuous Compliance Monitoring report. Those figures describe the operational problem more accurately than another promise of an audit-ready dashboard.

In July 2026, researchers at Noma Labs coaxed GitHub's new Agentic Workflows into leaking data from a private repository. It wasn’t from malware. They created a plausible-looking issue in a public repository containing instructions for the agent to retrieve information from other repositories in the organization. After testing variations of the prompt, they found that adding one word, "Additionally," was enough to get past GitHub's guardrails.

Business schools teach leaders how to evaluate markets, allocate resources, manage teams, and make strategic decisions. Cybersecurity tests those skills in real time.

Zero-Shot Learning is a podcast about how AI is built, secured, and deployed. Hosted by Nancy Wang, 1Password CTO, and Dev Tagare, Senior Director of Engineering at Google Gemini, it offers a builder’s view of the architecture and complex decisions involved in shipping AI.