Module 4
Module 4
• Internal Threat
• Create network accounts for themselves and their friends.
• Access accounts and applications they wouldn’t normally use for their daily jobs.
• E-mail former and prospective employers.
• Conduct furtive instant-messaging chats.
• Visit Web sites that cater to disgruntled employees, such as f’dcompany.com.
• Perform large downloads and file copying.
• Access the network during off hours.
Intrusion Techniques
• Rule-based detection: Involves an attempt to define a set of rules that can be used to
decide that a given behavior is that of an intruder.
Anomaly detection: Rules are developed to detect deviation from previous usage
patterns.
Penetration identification: An expert system approach that searches for suspicious
behavior
Audit Records
• Detection-specific audit records: Generates audit records containing only that information
required by the intrusion detection system. One advantage of such an approach is that it
could be made vendor independent and ported to a variety of systems. The disadvantage is
the extra overhead involved in having, in effect, two accounting packages running on a
machine.
Each audit record contains the following
fields
• Subject: A subject is typically a terminal user but might also be a process acting
on behalf of users or groups of users. All activity arises through commands
issued by subjects. Subjects may be grouped into different access classes.
• Action: Operation performed by the subject on or with an object; for example,
login, read, perform I/O, execute.
• Object: Examples include files, programs, messages, records, terminals, printers,
and user- or program-created structures. When a subject is the recipient of an
action, such as electronic mail, then that subject is considered an object.
Example, database actions may be audited for the database as a whole or at the
record level.
• Exception-Condition: Denotes which, if any, exception condition is raised on
return.
• Resource-Usage: Amount used of some resource (e.g., number of lines printed
or displayed, number of records read or written, processor time, I/O units used,
session elapsed time).
Examples of metrics that are useful for profile-based intrusion detection
• Dormant phase: The virus is idle. The virus will eventually be activated by some event, such
as a date, the presence of another program or file, or the capacity of the disk exceeding some
limit. Not all viruses have this stage.
• Propagation phase: The virus places a copy of itself into other programs or into certain
system areas on the disk. The copy may not be identical to the propagating version; viruses
often morph to evade detection. Each infected program will now contain a clone of the virus,
which will itself enter a propagation phase.
• Triggering phase: The virus is activated to perform the function for which it was intended. As
with the dormant phase, the triggering phase can be caused by a variety of system events,
including a count of the number of times that this copy of the virus has made copies of itself.
• Execution phase: The function is performed. The function may be harmless, such as a
message on the screen, or damaging, such as the destruction of programs and data files
VIRUS STRUCTURE
• Identification: Once detection has been achieved, identify the specific virus
that has infected a program.
• Removal: Once the specific virus has been identified, remove all traces of the
virus from the infected program and restore it to its original state. Remove
the virus from all infected systems so that the virus cannot spread further.
Four generations of antivirus software
• Virus signature scanner: A module that scans the target code looking
for known virus signatures.