Explain Attacks, Threats, and Vulnerabilities Flashcards

Lesson 16A (41 cards)

1
Q
A

Relationship between vulnerability, threat, and risk.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
A

Example of a phishing email. On the right, you can see the message in its true form as the mail client has stripped out the formatting (shown on the left) designed to disguise the nature of the links. (Screenshot courtesy of CompTIA.)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q
A

Using a command & control (C&C) network to operate a botnet of compromised hosts and
coordinate a DDoS attack.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
A

If authentication credentials are transmitted in cleartext, such as the unencrypted version of the
IMAP mailbox access protocol, it is a simple matter for the credentials to be intercepted via packet
sniffing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q
A

Hashcat password cracking utility. This example uses a mask to speed up a brute force attack. The attacker can use a mask by learning or guessing likely facts about how the target chooses a password, such as its length and likelihood of being a variation on a simple word or phrase.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Information security ensures

A

confidentiality, integrity, and availability (CIA) of data, while cybersecurity protects systems from attacks; security assessments evaluate vulnerabilities, threats, and risks to strengthen defenses.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

vulnerability

A

is a weakness in a system that a threat actor could exploit, arising from issues like misconfigurations, outdated patches, untested updates, protocol misuse, poor network design, weak physical security, insecure passwords, and software flaws such as unchecked user input.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Non-compliant systems

A

configuration baseline defines best practices hardening a system to minimize vulnerabilities by reducing its attack surface—the entry points a threat actor could exploit. Non-compliant systems have deviated from this baseline, and vulnerability scanners help detect them.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

unprotected system

A

lacks or has misconfigured technical security controls like antivirus scanners, firewalls, or intrusion detection systems, increasing its attack surface and exposing more vulnerabilities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

software vulnerability

A

is a flaw that can be exploited to bypass security or crash an application, potentially allowing attackers to install malware.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

zero-day vulnerability

A

is exploited before a fix is available, leaving systems exposed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

exploit

A

is malicious code that uses a vulnerability to compromise a system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

unpatched systems

A

While zero-day exploits are rare but dangerous, a greater risk comes from unpatched systems, which lack critical OS and application updates, and end-of-life (EOL) systems, where vendors no longer provide support or security fixes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

BYOD (Bring Your Own Device)

A

allows employees to use personal mobile devices for corporate access but complicates security by making it harder to enforce standardized configurations and compliance, ultimately expanding the network attack surface.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Social engineering

A

is a tactic where threat actors manipulate people into revealing confidential information or granting unauthorized access, often by persuasion or intimidation. Preventing these attacks requires awareness of common social engineering techniques.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Impersonation

A

is a social engineering tactic where an attacker creates a pretext scenario to engage with an employee, often pretending to be IT support to persuade them into revealing sensitive information, such as passwords, through trust-building, intimidation, or hoaxes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Dumpster diving

A

is a technique where attackers search discarded documents or media to collect sensitive information that strengthens social engineering attacks, making impersonation attempts more credible.

18
Q

Shoulder surfing

A

is a social engineering attack where a threat actor observes a user entering secure information like a password or PIN, either in person or remotely using binoculars, CCTV, or other surveillance methods.

19
Q

Tailgating

A

occurs when an attacker follows closely behind someone authorized to enter a secure area,

20
Q

piggybacking

A

involves gaining access with an employee’s permission, often using impersonation or deception, such as pretending to be a cleaning crew member or claiming to have forgotten a badge.

21
Q

Phishing

A

is a social engineering attack where threat actors send spoofed emails or messages to trick users into performing actions like installing malware or giving remote access. Some phishing campaigns use fake websites mimicking legitimate ones to capture login credentials.

22
Q

Phishing Variants include:

A

spear phishing (targeted attacks using personal details), whaling (focused on high-level executives), and vishing (voice-based scams). An evil twin attack operates similarly but uses a rogue wireless access point with a deceptive SSID or spoofed captive portal to steal user authentication data.

23
Q

threats

A

Early cybersecurity relied on detecting static threats like computer viruses through signature-based scanning, but adversaries developed techniques to evade detection. Modern security emphasizes behavioral analysis, assessing threat actors’ location, intent, and capability to counter evolving attacks.

24
Q

External threat actors

A

External threat actors lack authorized access and rely on malware or social engineering

25
**insider threats**
—including **employees, contractors, or partners**—can be **malicious (data theft) or unintentional (misconfigurations increasing risk)**.
26
**Footprinting**
is an **information-gathering threat** where attackers **research a target’s network and security systems**, using **public data, network scans, and social engineering** to identify **vulnerabilities and exploitation methods**.
27
**Spoofing threats**
involve attackers **masquerading as trusted users or systems**, using techniques like **cloning MAC/IP addresses, falsifying digital certificates, sending fake emails, or social engineering**. Some spoofing methods involve **stealing authentication tokens**, such as **web cookies**, to impersonate users, which is also known as a **replay attack**.
28
**on-path attack**
is a type of **spoofing** where a **threat actor covertly intercepts network traffic** between two hosts, allowing them to **read or modify packets**, often aiming to **recover password hashes**—an **evil twin attack** is one example.
29
**Denial of Service (DoS) attack**
overwhelms a service with **spoofed requests** or exploits **software vulnerabilities**, causing it to **fail or become unavailable**. Some DoS attacks are **physical** (e.g., cutting power or network cables), while others are used to **distract security teams**, masking **data theft or other malicious activities**.
30
**Distributed Denial of Service (DDoS) attack**
overwhelms a server with **bogus requests** from multiple **compromised devices**—a **botnet**—controlled remotely by a **command & control (C&C) system**, often infected via **automated exploits or phishing**.
31
**Password attacks**
**Password attacks** involve **stealing credentials** through **malware, sniffing, or stealing password hashes**, with attackers using **dictionary-based or brute-force cracking** to recover passwords.
32
**Cross-site scripting (XSS) attacks**
exploit **input validation vulnerabilities** in web applications, allowing **threat actors to inject malicious scripts** into **server-side or client-side code**, potentially compromising **user data or system integrity**.
33
**SQL injection attacks**
exploit **web applications** that fail to **properly validate user input**, allowing attackers to **modify SQL queries**, potentially extracting or inserting data, or executing **arbitrary code** with the database’s privileges. For example, an attacker can manipulate input fields to trick an application into executing unintended **SQL commands**, granting unauthorized access to sensitive information.
34
**Encryption technologies**
enable secure communication by making **data unreadable** unless the recipient has the **correct key**. This ensures **privacy**, even over **public networks** like the Internet.
35
The three primary cryptographic methods are
**symmetric encryption, asymmetric encryption, and cryptographic hashing**
36
**Cryptographic hashes**
generate a **fixed-length representation of data** using a **one-way function**, making it **irreversible**. They are commonly used for **secure storage**, such as **passwords**, where retrieval of the original value is unnecessary. Key algorithms include **SHA (Secure Hash Algorithm)** and **MD5**, though MD5 is becoming obsolete.
37
**Symmetric encryption**
uses a **single secret key** for both **encryption and decryption**, making **key security critical**—if compromised, the system is vulnerable. While **key distribution is a challenge**, symmetric encryption is **fast and efficient**, with ciphers like **AES** enabling **bulk data encryption**.
38
**Asymmetric encryption**
uses a **key pair**—a **private key and a public key**—that are **mathematically linked**. One key **encrypts**, and only the paired key **decrypts**, ensuring **secure communication**. The **public key** can be freely shared, while the **private key** must be kept **secret**, as it **cannot be derived** from the public key.
39
**Digital signatures and key exchange**
combine **cryptographic hashes, asymmetric encryption, and symmetric encryption** to enhance **confidentiality, integrity, and availability**. Because **asymmetric encryption** limits message size, it is often paired with **hashing and symmetric encryption** in **security protocols**.
40
**Digital signatures**
ensure the integrity and authenticity of a message or digital certificate. The sender **creates a cryptographic hash**, encrypts it with their **private key**, and attaches it to the message. The recipient **decrypts the signature** using the sender’s **public key**, then **recalculates the hash** to verify the message remains unchanged.
41
**Key exchange**
securely shares a **symmetric encryption key** between hosts, with **asymmetric encryption** used to **encrypt and exchange** the key. The **session key**, which may be **ephemeral**, protects actual data exchange efficiently.