Put several AI bots to work, and a mistake by one may not stay within its assigned task. For example, The post Grok Bot vs. Hermes: Where each draws the security boundary appeared first on The New Stack.
Put several AI bots to work, and a mistake by one may not stay within its assigned task. For example, The post Grok Bot vs. Hermes: Where each draws the security boundary appeared first on The New Stack.
In context
- Topic: Low-Code y No-Code — Plataformas de bajo código, su gobierno y su deuda técnica.
- Source: The New Stack
- Published: 24/08/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
In security the story is rarely the attack. It is the time between the intrusion and somebody noticing. That number says more about an organisation than any certificate hanging on the reception wall.
I separate technical risk from business risk, because they do not always match. A critical vulnerability in an isolated system matters less than a medium one in the system that issues invoices. Prioritising by severity without looking at where the money is is an expensive way to work hard and protect little.
What usually goes wrong
The most expensive blind spot is usually the supplier. The organisation hardens its own perimeter and grants broad access to a third party that has half those controls. A good share of the incidents I have seen in this region came in that way, and the contract said nothing about it.
What to watch
- What could be restored and how fast — a backup that was never tested does not count.
- How it was communicated to customers and regulators, which is where reputational cost is decided.
- Whether third parties or suppliers were in the chain, because the perimeter now includes partners.
How I read this entry
I would use it for a conversation with the board, not with the technical team. The question you must be able to answer there is how long the business can operate without its systems and what each day of that outage costs. With that number, the security budget gets discussed differently.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
