Ethics in Information Technology, Second Edition: Computer and Internet Crime
Ethics in Information Technology, Second Edition: Computer and Internet Crime
Ethics in Information Technology, Second Edition: Computer and Internet Crime
Chapter 3
Computer and Internet Crime
Objectives
• What key trade-offs and ethical issues are
associated with the safeguarding of data and
information systems?
Viruses
Computer virus has become an umbrella term for many types of
malicious code. Technically, a virus is a piece of programming code,
usually disguised as something else, that causes a computer to behave in
an unexpected and usually undesirable manner. Often a virus is attached
to a file, so that when the infected file is opened, the virus executes.
Other viruses sit in a computer’s memory and infect files as the
computer opens, modifies, or creates them. Most viruses deliver a
“payload,” or malicious software that causes the computer to perform in
an unexpected way. For example, the virus may be programmed to
display a certain message on the computer’s display screen, delete or
modify a certain document, or reformat the hard drive. A true virus does
not spread itself from computer to computer. A virus is spread to other
machines when a computer user opens an infected e-mail attachment,
downloads an infected program, or visits infected Web sites. In other
words, it takes action by the “infected” computer user to spread a
virus. Macro viruses have become a common and easily created form
of virus. Attackers use an application macro language (such as Visual
Basic or VBScript) to create programs that infect documents and
templates. After an infected document is opened, the virus is executed
and infects the user’s application templates. Macros can insert
unwanted words, numbers, or phrases into documents or alter
command functions. After a macro virus infects a user’s application, it
can embed itself in all future documents created with the application.
Worms
Trojan Horses
A Trojan horse is a program in which malicious code is hidden inside a
seemingly harmless program. The program’s harmful payload can
enable the hacker to destroy hard drives, corrupt files, control the
computer remotely, launch attacks against other computers, steal
passwords or Social Security numbers, and spy on users by recording
keystrokes and transmitting them to a server operated by a third party.
A Trojan horse can be delivered as an e-mail attachment, downloaded
from a Web site, or contracted via a removable media device such as a
CD/DVD or USB memory stick. Once an unsuspecting user executes
the program that hosts the Trojan horse, the malicious payload is
automatically launched as well—with no telltale signs. Common host
programs include screen savers, greeting card systems, and games.
Another type of Trojan horse is a logic bomb, which executes when it
is triggered by a specific event. For example, logic bombs can be
triggered by a change in a particular file, by typing a specific series of
keystrokes, or by a specific time or date.
Often it is necessary to act quickly to contain an attack and to keep a bad situation from
becoming even worse. The response plan should clearly define the process for deciding
if man attack is dangerous enough to warrant shutting down or disconnecting critical
systems from the network. How such decisions are made, how fast they are made, and
who makes them are all elements of an effective response plan.
Eradication
Before the IT security group begins the eradication effort, it must collect and log all
possible criminal evidence from the system, and then verify that all necessary backups
are current, complete, and free of any virus. Creating a forensic disk image of each
compromised system on write-only media both for later study and as evidence can be
very useful. After virus eradication, the group must create a new backup. Throughout
this process, a log should be kept of all actions taken. This will prove helpful during the
follow-up phase and ensure that the problem does not recur. It is imperative to back up
critical applications and data regularly. Many organizations, however, have
implemented inadequate backup processes and found that they could not fully restore
original data after a security incident. All backups should be created with enough
frequency to enable a full and quick restoration of data if an attack destroys the
This process should be tested to confirm that it works.
Incident Follow-Up
Of course, an essential part of follow-up is to determine how the organization’s
security was compromised so that it does not happen again. Often the fix is as
simple as getting a software patch from a product vendor. However, it is important
to look deeper than the immediate fix to discover why the incident occurred. If a
simple software fix could have prevented the incident, then why wasn’t the fix
installed before the incident occurred? A review should be conducted after an
incident to determine exactly what happened and to evaluate how the organization
responded. One approach is to write a formal incident report that includes a detailed
chronology of events and the impact of the incident. This report should identify any
mistakes so that they are not repeated in the future. The experience from this
incident should be used to update and revise the security incident
response plan. Creating a detailed chronology of all events will also document the
incident for later prosecution. To this end, it is critical to develop an estimate of the
monetary damage. Potential costs include loss of revenue, loss in productivity, and
the salaries of people working to address the incident, along with the cost to replace
data, software, and hardware.
Summary
• Ethical decisions regarding IT security include
determining which information systems and data
most need protection
• 65-fold increase in the number of reported IT
security incidents from 1997 to 2003
• Most incidents involve a:
– Virus
– Worm
– Trojan horse
– Denial-of-service
Summary (continued)
• Perpetrators include:
– Hackers
– Crackers
– Industrial spies
– Cybercriminals
– Cyberterrorists
Summary (continued)
• Key elements of a multilayer process for managing
security vulnerabilities include:
– Assessment
– User education
– Response plan