
Developers aren’t in your organisation to be security experts. They shouldn’t be the ones deciding whether a change meaningfully affects security. Ben Oster, @ThreatModeler on @CloudSecPod.

Award Winning Top 10 Ranked CyberSecurity Podcast in US,UK and Aus. Learn Cloud Security in Public Cloud the unbiased way from CyberSecurity Host: @hashishrajan

Developers aren’t in your organisation to be security experts. They shouldn’t be the ones deciding whether a change meaningfully affects security. Ben Oster, @ThreatModeler on @CloudSecPod.

One tag on a resource made the auto-remediation skip it. Teams managed that bypass themselves and had to justify using it afterwards, so it didn’t get abused. Andoni Alonso Fernández (@crossmint) and Samuel Burgos López (@Flywire) on @CloudSecPod.

DLP with high false positive rates stopped people from doing their work. Users get blocked with no idea why, raise a ticket, hear the tool isn’t sanctioned, and reply that they’re being told to use AI. Brandon Dixon from @Ent_Security on @CloudSecPod.

Invite a collaborator to your project and they get the same access an employee would. More people building apps means more people to try things against. Samuel Kelemen from @Lovable on @CloudSecPod.

Once Route 53 records are orphaned, someone can capture your domain’s name servers. Tokens sent to callback URLs on its subdomains then go to them, and the whole hosted zone is compromised. Ramesh Ramani from Block on @CloudSecPod.

Two people with a GPU rig can point it at an environment, and no one is writing signatures or detections for this. What used to be sophisticated is now commoditised, so your skill set matters that much more. Damien Lewke, @nebulocksec on @CloudSecPod.

A production app in another account may still be using a subdomain under an orphaned hosted zone. When the person who created the records has left, they belong to no one. Ramesh Ramani from Block on @CloudSecPod

A threat model for a complex application has gone from a multi-week or multi-month project to hours, in roughly six to nine months. Ben Oster, @ThreatModeler on @CloudSecPod.

A pen test agent verified domain ownership against a private IP, then tested the public site once the DNS record was repointed. Richard Fan on @CloudSecPod about the guardrails he got past in AWS Security Agent. #CloudSecurity

Breaches happen because something gets missed. An Okta API token logs into a MacBook, which opens the AWS CLI. Step by step, none of it is necessarily bad. Read as one series of events, it’s direct evidence of an active intrusion. Damien Lewke, @nebulocksec on @CloudSecPod.

With Cursor running different models on the back end, a threat model can be out of date by the time you’ve plugged it in. Historical data shows about 80% never get revisited. Ben Oster, @ThreatModeler on @CloudSecPod.

Most of us are probably running AI coding agents in YOLO mode. More of that work is likely to move into VMs and sandboxes, partly because agents need different tools from developers. Samuel Kelemen from @Lovable on @CloudSecPod.

An attempt to measure least privilege by having AI scroll through logs and configuration didn’t give the right signals. With logs at that volume, LLMs couldn’t be trusted to produce deterministic ones. Ramesh Ramani from Block on @CloudSecPod.

About 80% of threat models never get revisited. Each took weeks or months to build, and updating one meant another three weeks in a room. Now a model can be stale by the time it’s plugged into Cursor. Ben Oster, @ThreatModeler on @CloudSecPod #ThreatModeling

GTG-1002 went from reconnaissance to exfiltration in under 60 minutes. No human could have done that. Clustering, sequencing and time boxing should give high fidelity detections. Nicole Beckwith, @cribl_io on @CloudSecPod.

Securing AI agents by design means rebuilding IAM from the ground up. One engineer might run 40 agents in parallel in an hour. Multiply that across engineering, IT and business users. Ido Shlomo from @TheTokenSec on @CloudSecPod. #IdentitySecurity #AgenticAI