[nsp-sec] google contact, urgent

[Daniel Schwalbe]

I have been in the same boat before myself. I'm happy to see that Google 
has improved the 'removal request' process somewhat - it used to be an 
FAQ on how to remove the content and then get Google to re-cache the page.

That assumed you had editorial control over the the site/server where the 
original problem content was located. In both cases where we had 
'accidental' disclosure of protected information (one .xls, one .mdb) that 
ended up in Google cache, the information was cached from a site located 
3rd party servers.

I also got a much better response from the nsp-sec community - Cory was 
still at Google back then, and he took care of it. Yay Team! :-)

_______________________________________________________
Daniel Schwalbe, CISSP             dfs at u.washington.edu
Lead Security Engineer                 +1(206) 221-7000
University of Washington         UW Technology Services
PGP: E2DD CE57 62F4 0F22 CA09  37AB CA69 A2A3 1A45 0BF7


On Thu, 1 May 2008, Ariel Biener wrote:

> ----------- nsp-security Confidential --------
>
> On Thursday 01 May 2008 11:26, Hank Nussbacher wrote:
>>
>> In the meantime try:
>> https://www.google.com/webmasters/tools/removals
>>
>> -Hank
>>
>
> I done that before e-mailing nsp-security. I believe there is a saying
> that goes more or less like this:
>
> "God helps those who help themselves" :)
>
> --Ariel
> --
> Ariel Biener
> Technical Officer      tel: +972-3-6114094
> ISOC-IL                e-mail: ariel at isoc.org.il
> PGP: http://www.tau.ac.il/~ariel/pgp.html
>
>
> _______________________________________________
> nsp-security mailing list
> nsp-security at puck.nether.net
> https://puck.nether.net/mailman/listinfo/nsp-security
>
> Please do not Forward, CC, or BCC this E-mail outside of the nsp-security
> community. Confidentiality is essential for effective Internet security counter-measures.
> _______________________________________________
>