12,99 €
Mehr erfahren.
- Herausgeber: John Wiley & Sons
- Kategorie: Wissenschaft und neue Technologien
- Sprache: Englisch
The world's most infamous hacker offers an insider's view of the low-tech threats to high-tech security
Kevin Mitnick's exploits as a cyber-desperado and fugitive form one of the most exhaustive FBI manhunts in history and have spawned dozens of articles, books, films, and documentaries. Since his release from federal prison, in 1998, Mitnick has turned his life around and established himself as one of the most sought-after computer security experts worldwide. Now, in The Art of Deception, the world's most notorious hacker gives new meaning to the old adage, "It takes a thief to catch a thief."
Focusing on the human factors involved with information security, Mitnick explains why all the firewalls and encryption protocols in the world will never be enough to stop a savvy grifter intent on rifling a corporate database or an irate employee determined to crash a system. With the help of many fascinating true stories of successful attacks on business and government, he illustrates just how susceptible even the most locked-down information systems are to a slick con artist impersonating an IRS agent. Narrating from the points of view of both the attacker and the victims, he explains why each attack was so successful and how it could have been prevented in an engaging and highly readable style reminiscent of a true-crime novel. And, perhaps most importantly, Mitnick offers advice for preventing these types of social engineering hacks through security protocols, training programs, and manuals that address the human element of security.
Das E-Book können Sie in Legimi-Apps oder einer beliebigen App lesen, die das folgende Format unterstützen:
Veröffentlichungsjahr: 2011
Ähnliche
Table of Contents
Cover
Social Engineering
Foreword
Preface
STARTING OUT
FINAL THOUGHTS
Introduction
Part 1: Behind the Scenes
Chapter 1: Security's Weakest Link
THE HUMAN FACTOR
A CLASSIC CASE OF DECEPTION
THE NATURE OF THE THREAT
ABUSE OF TRUST
TERRORISTS AND DECEPTION
ABOUT THIS BOOK
Part 2: The Art of the Attacker
Chapter 2: When Innocuous Information Isn't
THE HIDDEN VALUE OF INFORMATION
CREDITCHEX
THE ENGINEER TRAP
MORE “WORTHLESS” INFO
PREVENTING THE CON
Chapter 3: The Direct Attack: Just Asking for It
AN MLAC QUICKIE
YOUNG MAN ON THE RUN
ON THE DOORSTEP
GAS ATTACK
PREVENTING THE CON
Chapter 4: Building Trust
TRUST: THE KEY TO DECEPTION
VARIATION ON A THEME: CARD CAPTURE
THE ONE-CENT CELL PHONE
HACKING INTO THE FEDS
PREVENTING THE CON
Chapter 5: “Let Me Help You”
THE NETWORK OUTAGE
A LITTLE HELP FOR THE NEW GAL
NOT AS SAFE AS YOU THINK
PREVENTING THE CON
Chapter 6: “Can You Help Me?”
THE OUT-OF-TOWNER
SPEAKEASY SECURITY
THE CARELESS COMPUTER MANAGER
PREVENTING THE CON
Chapter 7: Phony Sites and Dangerous Attachments
“WOULDN'T YOU LIKE A FREE (BLANK)?”
MESSAGE FROM A FRIEND
VARIATIONS ON A THEME
VARIATIONS ON THE VARIATION
Chapter 8: Using Sympathy, Guilt, and Intimidation
A VISIT TO THE STUDIO
“DO IT NOW”
“MR. BIGG WANTS THIS”
WHAT THE SOCIAL SECURITY ADMINISTRATION KNOWS ABOUT YOU
ONE SIMPLE CALL
THE POLICE RAID
TURNING THE TABLES
PREVENTING THE CON
Chapter 9: The Reverse Sting
THE ART OF FRIENDLY PERSUASION
COPS AS DUPES
PREVENTING THE CON
Part 3: Intruder Alert
Chapter 10: Entering the Premises
THE EMBARRASSED SECURITY GUARD
DUMPSTER DIVING
THE HUMILIATED BOSS
THE PROMOTION SEEKER
SNOOPING ON KEVIN
PREVENTING THE CON
Chapter 11: Combining Technology and Social Engineering
HACKING BEHIND BARS
THE SPEEDY DOWNLOAD
EASY MONEY
THE DICTIONARY AS AN ATTACK TOOL
PREVENTING THE CON
Chapter 12: Attacks on the Entry-Level Employee
THE HELPFUL SECURITY GUARD
THE EMERGENCY PATCH
THE NEW GIRL
PREVENTING THE CON
Chapter 13: Clever Cons
THE MISLEADING CALLER ID
VARIATION: THE PRESIDENT OF THE UNITED STATES IS CALLING
THE INVISIBLE EMPLOYEE
THE HELPFUL SECRETARY
TRAFFIC COURT
SAMANTHA'S REVENGE
PREVENTING THE CON
Chapter 14: Industrial Espionage
VARIATION ON A SCHEME
THE NEW BUSINESS PARTNER
LEAPFROG
PREVENTING THE CON
Part 4: Raising the Bar
Chapter 15: Information Security Awareness and Training
SECURITY THROUGH TECHNOLOGY, TRAINING, AND PROCEDURES
UNDERSTANDING HOW ATTACKERS TAKE ADVANTAGE OF HUMAN NATURE
CREATING TRAINING AND AWARENESS PROGRAMS
TESTING
ONGOING AWARENESS
WHAT'S IN IT FOR ME?
Chapter 16: Recommended Corporate Information Security Policies
WHAT IS A SECURITY POLICY?
DATA CLASSIFICATION
VERIFICATION AND AUTHORIZATION PROCEDURES
MANAGEMENT POLICIES
INFORMATION TECHNOLOGY POLICIES
POLICIES FOR ALL EMPLOYEES
POLICIES FOR TELECOMMUTERS
POLICIES FOR HUMAN RESOURCES
POLICIES FOR PHYSICAL SECURITY
POLICIES FOR RECEPTIONISTS
POLICIES FOR THE INCIDENT REPORTING GROUP
Security at a Glance
Sources
Acknowledgments
Index
End User License Agreement
List of Illustrations
Chapter 7
Figure 7.1
The link in this or any other email should be used with caution.
Guide
Cover
Table of Contents
Begin Reading
Pages
i
ii
iii
iv
v
vii
viii
ix
x
xi
xii
xiii
xv
xvi
1
3
4
5
6
7
8
9
10
11
12
13
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
39
41
42
43
44
45
46
47
48
49
50
51
52
53
55
56
57
58
59
60
61
62
63
71
64
65
66
67
68
69
70
72
73
74
75
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
THE ART OF DECEPTION
Controlling the Human Element of Security
Kevin D. Mitnick
William L. Simon
Publisher: Robert Ipsen Editor: Carol Long
Developmental Editor: Nancy Stevenson
Managing Editor: John Atkins
Interior Design: Marie Kristine Parial-Leonardo
Text Design & Composition: Wiley Composition Services
Chart Design: Stacey Kirkland
Designations used by companies to distinguish their products are often claimed as trademarks. In all instances where Wiley Publishing, Inc., is aware of a claim, the product names appear in initial capital or ALL CAPITAL LETTERS. Readers, however, should contact the appropriate companies for more complete information regarding trademarks and registration.
This book is printed on acid-free paper.
Copyright © 2002 by Kevin D. Mitnick. All rights reserved.
Published by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 750-4470. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4447, Email: [email protected].
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.
For general information on our other products and services please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.
Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.
ISBN: 0-471-23712-4
For Reba Vartanian, Shelly Jaffe, Chickie Leventhal, and Mitchell Mitnick, and for the late Alan Mitnick, Adam Mitnick, and Jack Biello
For Arynne, Victoria, and David, Sheldon, Vincent, and Elena
Social Engineering
Social engineering uses influence and persuasion to deceive people by convincing them that the social engineer is someone he is not, or by manipulation. As a result, the social engineer is able to take advantage of people to obtain information with or without the use of technology.
Foreword
We humans are born with an inner drive to explore the nature of our surroundings. As young men, both Kevin Mitnick and I were intensely curious about the world and eager to prove ourselves. We were rewarded often in our attempts to learn new things, solve puzzles, and win at games. But at the same time, the world around us taught us rules of behavior that constrained our inner urge toward free exploration. For our boldest scientists and technological entrepreneurs, as well as for people like Kevin Mitnick, following this inner urge offers the greatest thrills, letting us accomplish things that others believe cannot be done.
Kevin Mitnick is one of the finest people I know. Ask him, and he will say forthrightly that what he used to do—social engineering—involves conning people. But Kevin is no longer a social engineer. And even when he was, his motive never was to enrich himself or damage others. That's not to say that there aren't dangerous and destructive criminals out there who use social engineering to cause real harm. In fact, that's exactly why Kevin wrote this book—to warn you about them.
The Art of Deception shows how vulnerable we all are—government, business, and each of us personally—to the intrusions of the social engineer. In this security-conscious era, we spend huge sums on technology to protect our computer networks and data. This book points out how easy it is to trick insiders and circumvent all this technological protection.
Whether you work in business or government, this book provides a powerful road map to help you understand how social engineers work and what you can do to foil them. Using fictionalized stories that are both entertaining and eye-opening, Kevin and coauthor Bill Simon bring to life the techniques of the social engineering underworld. After each story, they offer practical guidelines to help you guard against the breaches and threats they've described.
Technological security leaves major gaps that people like Kevin can help us close. Read this book and you may finally realize that we all need to turn to the Mitnick's among us for guidance.
— Steve Wozniak
Preface
Some hackers destroy people's files or entire hard drives; they're called crackers or vandals. Some novice hackers don't bother learning the technology, but simply download hacker tools to break into computer systems; they're called script kiddies. More experienced hackers with programming skills develop hacker programs and post them to the Web and to bulletin board systems. And then there are individuals who have no interest in the technology, but use the computer merely as a tool to aid them in stealing money, goods, or services.
Despite the media-created myth of Kevin Mitnick, I am not a malicious hacker.
But I'm getting ahead of myself.
STARTING OUT
My path was probably set early in life. I was a happy-go-lucky kid, but bored. After my father split when I was three, my mother worked as a waitress to support us. To see me then—an only child being raised by a mother who put in long, harried days on a sometimes-erratic schedule— would have been to see a youngster on his own almost all his waking hours. I was my own babysitter.
Growing up in a San Fernando Valley community gave me the whole of Los Angeles to explore, and by the age of twelve I had discovered a way to travel free throughout the whole greater L.A. area. I realized one day while riding the bus that the security of the bus transfer I had purchased relied on the unusual pattern of the paper-punch that the drivers used to mark day, time, and route on the transfer slips. A friendly driver, answering my carefully planted question, told me where to buy that special type of punch.
The transfers are meant to let you change buses and continue a journey to your destination, but I worked out how to use them to travel anywhere I wanted to go for free. Obtaining blank transfers was a walk in the park.
The trash bins at the bus terminals were always filled with only-partly-used books of transfers that the drivers tossed away at the end of their shifts. With a pad of blanks and the punch, I could mark my own transfers and travel anywhere that L.A. buses went. Before long, I had all but memorized the bus schedules of the entire system. (This was an early example of my surprising memory for certain types of information; I can still, today, remember phone numbers, passwords, and other seemingly trivial details as far back as my childhood.)
Another personal interest that surfaced at an early age was my fascination with performing magic. Once I learned how a new trick worked, I would practice, practice, and practice some more until I mastered it. To an extent, it was through magic that I discovered the enjoyment in gaining secret knowledge.
From Phone Phreak to Hacker
My first encounter with what I would eventually learn to call social engineering came about during my high school years when I met another student who was caught up in a hobby called phone phreaking. Phone phreaking is a type of hacking that allows you to explore the telephone network by exploiting the phone systems and phone company employees.
He showed me neat tricks he could do with a telephone, like obtaining any information the phone company had on any customer, and using a secret test number to make long-distance calls for free. (Actually it was free only to us. I found out much later that it wasn't a secret test number at all. The calls were, in fact, being billed to some poor company's MCI account.)
That was my introduction to social engineering—my kindergarten, so to speak. My friend and another phone phreaker I met shortly thereafter let me listen in as they each made pretext calls to the phone company. I heard the things they said that made them sound believable; I learned about different phone company offices, lingo, and procedures. But that "training" didn't last long; it didn't have to. Soon I was doing it all on my own, learning as I went, doing it even better than my first teachers.
The course my life would follow for the next fifteen years had been set.
In high school, one of my all-time favorite pranks was gaining unauthorized access to the telephone switch and changing the class of service of a fellow phone phreak. When he'd attempt to make a call from home, he'd get a message telling him to deposit a dime because the telephone company switch had received input that indicated he was calling from a pay phone.
I became absorbed in everything about telephones, not only the electronics, switches, and computers, but also the corporate organization, the procedures, and the terminology. After a while, I probably knew more about the phone system than any single employee. And I had developed my social engineering skills to the point that, at seventeen years old, I was able to talk most telco employees into almost anything, whether I was speaking with them in person or by telephone.
My much-publicized hacking career actually started when I was in high school. While I cannot describe the detail here, suffice it to say that one of the driving forces in my early hacks was to be accepted by the guys in the hacker group.
Back then we used the term hacker to mean a person who spent a great deal of time tinkering with hardware and software, either to develop more efficient programs or to bypass unnecessary steps and get the job done more quickly. The term has now become a pejorative, carrying the meaning of "malicious criminal." In these pages I use the term the way I have always used it—in its earlier, more benign sense.
After high school I studied computers at the Computer Learning Center in Los Angeles. Within a few months, the school's computer manager realized I had found vulnerability in the operating system and gained full administrative privileges on their IBM minicomputer. The best computer experts on their teaching staff couldn't figure out how I had done this. In what may have been one of the earliest examples of "hire the hacker," I was given an offer I couldn't refuse: Do an honors project to enhance the school's computer security, or face suspension for hacking the system. Of course, I chose to do the honors project, and ended up graduating cum laude with honors.
Becoming a Social Engineer
Some people get out of bed each morning dreading their daily work routine at the proverbial salt mines. I've been lucky enough to enjoy my work. In particular, you can't imagine the challenge, reward, and pleasure I had in the time I spent as a private investigator. I was honing my talents in the performance art called social engineering (getting people to do things they wouldn't ordinarily do for a stranger) and being paid for it.
For me it wasn't difficult becoming proficient in social engineering. My father's side of the family had been in the sales field for generations, so the art of influence and persuasion might have been an inherited trait. When you combine that trait with an inclination for deceiving people, you have the profile of a typical social engineer.
You might say there are two specialties within the job classification of con artist. Somebody who swindles and cheats people out of their money belongs to one sub-specialty, the grifter. Somebody who uses deception, influence, and persuasion against businesses, usually targeting their information, belongs to the other sub-specialty, the social engineer. From the time of my bus-transfer trick, when I was too young to know there was anything wrong with what I was doing, I had begun to recognize a talent for finding out the secrets I wasn't supposed to have. I built on that talent by using deception, knowing the lingo, and developing a well-honed skill of manipulation.
One way I worked on developing the skills of my craft, if I may call it a craft, was to pick out some piece of information I didn't really care about and see if I could talk somebody on the other end of the phone into providing it, just to improve my skills. In the same way I used to practice my magic tricks, I practiced pretexting. Through these rehearsals, I soon found that I could acquire virtually any information I targeted.
As I described in Congressional testimony before Senators Lieberman and Thompson years later:
I have gained unauthorized access to computer systems at some of the largest corporations on the planet, and have successfully penetrated some of the most resilient computer systems ever developed. I have used both technical and nontechnical means to obtain the source code to various operating systems and telecommunications devices to study their vulnerabilities and their inner workings.
All of this activity was really to satisfy my own curiosity; to see what I could do; and find out secret information about operating systems, cell phones, and anything else that stirred my curiosity.
FINAL THOUGHTS
I've acknowledged since my arrest that the actions I took were illegal, and that I committed invasions of privacy.
My misdeeds were motivated by curiosity. I wanted to know as much as I could about how phone networks worked and the ins-and-outs of computer security. I went from being a kid who loved to perform magic tricks to becoming the world's most notorious hacker, feared by corporations and the government. As I reflect back on my life for the last 30 years, I admit I made some extremely poor decisions, driven by my curiosity, the desire to learn about technology, and the need for a good intellectual challenge.
I'm a changed person now. I'm turning my talents and the extensive knowledge I've gathered about information security and social engineering tactics to helping government, businesses, and individuals prevent, detect, and respond to information-security threats.
This book is one more way that I can use my experience to help others avoid the efforts of the malicious information thieves of the world. I think you will find the stories enjoyable, eye-opening, and educational.
Introduction
This book contains a wealth of information about information security and social engineering. To help you find your way, here's a quick look at how this book is organized:
In Part 1 I'll reveal security's weakest link and show you why you and your company are at risk from social engineering attacks.
In Part 2 you'll see how social engineers toy with your trust, your desire to be helpful, your sympathy, and your human gullibility to get what they want. Fictional stories of typical attacks will demonstrate that social engineers can wear many hats and many faces. If you think you've never encountered one, you're probably wrong. Will you recognize a scenario you've experienced in these stories and wonder if you had a brush with social engineering? You very well might. But once you've read Chapters 2 through 9, you'll know how to get the upper hand when the next social engineer comes calling.
Part 3 is the part of the book where you see how the social engineer ups the ante, in made-up stories that show how he can step onto your corporate premises, steal the kind of secret that can make or break your company, and thwart your hi-tech security measures. The scenarios in this section will make you aware of threats that range from simple employee revenge to cyber terrorism. If you value the information that keeps your business running and the privacy of your data, you'll want to read Chapters 10 through 14 from beginning to end.
It's important to note that unless otherwise stated, the anecdotes in this book are purely fictional.
In Part 4 I talk the corporate talk about how to prevent successful social engineering attacks on your organization. Chapter 15 provides a blueprint for a successful security-training program. And Chapter 16 might just save your neck—it's a complete security policy you can customize for your organization and implement right away to keep your company and information safe.
Finally, I've provided a Security at a Glance section, which includes checklists, tables, and charts that summarize key information you can use to help your employees foil a social engineering attack on the job. These tools also provide valuable information you can use in devising your own security-training program.
Throughout the book you'll also find several useful elements: Lingo boxes provide definitions of social engineering and computer hacker terminology; Mitnick Messages offer brief words of wisdom to help strengthen your security strategy; and notes and sidebars give interesting background or additional information.
Part 1Behind the Scenes
Chapter 1Security's Weakest Link
A company may have purchased the best security technologies that money can buy, trained their people so well that they lock up all their secrets before going home at night, and hired building guards from the best security firm in the business.
That company is still totally vulnerable.
Individuals may follow every best-security practice recommended by the experts, slavishly install every recommended security product, and be thoroughly vigilant about proper system configuration and applying security patches.
Those individuals are still completely vulnerable.
THE HUMAN FACTOR
Testifying before Congress not long ago, I explained that I could often get passwords and other pieces of sensitive information from companies by pretending to be someone else and just asking for it.
It's natural to yearn for a feeling of absolute safety, leading many people to settle for a false sense of security. Consider the responsible and loving homeowner who has a Medico, a tumbler lock known as being pickproof, installed in his front door to protect his wife, his children, and his home. He's now comfortable that he has made his family much safer against intruders. But what about the intruder who breaks a window, or cracks the code to the garage door opener? How about installing a robust security system? Better, but still no guarantee. Expensive locks or no, the homeowner remains vulnerable.
Why? Because the human factor is truly security's weakest link.
Security is too often merely an illusion, an illusion sometimes made even worse when gullibility, naïveté, or ignorance come into play. The world's most respected scientist of the twentieth century, Albert Einstein, is quoted as saying, “Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.” In the end, social engineering attacks can succeed when people are stupid or, more commonly, simply ignorant about good security practices. With the same attitude as our security-conscious homeowner, many information technology (IT) professionals hold to the misconception that they've made their companies largely immune to attack because they've deployed standard security products—firewalls, intrusion detection systems, or stronger authentication devices such as time-based tokens or biometric smart cards. Anyone who thinks that security products alone offer true security is settling for the illusion of security. It's a case of living in a world of fantasy: They will inevitably, later if not sooner, suffer a security incident.
As noted security consultant Bruce Schneier puts it, “Security is not a product, it's a process.” Moreover, security is not a technology problem—it's a people and management problem.
As developers invent continually better security technologies, making it increasingly difficult to exploit technical vulnerabilities, attackers will turn more and more to exploiting the human element. Cracking the human firewall is often easy, requires no investment beyond the cost of a phone call, and involves minimal risk.
A CLASSIC CASE OF DECEPTION
What's the greatest threat to the security of your business assets? That's easy: the social engineer—an unscrupulous magician who has you watching his left hand while with his right he steals your secrets. This character is often so friendly, glib, and obliging that you're grateful for having encountered him.
Take a look at an example of social engineering. Not many people today still remember the young man named Stanley Mark Rifkin and his little adventure with the now defunct Security Pacific National Bank in Los Angeles. Accounts of his escapade vary, and Rifkin (like me) has never told his own story, so the following is based on published reports.
Code Breaking
One day in 1978, Rifkin moseyed over to Security Pacific's authorized-personnel-only wire-transfer room, where the staff sent and received transfers totaling several billion dollars every day.
He was working for a company under contract to develop a backup system for the wire room's data in case their main computer ever went down. That role gave him access to the transfer procedures, including how bank officials arranged for a transfer to be sent. He had learned that bank officers who were authorized to order wire transfers would be given a closely guarded daily code each morning to use when calling the wire room.
In the wire room the clerks saved themselves the trouble of trying to memorize each day's code: They wrote down the code on a slip of paper and posted it where they could see it easily. This particular November day Rifkin had a specific reason for his visit. He wanted to get a glance at that paper.
Arriving in the wire room, he took some notes on operating procedures, supposedly to make sure the backup system would mesh properly with the regular systems. Meanwhile, he surreptitiously read the security code from the posted slip of paper, and memorized it. A few minutes later he walked out. As he said afterward, he felt as if he had just won the lottery.
There's This Swiss Bank Account…
Leaving the room at about 3 o'clock in the afternoon, he headed straight for the pay phone in the building's marble lobby, where he deposited a coin and dialed into the wire-transfer room. He then changed hats, transforming himself from Stanley Rifkin, bank consultant, into Mike Hansen, a member of the bank's International Department.
According to one source, the conversation went something like this:
”Hi, this is Mike Hansen in International,” he said to the young woman who answered the phone.
She asked for the office number. That was standard procedure, and he was prepared: “286,” he said.
The girl then asked, “Okay, what's the code?”
Rifkin has said that his adrenaline-powered heartbeat “picked up its pace” at this point. He responded smoothly, “4789.” Then he went on to give instructions for wiring “Ten million, two-hundred thousand dollars exactly” to the Irving Trust Company in New York, for credit of the Wozchod Handels Bank of Zurich, Switzerland, where he had already established an account.
The girl then said, “Okay, I got that. And now I need the interoffice settlement number.”
Rifkin broke out in a sweat; this was a question he hadn't anticipated, something that had slipped through the cracks in his research. But he managed to stay in character, acted as if everything was fine, and on the spot answered without missing a beat, “Let me check; I'll call you right back.” He changed hats once again to call another department at the bank, this time claiming to be an employee in the wire-transfer room. He obtained the settlement number and called the girl back.
She took the number and said, “Thanks.” (Under the circumstances, her thanking him has to be considered highly ironic.)
Achieving Closure
A few days later Rifkin flew to Switzerland, picked up his cash, and handed over $8 million to a Russian agency for a pile of diamonds. He flew back, passing through U.S. Customs with the stones hidden in a money belt. He had pulled off the biggest bank heist in history—and done it without using a gun, even without a computer. Oddly, his caper eventually made it into the pages of the Guinness Book of World Records in the category of “biggest computer fraud.”
Stanley Rifkin had used the art of deception—the skills and techniques that are today called social engineering. Thorough planning and a good gift of gab is all it really took.
And that's what this book is about—the techniques of social engineering (at which yours truly is proficient) and how to defend against their being used at your company.
THE NATURE OF THE THREAT
The Rifkin story makes perfectly clear how misleading our sense of security can be. Incidents like this—okay, maybe not $10 million heists, but harmful incidents nonetheless—are happening every day. You may be losing money right now, or somebody may be stealing new product plans, and you don't even know it. If it hasn't already happened to your company, it's not a question of if it will happen, but when.
A Growing Concern
The Computer Security Institute, in its 2001 survey of computer crime, reported that 85 percent of responding organizations had detected computer security breaches in the preceding twelve months. That's an astounding number: Only fifteen out of every hundred organizations responding were able to say that they had not had a security breach during the year. Equally astounding was the number of organizations that reported that they had experienced financial losses due to computer breaches: 64 percent. Well over half the organizations had suffered financially. In a single year.
My own experiences lead me to believe that the numbers in reports like this are somewhat inflated. I'm suspicious of the agenda of the people conducting the survey. But that's not to say that the damage isn't extensive; it is. Those who fail to plan for a security incident are planning for failure.
Commercial security products deployed in most companies are mainly aimed at providing protection against the amateur computer intruder, like the youngsters known as script kiddies. In fact, these wannabe hackers with downloaded software are mostly just a nuisance. The greater losses, the real threats, come from sophisticated attackers with well-defined targets who are motivated by financial gain. These people focus on one target at a time rather than, like the amateurs, trying to infiltrate as many systems as possible. While amateur computer intruders simply go for quantity, the professionals target information of quality and value.
Technologies like authentication devices (for proving identity), access control (for managing access to files and system resources), and intrusion detection systems (the electronic equivalent of burglar alarms) are necessary to a corporate security program. Yet it's typical today for a company to spend more money on coffee than on deploying countermeasures to protect the organization against security attacks.
Just as the criminal mind cannot resist temptation, the hacker mind is driven to find ways around powerful security technology safeguards. And in many cases, they do that by targeting the people who use the technology.
Deceptive Practices
There's a popular saying that a secure computer is one that's turned off. Clever, but false: The pretexter simply talks someone into going into the office and turning that computer on. An adversary who wants your information can obtain it, usually in any one of several different ways. It's just a matter of time, patience, personality, and persistence. That's where the art of deception comes in.
To defeat security measures, an attacker, intruder, or social engineer must find a way to deceive a trusted user into revealing information, or trick an unsuspecting mark into providing him with access. When trusted employees are deceived, influenced, or manipulated into revealing sensitive information, or performing actions that create a security hole for the attacker to slip through, no technology in the world can protect a business. Just as cryptanalysts are sometimes able to reveal the plain text of a coded message by finding a weakness that lets them bypass the encryption technology, social engineers use deception practiced on your employees to bypass security technology.
ABUSE OF TRUST
In most cases, successful social engineers have strong people skills. They're charming, polite, and easy to like—social traits needed for establishing rapid rapport and trust. An experienced social engineer is able to gain access to virtually any targeted information by using the strategies and tactics of his craft.
Savvy technologists have painstakingly developed information-security solutions to minimize the risks connected with the use of computers, yet left unaddressed the most significant vulnerability, the human factor. Despite our intellect, we humans—you, me, and everyone else—remain the most severe threat to each other's security.
Our National Character
We're not mindful of the threat, especially in the Western world. In the United States most of all, we're not trained to be suspicious of each other. We are taught to “love thy neighbor” and have trust and faith in each other. Consider how difficult it is for neighborhood watch organizations to get people to lock their homes and cars. This sort of vulnerability is obvious, and yet it seems to be ignored by many who prefer to live in a dream world—until they get burned.
We know that all people are not kind and honest, but too often we live as if they were. This lovely innocence has been the fabric of the lives of Americans and it's painful to give it up. As a nation we have built into our concept of freedom that the best places to live are those where locks and keys are the least necessary.
Most people go on the assumption that they will not be deceived by others, based upon a belief that the probability of being deceived is very low; the attacker, understanding this common belief, makes his request sound so reasonable that it raises no suspicion, all the while exploiting the victim's trust.
Organizational Innocence
That innocence that is part of our national character was evident back when computers were first being connected remotely. Recall that the ARPANet (the Defense Department's Advanced Research Projects Agency Network), the predecessor of the Internet, was designed as a way of sharing research information between government, research, and educational institutions. The goal was information freedom, as well as technological advancement. Many educational institutions therefore set up early computer systems with little or no security. One noted software libertarian, Richard Stallman, even refused to protect his account with a password.
But with the Internet being used for electronic commerce, the dangers of weak security in our wired world have changed dramatically. Deploying more technology is not going to solve the human security problem.
Just look at our airports today. Security has become paramount, yet we're alarmed by media reports of travelers who have been able to circumvent security and carry potential weapons past checkpoints. How is this possible during a time when our airports are on such a state of alert? Are the metal detectors failing? No. The problem isn't the machines. The problem is the human factor: The people manning the machines. Airport officials can marshal the National Guard and install metal detectors and facial recognition systems, but educating the frontline security staff on how to properly screen passengers is much more likely to help.
The same problem exists within government, business, and educational institutions throughout the world. Despite the efforts of security professionals, information everywhere remains vulnerable and will continue to be seen as a ripe target by attackers with social engineering skills, until the weakest link in the security chain, the human link, has been strengthened.
Now more than ever we must learn to stop wishful thinking and become more aware of the techniques that are being used by those who attempt to attack the confidentiality, integrity, and availability of our computer systems and networks. We've come to accept the need for defensive driving; it's time to accept and learn the practice of defensive computing.
The threat of a break-in that violates your privacy, your mind, or your company's information systems may not seem real until it happens. To avoid such a costly dose of reality, we all need to become aware, educated, vigilant, and aggressively protective of our information assets, our own personal information, and our nation's critical infrastructures. And we must implement those precautions today.
TERRORISTS AND DECEPTION
Of course, deception isn't an exclusive tool of the social engineer. Physical terrorism makes the biggest news, and we have come to realize as never before that the world is a dangerous place. Civilization is, after all, just a thin veneer.
The attacks on New York and Washington, D.C., in September 2001 infused sadness and fear into the hearts of every one of us—not just Americans, but well-meaning people of all nations. We're now alerted to the fact that there are obsessive terrorists located around the globe, well-trained and waiting to launch further attacks against us.
The recently intensified effort by our government has increased the levels of our security consciousness. We need to stay alert, on guard against all forms of terrorism. We need to understand how terrorists treacherously create false identities, assume roles as students and neighbors, and melt into the crowd. They mask their true beliefs while they plot against us—practicing tricks of deception similar to those you will read about in these pages.
And while, to the best of my knowledge, terrorists have not yet used social engineering ruses to infiltrate corporations, water-treatment plants, electrical generation facilities, or other vital components of our national infrastructure, the potential is there. It's just too easy. The security awareness and security policies that I hope will be put into place and enforced by corporate senior management because of this book will come none too soon.
ABOUT THIS BOOK
Corporate security is a question of balance. Too little security leaves your company vulnerable, but an overemphasis on security gets in the way of attending to business, inhibiting the company's growth and prosperity. The challenge is to achieve a balance between security and productivity.
Other books on corporate security focus on hardware and software technology, and do not adequately cover the most serious threat of all: human deception. The purpose of this book, in contrast, is to help you understand how you, your coworkers, and others in your company are being manipulated, and the barriers you can erect to stop being victims. The book focuses mainly on the non-technical methods that hostile intruders use to steal information, compromise the integrity of information that is believed to be safe but isn't, or destroy company work product.
My task is made more difficult by a simple truth: Every reader will have been manipulated by the grand experts of all time in social engineering—their parents. They found ways to get you—“for your own good”—to do what they thought best. Parents become great storytellers in the same way that social engineers skillfully develop very plausible stories, reasons, and justifications for achieving their goals. Yes, we were all molded by our parents: benevolent (and sometimes not so benevolent) social engineers.
Conditioned by that training, we have become vulnerable to manipulation. We would live a difficult life if we had to be always on our guard, mistrustful of others, concerned that we might become the dupe of someone trying to take advantage of us. In a perfect world we would implicitly trust others, confident that the people we encounter are going to be honest and trustworthy. But we do not live in a perfect world, and so we have to exercise a standard of vigilance to repel the deceptive efforts of our adversaries.
The main portions of this book, Parts 2 and 3, are made up of stories that show you social engineers in action. In these sections you'll read about:
What phone phreaks discovered years ago: A slick method for getting an unlisted phone number from the telephone company.
Several different methods used by attackers to convince even alert, suspicious employees to reveal their computer usernames and passwords.
How an Operations Center manager cooperated in allowing an attacker to steal his company's most secret product information.
The methods of an attacker who deceived a lady into downloading software that spies on every keystroke she makes and emails the details to him.
How private investigators get information about your company, and about you personally, that I can practically guarantee will send a chill up your spine.
You might think as you read some of the stories in Parts 2 and 3 that they're not possible, that no one could really succeed in getting away with the lies, dirty tricks, and schemes described in these pages. The reality is that in every case, these stories depict events that can and do happen; many of them are happening every day somewhere on the planet, maybe even to your business as you read this book.
The material in this book will be a real eye-opener when it comes to protecting your business, but also personally deflecting the advances of a social engineer to protect the integrity of information in your private life.
In Part 4 of this book I switch gears. My goal here is to help you create the necessary business policies and awareness training to minimize the chances of your employees ever being duped by a social engineer. Understanding the strategies, methods, and tactics of the social engineer will help prepare you to deploy reasonable controls to safeguard your IT assets, without undermining your company's productivity.
In short, I've written this book to raise your awareness about the serious threat posed by social engineering, and to help you make sure that your company and its employees are less likely to be exploited in this way.
Or perhaps I should say, far less likely to be exploited ever again.
Part 2The Art of the Attacker
Chapter 2When Innocuous Information Isn't
What do most people think is the real threat from social engineers? What should you do to be on your guard?
If the goal is to capture some highly valuable prize—say, a vital component of the company's intellectual capital—then perhaps what's needed is, figuratively, just a stronger vault and more heavily armed guards. Right?
But in reality penetrating a company's security often starts with the bad guy obtaining some piece of information or some document that seems so innocent, so everyday and unimportant, that most people in the organization wouldn't see any reason why the item should be protected and restricted.
THE HIDDEN VALUE OF INFORMATION
Much of the seemingly innocuous information in a company's possession is prized by a social engineering attacker because it can play a vital role in his effort to dress himself in a cloak of believability.
Throughout these pages, I'm going to show you how social engineers do what they do by letting you “witness” the attacks for yourself—sometimes presenting the action from the viewpoint of the people being victimized, allowing you to put yourself in their shoes and gauge how you yourself (or maybe one of your employees or coworkers) might have responded. In many cases you'll also experience the same events from the perspective of the social engineer.
The first story looks at a vulnerability in the financial industry.
CREDITCHEX
For a long time, the British put up with a very stuffy banking system. As an ordinary, upstanding citizen, you couldn't walk in off the street and open a bank account. No, the bank wouldn't consider accepting you as a customer unless some person already well established as a customer provided you with a letter of recommendation.
Quite a difference, of course, in the seemingly egalitarian banking world of today. And our modern ease of doing business is nowhere more in evidence than in friendly, democratic America, where almost anyone can walk into a bank and easily open a checking account, right? Well, not exactly. The truth is that banks understandably have a natural reluctance to open an account for somebody who just might have a history of writing bad checks—that would be about as welcome as a rap sheet of bank robbery or embezzlement charges. So it's standard practice at many banks to get a quick thumbs-up or thumbs-down on a prospective new customer.
One of the major companies that banks contract with for this information is an outfit we'll call CreditChex. They provide a valuable service to their clients, but like many companies, can also unknowingly provide a handy service to knowing social engineers.
The First Call: Kim Andrews
“National Bank, this is Kim. Did you want to open an account today?”
“Hi, Kim. I have a question for you. Do you guys use CreditChex?”
“Yes.”
“When you phone in to CreditChex, what do you call the number you give them—is it a ‘Merchant ID’?”
A pause; she was weighing the question, wondering what this was about and whether she should answer.
The caller quickly continued without missing a beat:
“Because, Kim, I'm working on a book. It deals with private investigations.”
“Yes,” she said, answering the question with new confidence, pleased to be helping a writer.
“So it's called a Merchant ID, right?”
“Uh huh.”
“Okay, great. Because I wanted to make sure I had the lingo right. For the book. Thanks for your help. Good-bye, Kim.”
The Second Call: Chris Talbert
“National Bank, New Accounts, this is Chris.”
“Hi, Chris. This is Alex,” the caller said. “I'm a customer service rep with CreditChex. We're doing a survey to improve our services. Can you spare me a couple of minutes?”
She was glad to, and the caller went on:
“Okay—what are the hours your branch is open for business?” She answered, and continued answering his string of questions.
“How many employees at your branch use our service?”
“How often do you call us with an inquiry?”
“Which of our 800-numbers have we assigned you for calling us?”
“Have our representatives always been courteous?”
“How's our response time?”
“How long have you been with the bank?”
“What Merchant ID are you currently using?”
“Have you ever found any inaccuracies with the information we've provided you?”
“If you had any suggestions for improving our service, what would they be?”
And:
“Would you be willing to fill out periodic questionnaires if we send them to your branch?”
She agreed, they chatted a bit, the caller rang off, and Chris went back to work.
The Third Call: Henry McKinsey
“CreditChex, this is Henry McKinsey, how can I help you?”
The caller said he was from National Bank. He gave the proper Merchant ID and then gave the name and social security number of the person he was looking for information on. Henry asked for the birth date, and the caller gave that, too. After a few moments, Henry read the listing from his computer screen.
“Wells Fargo reported NSF in 1998, one time, amount of $2,066.” NSF—nonsufficient funds—is the familiar banking lingo for checks that have been written when there isn't enough money in the account to cover them.
“Any activities since then?”
“No activities.”
“Have there been any other inquiries?”
“Let's see. Okay, two of them, both last month. Third United Credit Union of Chicago.” He stumbled over the next name, Schenectady Mutual Investments, and had to spell it. “That's in New York State,” he added.
Private Investigator at Work
All three of those calls were made by the same person: a private investigator we'll call Oscar Grace. Grace had a new client, one of his first. A cop until a few months before, he found that some of this new work came naturally, but some offered a challenge to his resources and inventiveness. This one came down firmly in the challenge category.
The hardboiled private eyes of fiction—the Sam Spades and the Philip Marlowes—spend long nighttime hours sitting in cars waiting to catch a cheating spouse. Real-life PIs do the same. They also do a less written about, but no less important kind of snooping for warring spouses, a method that leans more heavily on social engineering skills than on fighting off the boredom of nighttime vigils.
Grace's new client was a lady who looked as if she had a pretty comfortable budget for clothes and jewelry. She walked into his office one day and took a seat in the leather chair, the only one that didn't have papers piled on it. She settled her large Gucci handbag on his desk with the logo turned to face him and announced she was planning to tell her husband that she wanted a divorce, but admitted to “just a very little problem.”
It seemed her hubby was one step ahead. He had already pulled the cash out of their savings account and an even larger sum from their brokerage account. She wanted to know where their assets had been squirreled away, and her divorce lawyer wasn't any help at all. Grace surmised the lawyer was one of those uptown, high-rise counselors who wouldn't get his hands dirty on something messy like where-did-the-money-go.
Could Grace help?
He assured her it would be a breeze, quoted a fee, expenses billed at cost, and collected a check for the first payment.
Then he faced his problem. What do you do if you've never handled a piece of work like this before and don't quite know how to go about tracking down a money trail? You move forward by baby steps. Here, according to our source, is Grace's story.
I knew about CreditChex and how banks used the outfit—my ex-wife used to work at a bank. But I didn't know the lingo and procedures, and trying to ask my ex- would be a waste of time.
Step one: Get the terminology straight and figure out how to make the request so it sounds like I know what I'm talking about. At the bank I called, the first young lady, Kim, was suspicious when I asked about how they identify themselves when they phone CreditChex. She hesitated; she didn't know whether to tell me. Was I put off by that? Not a bit. In fact, the hesitation gave me an important clue, a sign that I had to supply a reason she'd find believable. When I worked the con on her about doing research for a book, it relieved her suspicions. You say you're an author or a movie writer, and everybody opens up.
She had other knowledge that would have helped—things like what information CreditChex requires to identify the person you're calling about, what information you can ask for, and the big one, what was Kim's bank Merchant ID number. I was ready to ask those questions, but her hesitation sent up the red flag. She bought the book research story, but she already had a few niggling suspicions. If she'd been more willing right way, I would have asked her to reveal more details about their procedures.
You have to go on gut instinct, listen closely to what the mark is saying and how she's saying it. This lady sounded smart enough for alarm bells to start going off if I asked too many unusual questions. And even though she didn't know who I was or what number I was calling from, still in this business you never want anybody putting out the word to be on the lookout for someone calling to get information about the business. That's because you don't want to burn the source—you may want to call the same office back another time.
Lingo
MARK The victim of a con.
BURN THE SOURCE An attacker is said to have burned the source when he allows a victim to recognize that an attack has taken place. Once the victim becomes aware and notifies other employees or management of the attempt, it becomes extremely difficult to exploit the same source in future attacks.
I'm always on the watch for little signs that give me a read on how cooperative a person is, on a scale that runs from “You sound like a nice person and I believe everything you're saying” to “Call the cops, alert the National Guard, this guy's up to no good.”
I read Kim as a little bit on edge, so I just called somebody at a different branch. On my second call with Chris, the survey trick played like a charm. The tactic here is to slip the important questions in among inconsequential ones that are used to create a sense of believability. Before I dropped the question about the Merchant ID number with CreditChex, I ran a little last-minute test by asking her a personal question about how long she'd been with the bank.
A personal question is like a land mine—some people step right over it and never notice; for other people, it blows up and sends them scurrying for safety. So if I ask a personal question and she answers the question and the tone of her voice doesn't change, that means she probably isn't skeptical about the nature of the request. I can safely ask the sought-after question without arousing her suspicions, and she'll probably give me the answer I'm looking for.
One more thing a good PI knows: Never end the conversation after getting the key information. Another two or three questions, a little chat, and then it's okay to say good-bye. Later, if the victim remembers anything about what you asked, it will probably be the last couple of questions. The rest will usually be forgotten.
So Chris gave me their Merchant ID number, and the phone number they call to make requests. I would have been happier if I had gotten to ask some questions about how much information you can get from CreditChex. But it was better not to push my luck.
It was like having a blank check on CreditChex. I could now call and get information whenever I wanted. I didn't even have to pay for the service. As it turned out, the CreditChex rep was happy to share exactly the information I wanted: two places my client's husband had recently applied to open an account. So where were the assets his soon-to-be ex-wife was looking for? Where else but at the banking institutions the guy at CreditChex listed?
Analyzing the Con
This entire ruse was based on one of the fundamental tactics of social engineering: gaining access to information that a company employee treats as innocuous, when it isn't.
The first bank clerk confirmed the terminology to describe the identifying number used when calling CreditChex: the Merchant ID. The second provided the phone number for calling CreditChex, and the most vital piece of information, the bank's Merchant ID number. All this information appeared to the clerk to be innocuous. After all, the bank clerk thought she was talking to someone from CreditChex—so what could be the harm in disclosing the number?
All of this laid the groundwork for the third call. Grace had everything he needed to phone CreditChex, pass himself off as a rep from one of their customer banks, National, and simply ask for the information he was after.
With as much skill at stealing information as a good swindler has at stealing your money, Grace had well-honed talents for reading people. He knew the common tactic of burying the key questions among innocent ones. He knew a personal question would test the second clerk's willingness to cooperate, before innocently asking for the Merchant ID number.
The first clerk's error in confirming the terminology for the CreditChex ID number would be almost impossible to protect against. The information is so widely known within the banking industry that it appears to be unimportant—the very model of the innocuous. But the second clerk, Chris, should not have been so willing to answer questions without positively verifying that the caller was really who he claimed to be. She should, at the very least, have taken his name and number and called back; that way, if any questions arose later, she may have kept a record of what phone number the person had used. In this case, making a call like that would have made it much more difficult for the attacker to masquerade as a representative from CreditChex.
