Identifying phishing in your e-mail

DespiteFor theinformation BOLabout alertphishing, what to phishingdo, e-mails,and manyexamples usersof arepast still unable to identifyemail phishing e-mails…

attempts

http://www.bol.ucla.edu/alert/20080307.html

Identifying things— any one of these generally is sufficient to identify that it is fake, most phishing e-mails will correlate with most of these items:
-—-
- We do not refer to “UCLA.edu” e-mail, we refer to it as Bruin Online mail (e.g. https://mail.ucla.edu displays “Welcome to Bruin Online Webmail”) to distinguish between BOL mail and departmental e-mail (such as geog.ucla.edu provided by SSC).

- You do not have an “e-mail username”, you have ain UCLA Logonemail, ID.

- BOL would never ask for your password, “e-mail password” or otherwise.

- BOL would never ask for your country or territory.

- We have a known policy for maintaining accounts andconsult the threatIT belowServices has“Phishing noScams” relationweb at all to Bruin Online policy (UCLA Logon IDs are permanent)page: http://www.bol.ucla.edu/services/accounts/info/regular.html#regexplinktext

- There’s no such thing as a “UCLA.edu Webmail team”; Bruin Online handles all e-mail directly from the ucla.edu domain.

- There’s no such thing as a “UCLA.edu Data”.

- There is no such thing as “uclateam@ucla.edu” .

- If you checkreceive and phishing email, IT Services’ Security team asks that you share it with them. Email a saved copy of the original message headersto :security@ucla.edu so they can put an image of the original contents in moretheir detailphishing yourepository. This will seegenerate thata ticket and an InfoSec Analyst will get it does not come from a UCLA mail server and that actual reply-to address does not go backposted to athe UCLA address.website.