O Google fechou temporariamente seu Programa de Recompensas por Vulnerabilidades em Software de Código Aberto (OSS VRP) para submissões de vulnerabilidades de produtos, alegando um aumento significativo de relatórios automatizados, a maioria deles inválidos. A pausa foi anunciada no X em 1º de outubro.
O Google fechou temporariamente seu Programa de Recompensas por Vulnerabilidades em Software de Código Aberto (OSS VRP) para submissões de vulnerabilidades de produtos, alegando um aumento significativo de relatórios automatizados, a maioria deles inválidos. A pausa foi anunciada no X em 1º de outubro.
Em contexto
- Tema: Ciberseguridad — Riesgo, identidad, respuesta a incidentes y cumplimiento.
- Fonte: CISO Advisor
- Publicado: 06/10/2026
Continuar lendo na fonte original →
Trecho publicado automaticamente pelo radar do site. O texto completo pertence ao veículo e está vinculado acima.
Why it matters
Every time I read a case like this I think the same thing: security is not bought, it is operated. You can own every tool on the market and remain exposed if nobody reviews the alerts, if patches get applied when there is time, or if the backup was never tested by actually restoring it.
My way of reading these cases is to ask what failed in the process, not what failed in the machine. Behind nearly every incident there is a reasonable decision taken under pressure: granting a permission to unblock somebody, postponing an update because it was month-end. That is where the lesson lives.
What usually goes wrong
What I see fail most is the backup. It is configured, it runs every night, nobody checks it. The day you need to restore, it turns out it had been failing silently for four months, or that everything was backed up except exactly what was needed. A backup never restored is an assumption.
What to watch
- How long it took to detect, usually the most revealing metric in the whole case.
- Whether initial access came from a legitimate account handled badly, which is the most frequent pattern.
- What could be restored and how fast — a backup that was never tested does not count.
How I read this entry
What I would review this very week is access: accounts belonging to people who left, permissions that grew without anyone trimming them, and shared credentials everybody swears do not exist. It is the least glamorous work and the one that cuts off the most attacks.
The original story is published in another language; the excerpt is quoted as the publisher delivers it and the commentary is written in English.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
