41
Phish, Flop, or Fine? Sandy Silk Catherine Conway

Phish, flop, or fine

Embed Size (px)

Citation preview

Page 1: Phish, flop, or fine

Phish, Flop, or Fine?Sandy Silk

Catherine Conway

Page 2: Phish, flop, or fine

We’re here to help.

Page 3: Phish, flop, or fine

Let us count the ways...

1. Increase the security of institutional and individual information. (Phish)

2. Improve the effectiveness of your broadcast email communications. (Flop)

3. Preserve email channel as a means for important messaging. (Fine)

Page 4: Phish, flop, or fine

From there to here, from here to there, phishy things are everywhere

Page 5: Phish, flop, or fine

One Phish

@iari.res.in

Page 6: Phish, flop, or fine

Two Phish

https://urldefense.proofpoint.com/v2/url?u=http-3A__kotovdent.ru_images_sampledata_collage_...

kotovdent.ru

my.bristol.ac.uk

Page 7: Phish, flop, or fine

Hunting expedition versus“catch of the day”

I am a rich prince in need of help...Hello Harvard...

Page 8: Phish, flop, or fine

Phish or Flop?

How many domains do you see in this message?

benstrat.lh1od.com

benstrat.navigatorsuite.com

benstrat.com

Page 9: Phish, flop, or fine

Phish or Fine?

Can’t I trust this if it comes from a Harvard address?

Page 10: Phish, flop, or fine

Message success depends on credibility

There are human ways and technological ways to make a good impression…and it’s a continuum.

Page 11: Phish, flop, or fine

Phishing filters at Harvard

Page 12: Phish, flop, or fine

Technical filters

Running the gauntletSuspect

Adult

SpamBulk

Phishing

Page 13: Phish, flop, or fine

66 millionEmail messages addressed to @harvard.edu that were blocked as spam/phishing in March 2016

Page 14: Phish, flop, or fine

Running the gauntlet (O365)Email from outside

Harvard

Spam, malware, and phishing filters

Bulk, malware, and phishing filters

Sender acceptance or blocking filters

Personal junk and blocking filters

(Email from inside Harvard)

Email sent outside Harvardor outside internal Exchange

(g.harvard, mail.harvard, @college, HBS)

What’s the “Holy Grail” of messaging?

Page 15: Phish, flop, or fine

There’s no recipe for spam.

Page 16: Phish, flop, or fine

Possible flagsUnfamiliar senderLack of text versionAttachmentRed textMany imagesLinking to multiple domainsAll capsKeywordsTyposSending to bad addressesLack of mailing addressNo unsubscribe link

Page 17: Phish, flop, or fine

Call ahead and order off the menu.

Page 18: Phish, flop, or fine

Call ahead: safelist your sender

Submit request to [email protected]

Email is still subject to local spam filters

Page 19: Phish, flop, or fine

Stick with the menu: Harvard URLs

Page 20: Phish, flop, or fine

Options for linking to Harvard websites

Post content on a Harvard website.

Use a Harvard link shortener for non-Harvard URLs.

Establish Harvard-branded domain for tracking (CNAME).

Page 21: Phish, flop, or fine

Floss after every meal.

Page 22: Phish, flop, or fine

Keep lists clean

Spam algorithms factor in engagement

No reason to keep unengaged subscribers on your list

Practice appropriate list hygiene

Re-engage inactive subscribers

If no response, consider opting out inactives

Page 23: Phish, flop, or fine

How to build credibility with technical filters

TacticsEmail marketing

service ListservOutlook with uploaded

list

Manage your spam flags X X X

Target your lists X X X

Link to Harvard URLs X X X

Use Harvard link shortener, when harvard url not available

X X

Safelist sender X

List hygiene X

Page 24: Phish, flop, or fine

Human filters

Phishing awareness campaign

Click Wisely

Page 25: Phish, flop, or fine

Phishing awareness and training

Page 26: Phish, flop, or fine

Mock phishing with feedback

Page 27: Phish, flop, or fine

Greater awareness drives more scrutiny of email

Page 28: Phish, flop, or fine
Page 29: Phish, flop, or fine

Be predictableManage your envelope:

Credible, consistent senderRelevant subject lineComplementary preheader textHave a reply address

Send at a regular, anticipated frequencyUse a well-tested and branded templateInclude all information within the email or on a Harvard website rather than sending an attachment

Provide option to manage preferences

Page 30: Phish, flop, or fine

Case study:EVP newsletter

Page 31: Phish, flop, or fine
Page 32: Phish, flop, or fine

Goals

Easily read across devices

Reflects best email practices

Incorporates tracking to measure engagement

Efficiently assembled each month

Continues to engage readers while serving as a messaging vehicle for Katie Lapp.

Page 33: Phish, flop, or fine

ExecutionContent

Project brief & wireframeTemplate developmentTestingIncorporated best practices:

Added a text versionAlt-text for imagesPreheader textMailing addressRemoved red textPosted full articles on Harvard

websites

DeliveryMoved to SilverpopCreated list querySafelisted [email protected] on

staff and school email servers via HUIT

Page 34: Phish, flop, or fine
Page 35: Phish, flop, or fine

links.mkt3495.com

Future plans

Page 36: Phish, flop, or fine

Tools for being a phish-aware, effective emailer

Page 37: Phish, flop, or fine

Harvard.edu/guidelines

Page 38: Phish, flop, or fine

Link shortener (coming soon)

Accessed by HarvardKey account with 2-step verification

Links checked against database of known malware sites

“hrvd.it” will be safelisted through our email systems

Page 39: Phish, flop, or fine

Are you phish, flop, or fine?

Page 40: Phish, flop, or fine

Remember the continuum

Page 41: Phish, flop, or fine

Questions?