honest take from someone who spends most of their time looking at how orgs actually get breached — the scariest thing isnt what a frontier model can do, but what orgs have already left wide open. i've been auditing CI/CD setups for years and the amount of GitHub Actions workflows running with IAM trust policies that basically say "any repo in my org can assume this production role" is wild. the EC breach started with a compromised trivy download leaking a static API key. no fancy model needed. i'm not saying capability concerns don't matter but there's a massive gap between "what if AI could hack us" and "we haven't even locked down the machine identities we set up 3 years ago and forgot about"
honest take from someone who spends most of their time looking at how orgs actually get breached — the scariest thing isnt what a frontier model can do, but what orgs have already left wide open. i've been auditing CI/CD setups for years and the amount of GitHub Actions workflows running with IAM trust policies that basically say "any repo in my org can assume this production role" is wild. the EC breach started with a compromised trivy download leaking a static API key. no fancy model needed. i'm not saying capability concerns don't matter but there's a massive gap between "what if AI could hack us" and "we haven't even locked down the machine identities we set up 3 years ago and forgot about"