Re: Oxford and Google Apps

["Santabarbara, Angelo" <asantabarbara () SIENA EDU>]

That's just their policy. We have our user services people submit samples
and then others add verification. As your "reputation" rises, a smaller
number of confirmations are required.  However they explicitly state that
it always requires more than one.

Angelo D. Santabarbara
Director Networks & Systems
On Feb 19, 2013 12:40 PM, "Bob Bayn" <bob.bayn () usu edu> wrote:

>  Why should it take more than one "legitimate" report?  It seems pretty
> obvious to me that a password collection form is a password collection
> form.  And a quick peek at the database behind the form will probably show
> the unrelated variety of victims.  As they err on the side of caution, more
> victims accumulate.
>
>
> Bob Bayn    SER 301    (435)797-2396       IT Security Team
> Office of Information Technology,     Utah State University
>      three common hazardous email scams to watch out for:
>      *1) unfamiliar transaction report from familiar business
>      2) attachment with no explanation in message body
>      3) "phishing" for your email password*
>  ------------------------------
> *From:* The EDUCAUSE Security Constituent Group Listserv [
> SECURITY () LISTSERV EDUCAUSE EDU] on behalf of Santabarbara, Angelo [
> asantabarbara () SIENA EDU]
> *Sent:* Tuesday, February 19, 2013 10:27 AM
> *To:* SECURITY () LISTSERV EDUCAUSE EDU
> *Subject:* Re: [SECURITY] Oxford and Google Apps
>
> We've been using OpenDNS to block known phishing hosts. We then
> immediately report the site to phishtank.org as well as Google and
> usually it gets blocked within a couple of hours if enough legitimate
> reports are received.
>
> Angelo D. Santabarbara
> Director Networks & Systems
> Siena College