Security Blog

The latest news and insights from Google on security and safety on the Internet

Disclosure timeline for vulnerabilities under active attack

29 de maio de 2013
Share on Twitter Share on Facebook
Google

7 comentários :

ëRiC disse...

Incredible that this is still debated at all! If you have wide spread software and there is a critical security hole: You fix it! NAO!

7 days is nice as a start. But actually bits and bytes know speed a little different than us puny humans. 7 days is enough to infect the whole world!

30 de maio de 2013 às 06:02
chillzwerg disse...

Better and faster security. Superb!

30 de maio de 2013 às 11:14
voodooKobra disse...

I approve of this maneuver. If the vendor doesn't respond after a week, they cannot be trusted to secure their customers.

30 de maio de 2013 às 14:41
killbit disse...

This is a fantastic policy for companies that are cloud based such as good. However those companies that provide enterprise software a customer has to install and test. is NOT going to be able to fix, test, release to customer, customer pick up the fix, customer test, submit change requests and deploy in < 7 days. You guys are going to expose more customers to these sorts of issues. Why not work with the companies to release guidance if they can't fix the issue. Google has no idea about enterprise customers. No enterprise is going to pick up any software from you they have to deploy.

30 de maio de 2013 às 16:15
Unknown disse...

I like it. Way to keep us safe :-D

30 de maio de 2013 às 16:37
Anônimo disse...

Will you also be holding the rest of Google to the same standard?

31 de maio de 2013 às 09:36
Joe Philipps disse...

Compared to some researchers, this is charitable. A certain proportion of them think full disclosure should be the norm so that the affected parties can begin to mitigate the trouble.

31 de maio de 2013 às 15:27

Postar um comentário

  

Marcadores


  • #sharethemicincyber
  • #supplychain #security #opensource
  • android
  • android security
  • android tr
  • app security
  • big data
  • biometrics
  • blackhat
  • C++
  • chrome
  • chrome enterprise
  • chrome security
  • connected devices
  • CTF
  • diversity
  • encryption
  • federated learning
  • fuzzing
  • Gboard
  • google play
  • google play protect
  • hacking
  • interoperability
  • iot security
  • kubernetes
  • linux kernel
  • memory safety
  • Open Source
  • pha family highlights
  • pixel
  • privacy
  • private compute core
  • Rowhammer
  • rust
  • Security
  • security rewards program
  • sigstore
  • spyware
  • supply chain
  • targeted spyware
  • tensor
  • Titan M2
  • VDP
  • vulnerabilities
  • workshop


Archive


  •     2025
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2024
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2023
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2022
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2021
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2020
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2019
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2018
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2017
    • dez.
    • nov.
    • out.
    • set.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2016
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2015
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2014
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2013
    • dez.
    • nov.
    • out.
    • ago.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2012
    • dez.
    • set.
    • ago.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2011
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
  •     2010
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • mai.
    • abr.
    • mar.
  •     2009
    • nov.
    • out.
    • ago.
    • jul.
    • jun.
    • mar.
  •     2008
    • dez.
    • nov.
    • out.
    • ago.
    • jul.
    • mai.
    • fev.
  •     2007
    • nov.
    • out.
    • set.
    • jul.
    • jun.
    • mai.

Feed

Follow
Give us feedback in our Product Forums.
  • Google
  • Privacy
  • Terms