Introduction |
|
1 | (1) |
|
|
2 | (1) |
|
Why We Combined Spam and Spyware |
|
|
2 | (1) |
|
How This Book Is Organized |
|
|
3 | (2) |
|
Part I: Understanding the Problem |
|
|
3 | (1) |
|
Part II: Justifying and Selecting Spam and Spyware Filters |
|
|
3 | (1) |
|
Part III: Deploying Your Chosen Solution |
|
|
4 | (1) |
|
Part IV: Maintaining Your Defenses |
|
|
4 | (1) |
|
|
4 | (1) |
|
Conventions Used in This Book |
|
|
5 | (1) |
|
Defining Spam, Spyware, and Malware |
|
|
5 | (1) |
|
|
6 | (1) |
|
|
6 | (1) |
|
|
7 | (1) |
|
And the Latest Breaking News |
|
|
8 | (1) |
|
|
8 | (1) |
|
Part I: Understanding the Problem |
|
|
9 | (60) |
|
Spam and Spyware: The Rampant Menace |
|
|
11 | (26) |
|
Knowing How Spam and Spyware Affect the Organization |
|
|
11 | (5) |
|
|
12 | (1) |
|
|
12 | (2) |
|
Exposing the business to malicious code |
|
|
14 | (1) |
|
Creating legal liabilities |
|
|
14 | (2) |
|
No Silver Bullets: Looking for Ways to Fight Back |
|
|
16 | (6) |
|
|
16 | (4) |
|
Keeping spyware away from workstations |
|
|
20 | (1) |
|
Other good defense-in-depth practices |
|
|
21 | (1) |
|
Understanding the role of legislation |
|
|
21 | (1) |
|
Taking Stock of Your Business |
|
|
22 | (5) |
|
|
22 | (1) |
|
|
23 | (1) |
|
Understanding your architecture |
|
|
24 | (1) |
|
Taking users' skills and attitudes into account |
|
|
25 | (1) |
|
Evaluating available skills in IT |
|
|
26 | (1) |
|
Working within your budget |
|
|
26 | (1) |
|
Justifying Spam and Spyware Control |
|
|
27 | (1) |
|
Choosing Anti-Spam and Anti-Spyware Solutions |
|
|
28 | (4) |
|
Types of anti-spam solutions |
|
|
29 | (1) |
|
What are the key features? |
|
|
30 | (1) |
|
|
30 | (2) |
|
Sizing for now and the future |
|
|
32 | (1) |
|
|
32 | (5) |
|
|
33 | (1) |
|
|
33 | (2) |
|
|
35 | (1) |
|
Taking your solution live |
|
|
36 | (1) |
|
|
36 | (1) |
|
The Spyware Who Loved Me: Stopping Spyware in Its Tracks |
|
|
37 | (16) |
|
|
37 | (3) |
|
|
38 | (1) |
|
An information transgressor |
|
|
38 | (2) |
|
|
40 | (2) |
|
Finding holes in the Web browser |
|
|
40 | (1) |
|
|
41 | (1) |
|
Hiding in software downloads |
|
|
41 | (1) |
|
Peer-to-peer file sharing |
|
|
42 | (1) |
|
How Spyware Gets Information from Your Computer |
|
|
42 | (3) |
|
|
43 | (1) |
|
|
43 | (1) |
|
|
44 | (1) |
|
|
44 | (1) |
|
Spoofing well-known Web pages |
|
|
44 | (1) |
|
|
45 | (1) |
|
|
45 | (4) |
|
Testing for vulnerabilities |
|
|
45 | (1) |
|
|
46 | (1) |
|
Scanning and removing spyware |
|
|
47 | (1) |
|
Preventing spyware from getting a foothold |
|
|
48 | (1) |
|
Choosing and Using Spyware Blockers |
|
|
49 | (4) |
|
Understanding the changing market |
|
|
49 | (1) |
|
Training users and getting their help |
|
|
50 | (1) |
|
Finding a product that deploys easily |
|
|
51 | (1) |
|
|
52 | (1) |
|
Understanding the Enemy: What Really Spawns Spam |
|
|
53 | (16) |
|
Understanding How Spammers Get E-Mail Addresses |
|
|
53 | (5) |
|
Harvesting from the Internet |
|
|
54 | (1) |
|
Buying and stealing addresses |
|
|
55 | (1) |
|
Directory service attacks |
|
|
56 | (2) |
|
Giving Filters the Slip: How Spam Messages Seep into Your Inbox |
|
|
58 | (6) |
|
Poisoning Bayesian filters |
|
|
59 | (1) |
|
|
60 | (1) |
|
|
61 | (1) |
|
Forging From: and Received: headers |
|
|
61 | (1) |
|
Relaying to hide message origins |
|
|
62 | (2) |
|
|
64 | (2) |
|
Making money with spam e-mail |
|
|
65 | (1) |
|
A black market of bots for relaying spam |
|
|
65 | (1) |
|
Spam's New Attitude: The Convergence of Spam and Viruses |
|
|
66 | (1) |
|
Advancing the War to New Fronts: Instant Messages and Text Messages |
|
|
67 | (2) |
|
Part II: Justifying and Selecting Spam and Spyware Filters |
|
|
69 | (64) |
|
Calculating ROI for Your Anti-Spam and Anti-Spyware Measures |
|
|
71 | (18) |
|
Understanding Activity-Based Costing |
|
|
73 | (2) |
|
|
73 | (1) |
|
|
74 | (1) |
|
|
75 | (1) |
|
Understanding Fixed and Variable Costs |
|
|
75 | (1) |
|
|
76 | (3) |
|
Using industry statistics |
|
|
76 | (1) |
|
|
77 | (1) |
|
Estimating your e-mail costs |
|
|
77 | (2) |
|
Employee-Productivity Model |
|
|
79 | (2) |
|
|
79 | (1) |
|
Turning hours into dollars |
|
|
80 | (1) |
|
Additional support calls because of spam and spyware-induced problems |
|
|
81 | (1) |
|
|
81 | (3) |
|
Risks from chronic exposure to obscene, violent, and hate material |
|
|
82 | (1) |
|
Risks from Web-site-borne malicious code |
|
|
82 | (1) |
|
Risks from phishing scams |
|
|
83 | (1) |
|
Qualitative Justifications |
|
|
84 | (1) |
|
|
84 | (1) |
|
|
85 | (1) |
|
Learning through networking |
|
|
85 | (1) |
|
Models for Justifying Spyware Filters |
|
|
85 | (4) |
|
|
86 | (1) |
|
Potential loss of corporate information |
|
|
86 | (1) |
|
Potential loss of custodial data |
|
|
87 | (1) |
|
Potential loss of employees' private information |
|
|
87 | (2) |
|
Developing the Battle Plans |
|
|
89 | (18) |
|
|
89 | (4) |
|
Knowing thy present architecture |
|
|
90 | (2) |
|
|
92 | (1) |
|
Knowing Your Business Objectives |
|
|
93 | (1) |
|
|
94 | (7) |
|
|
94 | (2) |
|
Collecting and organizing requirements |
|
|
96 | (1) |
|
|
96 | (1) |
|
|
97 | (1) |
|
|
98 | (3) |
|
Developing or Updating Policy |
|
|
101 | (1) |
|
Re-Engineering Business Processes |
|
|
102 | (3) |
|
|
102 | (1) |
|
Managing user workstations |
|
|
102 | (1) |
|
|
103 | (1) |
|
End-user training and orientation |
|
|
103 | (1) |
|
|
104 | (1) |
|
|
104 | (1) |
|
|
104 | (1) |
|
Defining Roles and Responsibilities |
|
|
105 | (2) |
|
Evaluating Anti-Spam and Anti-Spyware Solutions |
|
|
107 | (26) |
|
Ensuring the Anti-Spam Cure Is Better Than the Original Spam |
|
|
107 | (2) |
|
Choosing a Spam-Filtering Platform: Software, Appliance, or ASP? |
|
|
109 | (10) |
|
|
110 | (2) |
|
|
112 | (1) |
|
Application Service Provider solution |
|
|
113 | (3) |
|
|
116 | (1) |
|
The solutions side-by-side |
|
|
117 | (2) |
|
Choosing Spyware Filtering: Workstation or Centralized? |
|
|
119 | (4) |
|
|
120 | (1) |
|
Centralizing the anti-spyware solution |
|
|
120 | (2) |
|
|
122 | (1) |
|
Evaluating Information from Vendors |
|
|
123 | (6) |
|
Don't believe everything you hear |
|
|
124 | (1) |
|
Calling customer references |
|
|
125 | (1) |
|
Visiting a vendor's customer on-site |
|
|
126 | (1) |
|
|
127 | (1) |
|
Other ways to obtain vendor information |
|
|
128 | (1) |
|
Evaluating Anti-Spam and Anti-Spyware Vendors |
|
|
129 | (4) |
|
Understanding vendors' long-term product strategies |
|
|
129 | (2) |
|
Twisting vendors' arms to get the deal |
|
|
131 | (2) |
|
Part III: Deploying Your Chosen Solution |
|
|
133 | (74) |
|
Training Users and Support Staff |
|
|
135 | (14) |
|
The Many Methods of Training |
|
|
135 | (6) |
|
Offering effective seminars |
|
|
136 | (2) |
|
Creating paper user guides |
|
|
138 | (2) |
|
Posting user guides online |
|
|
140 | (1) |
|
|
141 | (3) |
|
Looking at the technology from a user's point of view |
|
|
142 | (1) |
|
Explaining the filter to users |
|
|
142 | (2) |
|
|
144 | (2) |
|
Put yourself in administrators' shoes |
|
|
145 | (1) |
|
Including practice in the training |
|
|
145 | (1) |
|
Give slightly more than needed |
|
|
146 | (1) |
|
Training the Helpdesk Staff |
|
|
146 | (3) |
|
Anticipating user questions and issues |
|
|
147 | (1) |
|
Building a knowledge base |
|
|
148 | (1) |
|
|
149 | (28) |
|
|
150 | (4) |
|
Involving the right people |
|
|
150 | (1) |
|
|
151 | (2) |
|
Keeping your objectives in mind |
|
|
153 | (1) |
|
|
153 | (1) |
|
|
154 | (8) |
|
|
155 | (3) |
|
Estimating time for key tasks |
|
|
158 | (1) |
|
|
159 | (1) |
|
Rounding up the hardware and software |
|
|
160 | (1) |
|
Working with outside resources |
|
|
160 | (2) |
|
|
162 | (1) |
|
Putting Together a Spam Filter Trial |
|
|
163 | (10) |
|
Developing measurable success criteria |
|
|
164 | (1) |
|
|
165 | (5) |
|
Selecting users for a trial |
|
|
170 | (1) |
|
|
171 | (1) |
|
Incorporating lessons learned into your deployment plan |
|
|
172 | (1) |
|
Planning a Spyware Filter Trial |
|
|
173 | (4) |
|
Needed: Measurable tests and results |
|
|
174 | (1) |
|
Identifying false positives |
|
|
174 | (1) |
|
|
174 | (1) |
|
Nondisruptive browser use |
|
|
175 | (2) |
|
Rolling Out to the Enterprise |
|
|
177 | (16) |
|
Implementing Spam Filtering |
|
|
177 | (10) |
|
Installing a software solution |
|
|
178 | (2) |
|
Plugging in a hardware solution |
|
|
180 | (1) |
|
Cutting over an ASP solution |
|
|
181 | (1) |
|
Taking care of the administrative details |
|
|
181 | (5) |
|
|
186 | (1) |
|
Implementing Spyware Filtering |
|
|
187 | (2) |
|
Starting with a trial installation |
|
|
187 | (1) |
|
Installing throughout your business |
|
|
188 | (1) |
|
Creating backout plans in case something goes awry |
|
|
189 | (1) |
|
Keeping Everything under Control |
|
|
189 | (4) |
|
Early warning signs of trouble |
|
|
190 | (1) |
|
Changing the plan in mid-sentence |
|
|
191 | (1) |
|
|
192 | (1) |
|
|
193 | (14) |
|
Understanding Common Support Scenarios |
|
|
194 | (3) |
|
Gathering information for support scenarios |
|
|
194 | (3) |
|
Documenting support scenarios |
|
|
197 | (1) |
|
Equipping Support Staff with Tools and Knowledge |
|
|
197 | (6) |
|
Seeing what the user sees |
|
|
198 | (3) |
|
|
201 | (2) |
|
Measuring the Support Effort |
|
|
203 | (4) |
|
Tracking numbers of calls |
|
|
203 | (1) |
|
|
204 | (1) |
|
Tracking the effort required to solve problems |
|
|
205 | (2) |
|
Part IV: Maintaining Your Defenses |
|
|
207 | (60) |
|
|
209 | (10) |
|
|
210 | (4) |
|
|
210 | (1) |
|
Administrative maintenance |
|
|
211 | (1) |
|
Automating quarantine management |
|
|
212 | (2) |
|
|
214 | (1) |
|
Maintaining user whitelists |
|
|
214 | (1) |
|
Maintaining systemwide whitelists |
|
|
215 | (1) |
|
|
215 | (2) |
|
Avoid specific rules that solve specific problems |
|
|
216 | (1) |
|
Monitor how effective specific rules are |
|
|
217 | (1) |
|
|
217 | (2) |
|
|
217 | (1) |
|
Updating the software (or engine) |
|
|
218 | (1) |
|
|
219 | (32) |
|
Coping with Performance Issues |
|
|
220 | (2) |
|
Dealing with interruptions in mail service |
|
|
220 | (1) |
|
|
221 | (1) |
|
Dealing with loss of productivity from spyware infestation |
|
|
221 | (1) |
|
Setting Realistic User Expectations |
|
|
222 | (9) |
|
False negatives: ``Your inbox won't be spam free'' |
|
|
223 | (3) |
|
False positives: When good mail looks bad |
|
|
226 | (4) |
|
Restricting Web browser configuration |
|
|
230 | (1) |
|
Identifying and Handling Business Issues |
|
|
231 | (8) |
|
Figuring out legal issues |
|
|
231 | (2) |
|
|
233 | (1) |
|
Preparing for ASP outages |
|
|
234 | (1) |
|
Developing skills to support the spam filter |
|
|
235 | (3) |
|
What about when spam actually works? |
|
|
238 | (1) |
|
Supporting spyware filters and scanning |
|
|
239 | (1) |
|
Stopping Deliberate Attacks |
|
|
239 | (12) |
|
Block Web bugs and other malicious content |
|
|
240 | (3) |
|
Don't make yourself a target for Joe Jobs |
|
|
243 | (1) |
|
Prevent spammers from verifying or listing e-mail addresses |
|
|
243 | (1) |
|
Make the Web spiders starve |
|
|
244 | (1) |
|
Viruses --- don't be part of the problem |
|
|
245 | (1) |
|
|
245 | (2) |
|
Educate users about spammy NDRs |
|
|
247 | (1) |
|
Protect users from phishing scams |
|
|
248 | (1) |
|
Be aware of single-target spyware |
|
|
249 | (2) |
|
Defense in Depth: Providing Layers of Protection |
|
|
251 | (16) |
|
Understanding Defense in Depth |
|
|
251 | (1) |
|
Deploying Security Patches |
|
|
252 | (3) |
|
Patches eliminate vulnerabilities |
|
|
253 | (1) |
|
Keeping pace with viruses and worms |
|
|
253 | (1) |
|
Patching made easier with dedicated tools |
|
|
254 | (1) |
|
|
255 | (4) |
|
|
256 | (2) |
|
|
258 | (1) |
|
Filtering incoming e-mail attachment extensions |
|
|
258 | (1) |
|
Turning off VRFY on your e-mail server |
|
|
259 | (1) |
|
|
259 | (3) |
|
|
259 | (1) |
|
Filtering inbound as well as outbound |
|
|
260 | (2) |
|
Keeping One Eye on the Future |
|
|
262 | (5) |
|
Watching the spam-filtering market as it matures |
|
|
262 | (2) |
|
|
264 | (2) |
|
Watching the maturing anti-spyware market |
|
|
266 | (1) |
|
|
267 | (54) |
|
Ten Spam-Filtering Solutions for the Enterprise |
|
|
269 | (10) |
|
|
270 | (1) |
|
Postini Perimeter Manager |
|
|
271 | (1) |
|
|
272 | (1) |
|
FrontBridge TrueProtect Message Management Suite |
|
|
273 | (1) |
|
Trend Micro Spam Prevention Solution |
|
|
274 | (1) |
|
|
274 | (1) |
|
|
275 | (1) |
|
|
276 | (1) |
|
Proofpoint Messaging Security Gateway |
|
|
277 | (1) |
|
MailFrontier Gateway Server |
|
|
278 | (1) |
|
Ten Keys to Successful Spam Filtering |
|
|
279 | (8) |
|
|
279 | (1) |
|
|
280 | (1) |
|
Matching the Product to the Users |
|
|
281 | (1) |
|
Training Users and Admins |
|
|
282 | (1) |
|
Preparing to Troubleshoot |
|
|
282 | (1) |
|
|
283 | (1) |
|
|
284 | (1) |
|
Creating a Global Whitelist |
|
|
284 | (1) |
|
|
285 | (1) |
|
Monitoring after You Deploy |
|
|
285 | (1) |
|
Epilogue: Reviewing Your Original Business Objectives |
|
|
286 | (1) |
|
Ten Spam-Related Issues Most Enterprises Face |
|
|
287 | (8) |
|
Users Don't Check Their Quarantines |
|
|
287 | (1) |
|
Users Don't Manage Their Whitelists |
|
|
288 | (1) |
|
|
288 | (1) |
|
Important Messages Lost or Delayed |
|
|
289 | (1) |
|
The Filter Vendor Exited the Market |
|
|
290 | (1) |
|
If your solution is an ASP |
|
|
290 | (1) |
|
If your solution is in-house |
|
|
290 | (1) |
|
Your Filter Is No Longer Effective |
|
|
291 | (1) |
|
Spam That Makes It through the Filter Is Still a Liability |
|
|
291 | (1) |
|
Mail Delivery Becomes More Complex |
|
|
292 | (1) |
|
Your Internet Connection Seems Slow |
|
|
293 | (1) |
|
My Company's Products Smell Like Spam (Or, I Work for Hormel) |
|
|
294 | (1) |
|
Ten Spyware-Filtering Solutions for Businesses |
|
|
295 | (12) |
|
|
296 | (1) |
|
|
297 | (1) |
|
SpyBot - Search & Destroy |
|
|
298 | (1) |
|
eTrust PestPatrol Anti-Spyware |
|
|
299 | (1) |
|
|
300 | (1) |
|
McAfee Anti-Spyware Enterprise Edition Module |
|
|
301 | (1) |
|
Panda Platinum Internet Security 2005 |
|
|
302 | (1) |
|
|
303 | (1) |
|
|
303 | (1) |
|
Microsoft Windows AntiSpyware |
|
|
304 | (3) |
|
Ten Online Resources for Resolving Spam and Spyware |
|
|
307 | (6) |
|
|
307 | (1) |
|
Coalition Against Unsolicited Commercial Email (CAUCE) |
|
|
308 | (1) |
|
Internet Privacy For Dummies |
|
|
309 | (1) |
|
The SPAM-L Tracking Spam FAQ |
|
|
309 | (1) |
|
Federal Trade Commission (FTC) |
|
|
310 | (1) |
|
|
310 | (1) |
|
|
311 | (1) |
|
|
311 | (1) |
|
|
312 | (1) |
|
Anti-Phishing Working Group |
|
|
312 | (1) |
|
Ten Keys to Successful Spyware Filtering |
|
|
313 | (8) |
|
Understanding the Problem |
|
|
313 | (2) |
|
|
315 | (1) |
|
|
315 | (1) |
|
|
316 | (1) |
|
Planning the Installation Judiciously |
|
|
317 | (1) |
|
Testing Your Solution Thoroughly |
|
|
317 | (1) |
|
|
318 | (1) |
|
Monitoring after Implementation |
|
|
319 | (1) |
|
|
319 | (1) |
|
Watching the Product Market |
|
|
320 | (1) |
|
Appendix A: Spam- and Spyware-Filtering Project Plan |
|
|
321 | (6) |
|
Appendix B: Spam- and Spyware-Filtering Project Requirements |
|
|
327 | (14) |
|
|
328 | (7) |
|
Spam-Specific Requirements |
|
|
335 | (3) |
|
Spyware-Specific Requirements |
|
|
338 | (3) |
|
|
341 | (8) |
Index |
|
349 | |