DevOps / SRE / Platform · 30.07.2026, 19:18 UTC
AI-generated software is forcing yet another another platform rethink
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 30.07.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
“Raise your hand if your team is actively using AI to write and review code. Now keep it up if you feel you have the security systems in place to account for that.”
This is how the panel discussion on security kicked off earlier this summer at PlatformCon London. The not-uncommon response to this question was that the hundreds assembled of platform engineers and engineering leaders raised their hands about using AI to write code. Then all but two of them kept their hands up when asked if they felt comfortable with the security systems they have in place to account for AI-written code.
This contrast begs the question: If we can’t go at the speed of AI securely, should we go that fast at all?
Liz Rice, chief open source officer at Isovalent and member of that panel discussion on security, told The New Stack last month, “The threat landscape has really changed a lot because finding vulnerabilities is almost wasted work now. What we’re doing in the AI world is non-deterministic, so having guardrails around what systems can do becomes ever more important because we can’t predict what models are going to do next.”
“What we’re doing in the AI world is non-deterministic, so having guardrails around what systems can do becomes ever more important because we can’t predict what models are going to do next.”
Expanding that risk factor is that many more people in a company than even a few years ago might be able to write code that creates a security risk. So. should everybody in your company be onboarded to your internal developer platform?
AI-BOM: The threat lurking in your …