Security
Securing AI systems and workflows: prompt injection, permissions, secrets, and safe tool use.
The collection25 saves · newest SEP 04
Player 1 · this device0 / 25 adopted
- LV.13 Security Checks Every AI-Built App Needs
- LV.23 Five-Minute Security Checks Before Shipping a Vibe-Coded App
- LV.3AI Forgets Authorization: And That's a Security Hole
- LV.4Never Give an Assistant Your Actual Mail Password
- LV.5Three Ways a Tutorial Can Leave You Exposed
- LV.6Ask Claude for a Security Audit Before Shipping, Then Fix It All
- LV.7Safer Alternative to Bypass Permissions: Allow + Deny Lists in Claude Code
- LV.8Five login-screen security practices to give your AI coding agent
- LV.9Why Enterprise Buyers Ask for SOC 2 and ISO 27001
- LV.10Memory Poisoning Explained: Why AI Agents' Saved Memories Need Review
- LV.11SQL Injection Explained for Vibe Coders (Day 5)
- LV.12Deny Rules Block a Coding Agent's Tool Calls
- LV.13Three Questions to Answer Before Launching a Product
- LV.14Set Guardrails Before Connecting Any Tool to Claude
- LV.15Scanning Every Repo for Exposed Keys and Vulnerabilities
- LV.16A Ten-Point Security Checklist for a Generated App
- LV.17Vet a Skill or Connector in an Isolated Chat Before Installing It
- LV.18EU AI Act Transparency: Label, Consent, and Log AI Output
- LV.19Five Ways an AI-Built Login Page Is Insecure
- LV.20When Attackers Go Around Cloudflare to Your Origin IP
- LV.21Three Cloudflare Rules Your App Is Probably Missing
- LV.22Cryptographic Erasure: Deleting User Data That Sits in Backups
- LV.23Lock Down AI Agent URL Fetching to Stop SSRF Attacks
- LV.24Stop Next.js Server Actions From Leaking Database Credentials
- LV.25Anthropic's Security Guidance Plugin for Claude Code