Threats and Attacks
Threats and Attacks
THREATS
&
ATTACKS
Chapter 2
The Need for Security
Threats vs Attacks
• Threats represent potential risks that could exploit vulnerabilities in a
system. These risks can come from various sources such as malicious
actors, internal mistakes, or natural disasters.
• Attacks are the actual exploitation of these threats, where someone
actively tries to compromise, damage, or gain unauthorized access to a
system or data.
• Example:
• Threat: A known software vulnerability that allows unauthorized access.
• Attack: A hacker uses this vulnerability to breach the system and steal sensitive
data.
• In summary,
• Threat is the potential for harm.
• Attack is the execution of that potential harm when a vulnerability is exploited.
2
Introduction
7
Business Needs First
8
Protecting the Functionality of an
Organization
• Management (general and IT) responsible for implementation
• Information security is both management issue and people issue
• Organization should address information security in terms of
business impact and cost
9
Enabling the Safe Operation of Applications
10
Protecting Data that Organizations Collect
and Use
• Organization, without data, loses its record of transactions and/or
ability to deliver value to customers
• Protecting data in motion and data at rest are both critical aspects of
information security
11
Safeguarding Technology Assets in
Organizations
• Organizations must have secure infrastructure services based on size
and scope of enterprise
• Additional security services may be needed as organization grows
• More robust solutions may be needed to replace security programs
the organization has outgrown
12
Figure 2-1 World Internet usage3
13
THREATS
15
Threats
Threat: an object, person, or other entity that represents a
constant danger to an asset
17
Table 2-1 Threats to Information Security4
18
Threats…
Deepfake Technology
• Description: Deepfake technology creates realistic but fake video,
audio, or images, often used to impersonate individuals or create
misleading content.
• Why it's dangerous: Deepfakes can be used to manipulate public
perception, impersonate individuals for fraud, or disrupt political
processes. They are particularly challenging to detect.
• Example: Deepfake scams involving impersonating CEOs to trick
employees into transferring money.
Cloud Security Threats
• Threat: The risk that sensitive data or services hosted on cloud
platforms could be compromised due to misconfiguration, poor
access controls, or API vulnerabilities.
• Why it's dangerous: As more businesses rely on cloud services,
improper security measures can expose vast amounts of data or
critical services to potential breaches.
19
Compromises to Intellectual Property
22
Deviations in Quality of Service
• Power irregularities
• Commonplace
• Organizations with inadequately conditioned power are susceptible
• Controls can be applied to manage power quality
• Fluctuations (short or prolonged)
• Excesses (spikes or surges) – voltage increase
• Shortages (sags or brownouts) – low voltage
• Losses (faults or blackouts) – loss of power
25
Espionage or Trespass
26
Figure 2-5 Shoulder Surfing
27
Figure 2-6 Hacker Profiles
28
Espionage or Trespass (cont’d.)
Expert hacker
Unskilled hacker
30
Includes acts
performed without Inexperience
malicious intent
Human
Error or Causes include: Improper training
Failure
Employees are among
the greatest threats to Incorrect assumptions
an organization’s data
31
Revelation of classified
data
Entry of erroneous
data
Human
Error or Employee mistakes
Accidental data
deletion or
can easily lead to:
Failure modification
Failure to protect
information
32
Figure 2-8 Acts of Human Error or Failure
33
Information Extortion
34
35
39
Antiquated/outdated
infrastructure can lead to
unreliable, untrustworthy
systems
40
ATTACKS
41
Attacks
• Attacks
• Acts or actions that exploits
vulnerability (i.e., an identified
weakness) in controlled system
• Accomplished by threat agent that
damages or steals organization’s
information
42
Listing of attacks
43
Passive Attacks
52
Attacks Conti…
Credential Stuffing
• Description: Attackers use stolen credentials (from past data breaches) to
gain unauthorized access to user accounts across multiple services.
• Why it’s dangerous: Many people reuse passwords, so once one account is
compromised, attackers can gain access to others, including corporate
systems.
• Recent examples: Credential stuffing attacks on retail and financial services
have increased as stolen credentials are sold on the dark web.
IoT Attacks
• Description: Internet of Things (IoT) devices, such as smart home systems,
medical devices, and industrial control systems, are increasingly targeted
due to weak security configurations.
• Why it’s dangerous: These devices often have poor security, and if
compromised, they can give attackers access to sensitive data or even critical
infrastructure.
• Recent examples: The Mirai botnet hijacked IoT devices for large-scale DDoS
attacks, and medical devices have been targeted in healthcare facilities.
53
Attacks Conti…
Cryptojacking
• Description: Attackers hijack systems to mine cryptocurrency using
unauthorized resources, leading to performance degradation and higher
operational costs.
• Why it's dangerous: Cryptojacking often goes unnoticed for long periods,
draining resources, reducing system performance, and increasing
electricity costs.
• Example: Infected websites or software that use the computing power of
visitors’ devices to mine cryptocurrencies like Bitcoin.
Business Email Compromise (BEC)
• Description: Attackers impersonate senior executives or vendors and manipulate employees
into wiring funds or sharing sensitive data.
• Why it's dangerous: BEC scams are highly targeted and often result in significant financial
losses, with little chance of recovery once funds are transferred.
• Example: Fraudulent emails convincing employees to transfer money to attacker-controlled
accounts, leading to millions in losses for businesses.
54
Attacks Conti…
SQL Injection
• Malicious SQL queries inserted into input fields to manipulate or access databases.
• Example: An attacker enters ' OR '1'='1' -- into a login form, bypassing authentication and
gaining unauthorized access to user accounts.
Cross-Site Scripting (XSS)
• Injects malicious scripts into websites, which execute on users’ browsers.
• Example: A user posts <script>alert('You have been hacked!');</script> in a forum comment,
causing every visitor to see the alert when viewing that comment.
Session Hijacking
• Taking over a user’s session to impersonate them without needing login credentials.
• Example: In a public Wi-Fi network, an attacker uses Firesheep to intercept session cookies,
allowing them to log in as the victim on a website.
Malvertising
• Malicious ads that distribute malware or redirect users to malicious sites.
• Example: An infected advertisement on a legitimate website redirects users to a site hosting
ransomware, infecting their device without any user interaction.
55
Attacks Conti…
• Malicious code: includes execution of viruses, worms,
Trojan horses, and active Web scripts with intent to
destroy or steal information
• Hoaxes: transmission of a virus hoax with a real virus attached;
more devious form of attack
• Back door: gaining access to system or network using
known or previously unknown/newly discovered access
mechanism
• Password crack: attempting to reverse calculate a
password
• Brute Force: trying every possible combination of
options of a password
• Dictionary: selects specific accounts to attack and uses
commonly used passwords (i.e., the dictionary) to guide
guesses
56
New Table
57
Attacks (cont’d.)
58
Figure 2-11 Denial-of-Service Attacks
59
Attacks (cont’d.)
60
Figure 2-12 IP Spoofing
61
Figure 2-13 Man-in-the-Middle Attack
62
Attacks (cont’d.)
64
\
65
Reading task (Optional)
1. HACK PCWEEK TOPOLOGY
2. Nigerian Fraud Example @ Advance-Fee Fraud (AFF),
(Course Book)
3. Secure Software Development
67
Supplementary
68
Secure Software Development
69
Software Assurance and the SA Common
Body of Knowledge
• National effort underway to create common body of knowledge
focused on secure software development
• US Department of Defense and Department of Homeland Security
supported Software Assurance Initiative, which resulted in
publication of Secure Software Assurance (SwA) Common Body of
Knowledge (CBK)
• SwA CBK serves as a strongly recommended guide to developing
more secure applications
70
Software Design Principles
71
Software Design Principles (cont’d.)
72
Software Development Security Problems
73
Software Development Security Problems
(cont’d.)
• Problem areas in software development (cont’d.):
• Format string problems
• Neglecting change control
• Improper file access
• Improper use of SSL
• Information leakage
• Integer bugs (overflows/underflows)
• Race conditions
• SQL injection
74
Software Development Security Problems
(cont’d.)
• Problem areas in software development (cont’d.):
• Trusting network address resolution
• Unauthenticated key exchange
• Use of magic URLs and hidden forms
• Use of weak password-based systems
• Poor usability
75
Summary
76
Summary (cont’d.)
77