{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/0df99d8ca2ab47c7bcd9918a00e1762a\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/0df99d8ca2ab47c7bcd9918a00e1762a-69424ea1e92f7a7f.gif","duration":236.979,"title":"Automated Security Checks for Deployment Keys","description":"This Loom introduces a security incident monitoring checker to alert teams when deployed service keys are affected by breaches. The creator explains that teams set up each project with its hosting location and reference the keys they use, without storing key values. A Go agent then checks the web every day for security incidents involving those services and creates tasks in the system. In a recent example involving Railway, the agent found an incident and generated three tasks to rotate the Supabase publishable key, Supabase secret key, and OpenRouter key."}