Vulnerabilities / Threats
2/27/2007
07:45 AM
50%
50%

A Hacker by Any Other Name

Black hat? Gray hat? Carder? Cracker? Putting a name on today's hacker is no simple task

5:45 PM -- Okay, confession time. I've been the site editor for a security news portal for almost a year now, and I still don't know the politically correct way to refer to a hacker.

It's not for lack of trying. In fact, I've been working on this stuff for more than 20 years. I remember when I wrote about the Milwaukee 414 gang back in 1984, several people got mad at me for calling them "hackers" and not "crackers." I've read books. I've talked to people, including some of those who started the whole phenomenon. I just finished a survey of 116 people who break into computer systems on a regular basis. (See Five Myths About Black Hats.)

I still can't figure it out.

So let me ask you, the most intelligent readership in the land, if you can help me. I'll describe each of these terms as I understand them, and you tell me where I'm wrong. One warning, though: if I get lots of disagreement from you, we're going to change our style and just call everybody "Bruce."

A hacker, as I understand it, is anyone who tries to break into computer systems to see if they can do it. The "hacker's code" says that if you're successful in breaking in, you should do no harm. So, technically, anyone that penetrates computer systems and makes changes or steals data is not a hacker.

A black hat is someone who breaks into computer systems for malicious purposes, including theft, destruction of data, or denial of service. If a hacker uses his knowledge of systems penetration to do something bad to a computer system, then he is said to be "wearing his black hat." Black hats are sometimes called attackers.

A white hat is someone who breaks into computer systems to show how it can be done, revealing security vulnerabilities in order to help eliminate them. Most white hats swear they will never do anything to hurt the data they access, but occasionally some of them do malicious things, just to prove they can. These are called gray hats.

A carder is someone who penetrates computer systems with the express purpose of collecting credit card data, which can be used to buy things or sold to criminals who want to use the data to steal from stores or individuals.

A cracker is someone who breaks a code, such as a user password or an encryption scheme.

A security researcher is anyone who seeks out vulnerabilities in computer systems, for good or evil purposes.

There are probably several terms I'm forgetting here, but these are the main ones I run across every day. As near as I can figure, only two of these terms always apply to ethical people: "hacker," a word whose true meaning (and ethical code) is frequently overlooked by the general public; and "white hat." Only one of these terms always applies to a bad person: "carder," who is virtually always dealing with stolen data.

Black hats, attackers, crackers, gray hats, and security researchers can swing either way. They could be good people performing research, exploits or attacks to expose vulnerabilities and prove flaws; or they could be criminals looking to expose and exploit vulnerabilities for their own purposes.

In my research for our black hat survey, I was puzzled by some of the results, because while most of the respondents said they attempt to break into computer systems for fun or profit, almost half of them agreed with the statement that "unauthorized access to computer information is never okay." While almost all of those we interviewed had some knowledge of systems penetration, many of them were inconsistent as to whether they should be called "hackers," "black hats," or "white hats."

As an editor who's sensitive to labels and political correctness, I'd like to use the right name when I talk about people who try to break into corporate computer systems. Often, though, I'm not sure whether to call them "attackers," "hackers," or "hey you."

Who can give me some guidance on this? If you've got a thought, please post it to the message board attached to this story. If you haven't used our boards before, you'll have to register, but I promise it's easy and quick. And when you get on there, you can call me "Tim" or "Enchanter" or "Bozo."

Just don't call me late for dinner.

— Tim "Bruce" Wilson, Site Editor, Dark Reading

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
Dark Reading Live EVENTS
INsecurity - For the Defenders of Enterprise Security
A Dark Reading Conference
While red team conferences focus primarily on new vulnerabilities and security researchers, INsecurity puts security execution, protection, and operations center stage. The primary speakers will be CISOs and leaders in security defense; the blue team will be the focus.
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
[Strategic Security Report] Assessing Cybersecurity Risk
[Strategic Security Report] Assessing Cybersecurity Risk
As cyber attackers become more sophisticated and enterprise defenses become more complex, many enterprises are faced with a complicated question: what is the risk of an IT security breach? This report delivers insight on how today's enterprises evaluate the risks they face. This report also offers a look at security professionals' concerns about a wide variety of threats, including cloud security, mobile security, and the Internet of Things.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.