Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

How to Build an AI Governance Policy for Employees

Most organizations now have an AI policy on paper. Far fewer can tell whether employees follow it. According to ISACA, 25% of organizations have no AI policy at all, and only 38% of those with one describe it as formal and thorough. Meanwhile, employees keep pasting, uploading, and delegating work to AI tools, both generative and agentic. Cyberhaven Labs found that 39.7% of employee interactions with AI tools involve sensitive data.

Identity Security in the Age of AI

As AI becomes more sophisticated and adoption increases, so does the number of non-human identities operating across enterprise environments. And yet, only 43% of organizations have AI-related NHI management and security in place. Keeper Security provides a unified platform, bringing together privileged access management, endpoint privilege management, secrets management and AI governance to protect against emerging AI threats.

AI Attackers Move Fast. Reach Moves First.

AI-fueled attacks can now find and exploit misconfigured security controls in minutes. Human-driven defenses can no longer keep pace with the speed, scale, and volume of those attacks. Reach helps you autonomously close defensive gaps before AI-powered attackers strike, across email, network, endpoint, SaaS applications, and identity access management. Setup takes 3 minutes with a read-only API key, and results arrive in under 5 days.

5 Reasons Your DAST and SAST Scans Miss BOLA & BFLA

Every API security evaluation reaches the same objection: “We already run SAST and DAST.” The objection is fair. Static Application Security Testing (SAST) reads source code before release. Dynamic Application Security Testing (DAST) probes a running application from the outside. Both belong in continuous integration and continuous delivery (CI/CD) pipelines. Both also struggle with the two Application Programming Interface (API) flaws that matter most.

Data residency for LLMs: what GDPR requires and your three options

Short answer: GDPR does not require personal data to stay in the EU. It lets data leave only with a valid transfer mechanism. Data residency for LLMs comes down to three options: use the EU region of a hosted API, tokenize before the API call, or run the model yourself. Only the third keeps data out of the US in the literal sense. A procurement lead at a European customer sends your team a one-line requirement: “keine Daten in die USA.” No personal data in the United States.

bREACHYing the Perimeter: How One HTTP Request can Hijack your AI Robot

Software supply chain attacks are on the rise, and naturally taking the headlines. But with the rise of localized models and common software embedded into smart “things”, risks may even be hidden in plain sight – or, in some cases, quite literally watching you. Vulnerabilities and malicious packages may extend risks to the unlikeliest of places, demanding change and accountability in even some well-intended innovations.

17 Endpoints, Zero Logins Required: Broken Access Control in AI-Built Apps

We handed four vibe-coding tools (Emergent, Replit, Lovable, Base44) the same prompt for a FastAPI user-management microservice. The spec was explicit: JWT auth, parameterized queries, rate limiting, four-tier role model with per-endpoint scope. Each tool shipped a build, and our flagship autonomous pentest surfaced 137 confirmed vulnerabilities across all four.

Vibe Coding Security Checklist: Stress-Test Your AI-Built App in 10 Minutes

You shipped an app in a weekend. The AI wrote the login, the dashboard, and the database layer, and everything works, but it’s far from safe. With 0 logins, an attacker can forge admin invitations, alter audit logs, and change other users’ passwords. The guy is just swimming freestyle through your entire app stack. This is just one of the 137 vulnerabilities we found in vibe-coding across the top 4 platforms.