Security Blog

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

Disclosure timeline for vulnerabilities under active attack

2013 m. gegužės 29 d.
Share on Twitter Share on Facebook
Google

7 komentarai :

ëRiC rašė...

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!

2013 m. gegužės 30 d. 06:02
chillzwerg rašė...

Better and faster security. Superb!

2013 m. gegužės 30 d. 11:14
voodooKobra rašė...

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

2013 m. gegužės 30 d. 14:41
killbit rašė...

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.

2013 m. gegužės 30 d. 16:15
Unknown rašė...

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

2013 m. gegužės 30 d. 16:37
Anonimiškas rašė...

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

2013 m. gegužės 31 d. 09:36
Joe Philipps rašė...

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.

2013 m. gegužės 31 d. 15:27

Rašyti komentarą

  

Etiketės


  • #sharethemicincyber
  • #supplychain #security #opensource
  • AI Security
  • 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


  •     2026
    • bal.
    • kov.
    • vas.
    • saus.
  •     2025
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2024
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2023
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2022
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2021
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2020
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2019
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2018
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2017
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2016
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2015
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2014
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2013
    • gruod.
    • lapkr.
    • spal.
    • rugp.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2012
    • gruod.
    • rugs.
    • rugp.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
    • saus.
  •     2011
    • gruod.
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • birž.
    • geg.
    • bal.
    • kov.
    • vas.
  •     2010
    • lapkr.
    • spal.
    • rugs.
    • rugp.
    • liep.
    • geg.
    • bal.
    • kov.
  •     2009
    • lapkr.
    • spal.
    • rugp.
    • liep.
    • birž.
    • kov.
  •     2008
    • gruod.
    • lapkr.
    • spal.
    • rugp.
    • liep.
    • geg.
    • vas.
  •     2007
    • lapkr.
    • spal.
    • rugs.
    • liep.
    • birž.
    • geg.

Feed

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