CompTIA Sec+ SY0-701 Cyber Attacks Flashcards

1
Q

Ransomware:

Description: Ransomware encrypts files or locks users out of their systems, demanding payment (usually in cryptocurrency) for decryption or access restoration.

Scenario: A user downloads a file from an email attachment that appears to be a legitimate invoice. Unbeknownst to them, the attachment contains ransomware, which quickly encrypts files across their system, demanding payment for decryption keys.
A

Preventive Measures: Employ email and web filtering solutions to block malicious attachments and links, keep systems and software updated with security patches, and regularly back up critical data offline.

Remedial Measures: Isolate infected systems from the network to prevent further spread, restore data from backups, and use reputable ransomware decryption tools if available.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Trojan Horse:

Description: Trojans masquerade as legitimate software or files to deceive users into executing them, allowing attackers to gain unauthorized access, steal data, or install additional malware.

Scenario: A user downloads a seemingly innocuous software update from a third-party website, unaware that it contains a Trojan horse designed to steal sensitive login credentials stored on their system.
A

Preventive Measures: Exercise caution when downloading files or software from untrusted sources, use reputable antivirus software to scan for and remove Trojans, and implement least privilege access controls.

Remedial Measures: Quarantine infected systems, scan for and remove Trojan files and associated artifacts, and conduct thorough security assessments to identify potential entry points.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Spyware:

Description: Spyware secretly monitors users' activities, collects personal information, and relays it to third parties without consent, compromising privacy and security.

Scenario: A user unknowingly installs a free software application bundled with spyware onto their device. The spyware tracks their web browsing habits, captures login credentials, and sends the data to a remote server controlled by attackers.
A

Preventive Measures: Install reputable anti-spyware software to detect and remove spyware, avoid clicking on suspicious links or pop-up ads, and regularly review app permissions on devices.

Remedial Measures: Use anti-spyware tools to scan and remove malicious software, reset compromised account credentials, and educate users on safe internet browsing practices.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Worms:

Description: Worms are self-replicating malware that spread across networks by exploiting vulnerabilities, consuming system resources, and often carrying payloads for further malicious activities.

Scenario: A vulnerable server connected to a corporate network is infected with a worm that exploits a known software vulnerability. The worm rapidly propagates across the network, disrupting services and
A

Preventive Measures: Keep systems and software updated with security patches, segment network traffic to contain potential worm outbreaks, and deploy intrusion detection systems (IDS) to monitor for suspicious behavior.

Remedial Measures: Isolate infected systems from the network, apply security patches to vulnerable systems, and use antivirus software to detect and remove worm components.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Adware:

Description: Adware displays unwanted advertisements, pop-ups, or redirects on users' devices, often disrupting user experience and compromising system performance.

Scenario: A user downloads a free game application from an unofficial app store. Unbeknownst to them, the application contains adware that bombards the device with intrusive advertisements, slowing down system performance.
A

Preventive Measures: Install reputable ad-blocking extensions or software, be cautious when downloading free software from the internet, and regularly update antivirus software to detect and remove adware.

Remedial Measures: Use adware removal tools to scan and remove malicious software, reset browser settings to default, and educate users on avoiding potentially unwanted programs (PUPs).
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Rootkits:

Description: Rootkits are stealthy malware that conceals malicious processes or files within the operating system, enabling unauthorized access, data theft, and system manipulation.

Scenario: An attacker exploits a known vulnerability to install a rootkit on a server hosting critical business applications. The rootkit conceals its presence, allowing the attacker to maintain persistent access and exfiltrate sensitive data without detection.
A

Preventive Measures: Regularly update system firmware and security patches, use secure boot processes to prevent unauthorized modifications, and implement intrusion detection systems (IDS) to detect rootkit activity.

Remedial Measures: Employ rootkit detection and removal tools to scan for and eliminate malicious software, perform system re-imaging from a known good backup, and monitor for signs of system compromise.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Botnets:

Description: Botnets are networks of compromised devices, or "bots," controlled by attackers to carry out malicious activities such as distributed denial-of-service (DDoS) attacks, spam email campaigns, and information theft.

Scenario: A group of internet-connected IoT devices, including smart cameras and routers, is infected with botnet malware. The devices are remotely controlled by attackers to launch a coordinated DDoS attack against a targeted website, causing service disruption.
A

Preventive Measures: Implement network segmentation to limit the spread of botnet infections, deploy intrusion prevention systems (IPS) to block malicious traffic, and use strong, unique passwords for device authentication.

Remedial Measures: Disconnect infected devices from the network, perform malware scans to identify and remove botnet components, and collaborate with internet service providers (ISPs) to mitigate botnet activity.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Cryptojacking:

Description: Cryptojacking involves using malware to hijack computing resources, such as CPU and GPU cycles, to mine cryptocurrency without the user's consent or knowledge.

Scenario: A user visits a compromised website that secretly runs JavaScript code in the background, exploiting the device's processing power to mine cryptocurrency without the user's permission, causing system slowdowns.
A

Preventive Measures: Employ browser extensions or software to block cryptojacking scripts, monitor system performance for signs of unusual resource consumption, and educate users on the risks of visiting untrusted websites.

Remedial Measures: Use antivirus software to detect and remove cryptojacking malware, close browser tabs or processes consuming excessive resources, and update security patches to address known vulnerabilities.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Fileless Malware:

Description: Fileless malware resides in memory or uses legitimate system processes to execute malicious commands, making it difficult to detect using traditional antivirus solutions and bypassing file-based security measures.

Scenario: An unsuspecting user clicks on a malicious link in a phishing email, triggering the execution of fileless malware that exploits a vulnerability in the web browser. The malware executes in memory, evading detection by traditional antivirus software and stealing sensitive information.
A

Preventive Measures: Deploy endpoint detection and response (EDR) solutions to monitor for suspicious behavior, restrict administrative privileges to reduce attack surface, and conduct regular security assessments to identify vulnerabilities.

Remedial Measures: Analyze memory dumps and system logs for signs of fileless malware activity, implement application whitelisting to prevent unauthorized code execution, and educate users on recognizing phishing attempts.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Mobile Malware:

Description: Mobile malware targets smartphones and tablets, compromising device security, stealing sensitive information, and performing unauthorized activities such as premium SMS fraud or banking credential theft.

Scenario: A user downloads a seemingly harmless mobile game from a third-party app store. Unbeknownst to them, the game contains malware that exploits device vulnerabilities to steal personal information and send premium-rate SMS messages.
A

Preventive Measures: Download apps only from official app stores, keep operating systems and applications updated with the latest security patches, and use mobile security software to scan for and remove malware.

Remedial Measures: Reset compromised devices to factory settings to remove malware, install security updates to patch vulnerabilities, and enable remote wipe features to protect sensitive data in case of loss or theft.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Scareware:

Description: Scareware is malicious software that masquerades as legitimate security software, often displaying alarming messages or pop-ups to trick users into purchasing fake security solutions or providing personal information.

Scenario: A user encounters a pop-up message claiming their computer is infected with viruses and prompts them to download a fake antivirus program. Believing the message to be genuine, the user installs the scareware, which further compromises their system.
A

Preventive Measures: Educate users about the tactics used by scareware, use reputable antivirus software to detect and block scareware, and avoid clicking on suspicious pop-up messages or advertisements.

Remedial Measures: Remove scareware programs using reputable antivirus or anti-malware tools, reset browser settings to default to remove malicious extensions, and review recent software installations for potentially unwanted programs.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Backdoors:

Description: Backdoors are hidden entry points in software or systems that allow unauthorized access to the system, bypassing normal authentication mechanisms. They are often used by attackers to maintain persistent access to compromised systems.

Scenario: An attacker exploits a known vulnerability in a web server to install a backdoor that allows remote access to the system. The backdoor enables the attacker to upload and execute malicious code, steal sensitive data, and manipulate system settings.
A

Preventive Measures: Regularly update software and firmware with security patches, use strong encryption for network communication, and implement intrusion detection systems (IDS) to detect and block backdoor activity.

Remedial Measures: Close the backdoor by removing or patching the vulnerability, conduct a thorough security audit to identify potential backdoors, and implement access controls to prevent unauthorized system access.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Exploit Kits:

Description: Exploit kits are prepackaged bundles of malicious code designed to automate the exploitation of vulnerabilities in software, web browsers, and plugins. They are often distributed through compromised websites or malicious links.

Scenario: A user visits a compromised website hosting an exploit kit. The kit scans the user's system for known vulnerabilities and delivers a payload tailored to exploit the detected weaknesses, leading to the installation of malware or remote access tools.
A

Preventive Measures: Keep software and plugins up-to-date with security patches, use web application firewalls (WAFs) to block exploit kit traffic, and regularly scan websites for vulnerabilities using security tools.

Remedial Measures: Apply security patches to vulnerable systems, remove malicious code injected by exploit kits, and implement network monitoring to detect and block exploit kit activity.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Email Phishing Attacks:

Description: Email phishing involves sending fraudulent emails that appear to be from legitimate sources, such as banks, social media platforms, or government agencies, with the intention of tricking recipients into revealing sensitive information or clicking on malicious links.

Scenario: An employee receives an email purportedly from their company's IT department, requesting them to reset their account password by clicking on a link provided in the email. The link leads to a phishing website designed to steal the user's login credentials.
A

Prevention/Remediation:
Educate users about the characteristics of phishing emails, such as generic greetings, urgent language, and suspicious sender addresses.
Implement email filtering solutions to detect and block phishing emails before they reach users’ inboxes.
Encourage users to verify the authenticity of emails by contacting the purported sender through official channels.

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

Spear Phishing Attacks:

Description: Spear phishing attacks are targeted phishing campaigns that tailor messages to specific individuals or organizations, often using personal information obtained from social media or other sources to increase credibility.

Scenario: A senior executive receives an email purportedly from a trusted business partner, requesting urgent payment for an invoice. The email contains accurate details about the company's ongoing projects, making it appear legitimate. However, the request is fraudulent, and the payment would go to the attacker's account.
A

Prevention/Remediation:
Implement strict access controls to limit the exposure of personal and organizational information.
Train employees to be cautious about sharing personal information online and to recognize suspicious requests for sensitive data.
Utilize email authentication protocols such as SPF, DKIM, and DMARC to verify the authenticity of email senders.

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

Vishing (Voice Phishing) Attacks:

Description: Vishing attacks involve using voice communication, such as phone calls or voicemail messages, to trick individuals into divulging sensitive information or performing specific actions.

Scenario: A user receives a phone call from someone claiming to be from their bank's fraud department, informing them of suspicious activity on their account. The caller asks the user to verify their account details, including their account number and PIN, to resolve the issue. Unaware of the scam, the user provides the requested information, which the attacker then uses to access their bank account.
A

Prevention/Remediation:
Educate employees about the risks of vishing attacks and the importance of verifying the identity of callers before disclosing sensitive information.
Implement caller ID verification systems to help users identify potential vishing calls.
Establish clear procedures for handling requests for sensitive information over the phone, including verifying the legitimacy of the request through known contacts.

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

Smishing (SMS Phishing):

Description: Smishing involves sending deceptive text messages to individuals, typically containing links to malicious websites or instructions to call a fraudulent phone number.

Scenario: A user receives a text message claiming to be from a delivery service, notifying them of a package delivery failure and instructing them to click on a link to reschedule delivery. The link leads to a phishing website designed to steal the user's personal information.
A

Prevention/Remediation:
Enable spam filtering for SMS messages to detect and block suspicious or unsolicited texts.
Educate users about the risks of smishing and advise them to avoid clicking on links or responding to messages from unknown or untrusted sources.
Encourage users to report suspected smishing attempts to the appropriate authorities or IT security team.

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

Whaling Attacks:

Description: Whaling attacks target high-profile individuals within organizations, such as executives or senior managers, with the goal of obtaining sensitive information or gaining unauthorized access to corporate systems.

Scenario: The CEO of a company receives an email purportedly from the company's legal department, requesting urgent access to confidential financial documents for a pending lawsuit. The email contains a malicious attachment that, when opened, installs malware on the CEO's computer.
A

Prevention/Remediation:
Implement strict access controls and least privilege principles to limit the exposure of sensitive information to unauthorized users.
Provide specialized security training and awareness programs tailored to executives and other high-profile targets.
Enable advanced threat protection features such as sandboxing and attachment scanning to detect and block malicious emails targeting senior management.

16
Q

Email Spoofing:

Description: Email spoofing involves forging the sender's email address to impersonate a legitimate user or organization, often used in phishing and malware distribution campaigns.

Scenario: An attacker sends an email to employees posing as the CEO, requesting urgent wire transfers to a fraudulent account. The email appears legitimate, causing employees to unknowingly transfer funds to the attacker.
A

Prevention/Remediation:
Implement technologies such as SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance) to authenticate and validate email senders.
Use email filtering solutions to detect and block spoofed emails based on sender reputation, domain alignment, and other criteria.
Educate users about the importance of verifying email sender identities and avoiding clicking on links or downloading attachments from suspicious or unexpected emails.

16
Q

DNS Spoofing (DNS Cache Poisoning):

Description: DNS spoofing involves corrupting or poisoning the DNS cache to redirect users to malicious websites or servers controlled by the attacker.

Scenario: An attacker manipulates DNS records to redirect users attempting to access a legitimate banking website to a fake site controlled by the attacker, harvesting login credentials and financial information.
A

Prevention/Remediation:
Use DNSSEC (Domain Name System Security Extensions) to cryptographically sign DNS records and verify their authenticity.
Implement DNS caching best practices and regularly update DNS software to mitigate vulnerabilities that could be exploited for cache poisoning.
Monitor DNS traffic for anomalies and employ DNS firewalls or filtering solutions to block requests to known malicious domains.

17
Q

ARP Spoofing (Man-in-the-Middle):

Description: ARP spoofing involves manipulating Address Resolution Protocol (ARP) messages to associate the attacker's MAC address with the IP address of a legitimate device on the network, enabling interception and modification of network traffic.

Scenario: An attacker performs ARP spoofing to intercept and eavesdrop on communications between a client device and a web server, capturing sensitive information such as login credentials and financial data.
A

Prevention/Remediation:
Implement ARP spoofing detection mechanisms such as ARP inspection or dynamic ARP inspection (DAI) on network switches and routers.
Use static ARP entries or ARP cache validation techniques to prevent unauthorized changes to ARP tables.
Encrypt network traffic using protocols such as SSL/TLS to protect data integrity and confidentiality against interception by malicious actors.

18
Q

GPS Spoofing:

Description: GPS spoofing involves manipulating GPS signals to deceive GPS receivers and devices, leading to inaccurate location information or navigation instructions.

Scenario: An attacker broadcasts spoofed GPS signals near a shipping port, causing GPS-guided cargo ships to deviate from their intended routes and potentially leading to collisions or cargo theft.
A

Prevention/Remediation:
Use encrypted and authenticated GPS signals whenever possible to verify the authenticity and integrity of location data.
Implement GPS signal monitoring and anomaly detection systems to detect and mitigate spoofing attacks in real-time.
Employ alternative positioning technologies and backup navigation systems to supplement GPS and reduce reliance on potentially compromised signals.

19
Q

IP Spoofing:

Description: IP spoofing involves forging the source IP address of packets to hide the identity of the sender or to impersonate another system.

Scenario: An attacker spoofs the IP address of a trusted server to launch a distributed denial-of-service (DDoS) attack against a target, flooding it with a high volume of malicious traffic.
A

Prevention/Remediation:
Implement Ingress and Egress filtering at network boundaries to block packets with spoofed source IP addresses.
Deploy cryptographic techniques such as IPsec to authenticate the source of packets and ensure data integrity.
Utilize intrusion detection systems (IDS) to detect and alert on suspicious network traffic patterns indicative of IP spoofing.

20
Q

Credential Stuffing:

Description: Credential stuffing attacks involve using stolen username and password combinations obtained from previous data breaches to gain unauthorized access to other accounts.

Scenario: An attacker obtains a list of username and password pairs from a data breach at one online service and attempts to use the same credentials to gain access to users' accounts on other platforms.
A

Prevention/Remediation:
Encourage users to use unique passwords for each account and avoid using easily guessable passwords.
Implement multi-factor authentication (MFA) to add an extra layer of security beyond passwords.
Monitor for and block suspicious login attempts, such as multiple failed login attempts from different locations in a short period.

21
Q

Man-in-the-Browser (MitB) Attacks:

Description: MitB attacks involve malware installed on a user's browser that intercepts and manipulates communication between the user and websites, allowing attackers to steal sensitive information such as login credentials or financial data.

Scenario: A user unknowingly installs a malicious browser extension that captures their online banking credentials and sends them to an attacker-controlled server, allowing the attacker to access their bank account and make unauthorized transactions.
A

Prevention/Remediation:
Keep web browsers and plugins up to date with the latest security patches and updates.
Use browser security features such as sandboxing and secure browsing modes to minimize the risk of malware infection.
Educate users about the dangers of downloading and installing software from untrusted sources and clicking on suspicious links or pop-ups.

21
Q

Brute Force Attacks:

Description: Brute force attacks involve systematically trying every possible combination of usernames and passwords until the correct one is found, allowing the attacker to gain unauthorized access.

Scenario: An attacker uses automated tools to repeatedly attempt to log in to an online banking portal using various combinations of usernames and passwords until they successfully guess a user's credentials.
A

Prevention/Remediation:
Implement account lockout mechanisms after a certain number of failed login attempts to prevent brute force attacks.
Enforce strong password policies requiring complex passwords that are resistant to brute force attacks.
Use intrusion detection systems (IDS) and intrusion prevention systems (IPS) to monitor and block suspicious login attempts.

22
Q

Pass-the-Hash Attacks:

Description: Pass-the-hash attacks involve capturing hashed passwords from compromised systems and using them to authenticate to other systems within the same network.

Scenario: An attacker gains access to a system administrator's account on a compromised server and extracts the hashed password. They then use this hash to authenticate to other servers within the same network without needing to know the plaintext password.
A

Prevention/Remediation:
Implement strong network segmentation to limit the lateral movement of attackers within the network.
Use modern authentication protocols such as Kerberos that are resistant to pass-the-hash attacks.
Regularly update and patch systems to address vulnerabilities that could be exploited for pass-the-hash attacks.

23
Q

Password Spraying Attacks:

Description: Password spraying attacks involve attempting a few commonly used passwords against a large number of user accounts, aiming to evade account lockout mechanisms and gain unauthorized access.

Scenario: An attacker uses a list of commonly used passwords to attempt login across multiple user accounts in an organization, aiming to find accounts with weak passwords that can be exploited for unauthorized access.
A

Prevention/Remediation:
Enforce account lockout policies and rate-limit login attempts to prevent password spraying attacks.
Educate users about the importance of using strong, unique passwords and encourage the use of password managers to generate and store complex passwords securely.
Monitor for and investigate anomalous login patterns and authentication failures to detect and mitigate password spraying attempts.

24
Q

Keylogging Attacks:

Description: Keylogging attacks involve malware installed on a user's device that records keystrokes, allowing attackers to capture sensitive information such as usernames, passwords, and credit card numbers.

Scenario: An attacker infects a user's computer with keylogging malware through a malicious email attachment. The malware silently records the user's keystrokes, allowing the attacker to capture their login credentials and other sensitive information.
A

Prevention/Remediation:
Use anti-malware software to detect and remove keylogging malware from infected devices.
Implement security measures such as endpoint detection and response (EDR) solutions to monitor for suspicious behavior and prevent unauthorized access.
Educate users about the risks of downloading and installing software from untrusted sources and the importance of keeping their devices and software up to date.

25
Q

Man-in-the-Cloud (MitC) Attacks:

Description: Man-in-the-Cloud attacks involve compromising cloud storage accounts (e.g., Dropbox, Google Drive) by stealing authentication tokens or session cookies, allowing attackers to access and manipulate files stored in the cloud.

Scenario: An attacker gains access to a user's cloud storage account by stealing their session cookie through a compromised session. The attacker then downloads sensitive documents and manipulates files stored in the cloud without the user's knowledge.
A

Prevention/Remediation:
Implement multi-factor authentication (MFA) for cloud storage accounts to add an extra layer of security beyond passwords.
Encrypt sensitive files before uploading them to cloud storage and use encryption keys that are managed and stored securely.
Regularly review access logs and audit activity in cloud storage accounts to detect and respond to unauthorized access attempts.

26
Q

Directory Traversal Attacks:

Description: Directory traversal attacks involve exploiting vulnerabilities in web applications to gain unauthorized access to files and directories stored on the server.

Scenario: An attacker manipulates a URL parameter in a web application to traverse directories and access sensitive configuration files containing database credentials and other confidential information.
A

Prevention/Remediation:
Implement proper input validation and output encoding to prevent attackers from injecting directory traversal sequences into user-controlled input fields.
Use access control mechanisms to restrict users’ access to sensitive files and directories based on their privileges and roles.
Regularly audit and review file and directory permissions to identify and remediate misconfigurations that could be exploited for directory traversal attacks.

27
Q

Kerberoasting:

Description:
Kerberoasting is a method used by attackers to exploit weak or poorly configured service accounts in Active Directory environments. It involves extracting encrypted Kerberos tickets for service accounts with weak passwords and offline brute-forcing to crack the passwords and gain unauthorized access to sensitive resources.

Scenario:
An attacker gains access to a compromised workstation within an organization’s network. Using various reconnaissance techniques, they identify service accounts with weak or poorly configured passwords. The attacker then extracts Kerberos tickets associated with these service accounts using tools like Rubeus or Mimikatz. With the stolen tickets, they proceed to perform offline brute-force attacks to crack the passwords. Once successful, the attacker can use the compromised service accounts to access sensitive resources and escalate privileges within the network.

A

Prevention/Remediation Measures:

Use Strong Passwords:
Ensure that service accounts have strong, complex passwords that are resistant to brute-force attacks.

Regularly Rotate Passwords:
Implement a password rotation policy for service accounts to reduce the exposure window in case of compromise.

Implement Account Lockout Policies:
Configure account lockout policies to lock out service accounts after a certain number of failed authentication attempts, thereby mitigating brute-force attacks.

Monitor Kerberos Traffic:
Use security monitoring tools to detect and alert on suspicious Kerberos ticket requests, especially those targeting service accounts.

Use Managed Service Accounts (MSAs) or Group Managed Service Accounts (gMSAs):
Consider using MSAs or gMSAs, which are designed specifically for services running on Windows, as they automatically manage password changes and enhance security.

Implement Credential Guard:
Utilize Credential Guard, a security feature in Windows, to protect Kerberos tickets and prevent attackers from extracting them for offline brute-forcing.
28
Q

Man-in-the-Middle (MitM) Attack:

Description:
A Man-in-the-Middle (MitM) attack is a form of cyber attack where an attacker intercepts and potentially alters communication between two parties who believe they are communicating directly with each other. In a MitM attack, the attacker secretly relays and possibly modifies the communication between the two parties, allowing them to eavesdrop on sensitive information, steal data, or inject malicious content.

Scenario:
Bob is trying to log in to his online banking account using his laptop at a coffee shop with free Wi-Fi. An attacker, Eve, is also connected to the same Wi-Fi network and secretly intercepts the communication between Bob’s laptop and the bank’s server. When Bob enters his login credentials, Eve captures the information before it reaches the bank’s server. Eve can now use Bob’s credentials to log in to his bank account and perform unauthorized transactions.

A

Prevention/Remediation Measures:

Encryption: Implement end-to-end encryption using secure communication protocols such as SSL/TLS (HTTPS) to encrypt data transmitted between client and server, making it difficult for attackers to intercept and decipher the communication.

Digital Certificates: Use digital certificates to verify the authenticity of websites and ensure that communication channels are secure and not tampered with by attackers.

Public Key Infrastructure (PKI): Implement PKI to manage digital certificates, issue trusted certificates, and establish secure communication channels between parties.

Network Segmentation: Employ network segmentation to isolate sensitive systems and data from untrusted networks, reducing the attack surface and limiting the impact of MitM attacks.

Security Awareness: Educate users and employees about the risks of MitM attacks and advise them to avoid connecting to unsecured networks or accessing sensitive information over unencrypted channels.
29
Q

Silver Ticket Attack:

	In a Silver Ticket attack, the attacker obtains the service account's NTLM hash (usually from memory or a compromised system) and uses it to generate a forged Ticket Granting Ticket (TGT) for a specific service, granting unauthorized access to that service without needing the account's actual password.
The attacker crafts the TGT with the service's Service Principal Name (SPN) and the forged NTLM hash, allowing them to authenticate to the service using the compromised ticket.
	
	Scenario: An attacker gains access to a domain controller using a combination of social engineering and malware. Once inside, the attacker extracts the NTLM hash of a service account used for accessing a critical database server. With the extracted hash, the attacker crafts a forged Ticket Granting Ticket (TGT) for the database service and inserts it into the domain controller's memory. The attacker then uses the forged TGT to authenticate to the database server, bypassing normal authentication mechanisms. From there, they can access sensitive data stored in the database, manipulate records, or carry out other malicious activities without needing the actual password of the service account.
A

Prevention/Remediation Measures:

Protect Service Account Credentials: Keep service account credentials secure and regularly rotate them to minimize the risk of compromise.
Monitor Kerberos Traffic: Implement network monitoring tools to detect abnormal or suspicious Kerberos authentication traffic, which could indicate the presence of Silver Ticket attacks.
Implement Strong Security Policies: Enforce strong security policies that restrict unnecessary access and privileges, limiting the impact of compromised service accounts.
Use Credential Guard: Implement Windows Credential Guard or similar technologies to protect against credential theft and abuse.
Regular Security Audits: Conduct regular security audits and penetration testing to identify and remediate vulnerabilities in the authentication and authorization mechanisms.
30
Q

Gold Ticket Attack:

Description: A Gold Ticket attack is a type of Kerberos authentication attack where an attacker creates a forged Ticket Granting Ticket (TGT) using the Key Distribution Center's (KDC) long-term encryption key. This forged TGT grants the attacker unrestricted access to any service in the domain.

Scenario: An attacker gains access to a domain controller and extracts the KDC's long-term encryption key. Using this key, the attacker forges a TGT granting them unrestricted access to all services within the domain.
A

Prevention/Remediation:
Implement strict access controls and least privilege principles to limit the impact of compromised accounts.
Monitor Kerberos authentication logs for suspicious activity, such as multiple authentication requests from the same account.
Regularly rotate and update Kerberos service account passwords to mitigate the risk of long-term compromise.

31
Q

Credential Harvesting:

Description: Credential harvesting involves the systematic gathering of usernames, passwords, or other authentication credentials through various means such as phishing emails, fake login pages, or malware.

Scenario: An attacker sends phishing emails to employees, directing them to a fake login page that mimics the company's email portal. Unsuspecting users enter their credentials, which are captured by the attacker for unauthorized access.
A

Prevention/Remediation:
Educate users about the risks of phishing emails and social engineering tactics used by attackers to harvest credentials.
Implement email filtering and anti-phishing measures to detect and block malicious emails containing phishing links or attachments.
Use multi-factor authentication (MFA) to add an extra layer of security and mitigate the impact of stolen credentials.

32
Q

Credential Stuffing:

Description: Credential stuffing is a type of cyber attack where attackers use lists of username and password combinations obtained from previous data breaches to gain unauthorized access to user accounts on other platforms or services.

Scenario: An attacker obtains a list of username and password combinations leaked from a previous data breach and systematically attempts to log in to various online accounts using automated tools.
A

Prevention/Remediation:
Encourage users to use unique passwords for each account and avoid password reuse across multiple platforms.
Implement multi-factor authentication (MFA) to mitigate the risk of unauthorized access even if credentials are compromised.
Monitor login attempts for unusual patterns or high-volume login activity and implement account lockout mechanisms.

33
Q

Password Spraying:

Description: Password spraying is a type of brute force attack where attackers attempt to gain unauthorized access to multiple accounts by trying a few commonly used passwords against a large number of usernames.

Scenario: An attacker attempts to gain access to a company's network by trying common passwords such as "password123" or "123456" against a list of employee usernames.
A

Prevention/Remediation:
Enforce strong password policies requiring complex passwords that are resistant to dictionary attacks.
Implement account lockout mechanisms to prevent attackers from making repeated login attempts.
Monitor authentication logs for failed login attempts and investigate anomalies or patterns indicative of password spraying attacks.

33
Q

Downgrade Attacks:

Description: Downgrade attacks exploit vulnerabilities in cryptographic protocols or security mechanisms to force communication between systems to use less secure versions, allowing attackers to intercept or manipulate data.

Scenario: An attacker intercepts communication between a client and a server and downgrades the TLS protocol version from TLS 1.2 to SSL 3.0, which is vulnerable to known cryptographic attacks, allowing the attacker to eavesdrop on sensitive information transmitted between the client and server.
A

Prevention/Remediation:
Keep software and systems up to date with the latest security patches and updates to mitigate known vulnerabilities.
Disable insecure cryptographic algorithms and deprecated security protocols to prevent downgrade attacks.
Implement secure communication channels such as TLS 1.2 or later to protect data in transit from downgrade attacks.

34
Q

Domain Spoofing:

Description: In domain spoofing attacks, attackers typically manipulate the “From” field in email headers to display an address that resembles that of a reputable organization, such as a bank, government agency, or well-known company. By impersonating a trusted sender, attackers attempt to deceive recipients into believing that the email is legitimate and thus increase the likelihood of successful phishing.

Scenario:
Imagine a scenario in which employees at a financial institution receive emails purportedly originating from the organization’s IT department. The emails claim that due to a recent security breach, employees must reset their account passwords immediately by clicking on a provided link. The sender’s email address appears legitimate, resembling that of the organization’s IT department.
However, upon closer inspection, the emails exhibit several signs of domain spoofing, including inconsistencies in the sender’s domain name and irregularities in the email headers. Unaware of the phishing attempt, some employees proceed to click on the provided link and unwittingly divulge their account credentials to the attackers.

A

Prevention and Remediation Measures:

Implement Email Authentication Protocols:
    Deploy email authentication protocols such as SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance) to validate the authenticity of email senders.
    SPF helps verify that incoming messages are from authorized servers, DKIM allows for cryptographic authentication of email content, and DMARC provides policies for handling messages that fail authentication.

Enforce DMARC Policies:
    Configure DMARC policies to specify how email servers should handle messages that fail SPF and DKIM authentication checks.
    DMARC policies can instruct email servers to quarantine or reject suspicious messages, protecting recipients from domain spoofing attacks.

Educate Users:
    Provide regular security awareness training to educate users about the risks associated with domain spoofing attacks and how to recognize phishing attempts.
    Encourage users to scrutinize email headers, examine sender addresses closely, and avoid clicking on suspicious links or attachments.

Implement Email Filtering Solutions:
    Deploy advanced email filtering solutions capable of detecting and blocking domain spoofing attempts in real-time.
    These solutions can analyze email headers, content, and sender reputation to identify indicators of phishing and domain spoofing.
35
Q

Denial of Service (DoS) Attacks:

Distributed Denial of Service (DDoS) Attacks:
    Description: DDoS attacks involve multiple compromised systems, often distributed across the internet, coordinating to flood a target system or network with an overwhelming volume of traffic, rendering it inaccessible to legitimate users.

    Scenario: An online retailer's website becomes the target of a DDoS attack during a major holiday sale. The attackers flood the website with a massive volume of traffic, causing it to become unresponsive and preventing legitimate customers from accessing the site to make purchases.
A

Prevention/Remediation:
Implement network traffic monitoring and filtering mechanisms to detect and block malicious traffic patterns associated with DDoS attacks.
Deploy dedicated DDoS mitigation solutions or services that can identify and mitigate DDoS attacks in real-time, such as rate limiting, traffic scrubbing, and IP blacklisting.
Utilize content delivery networks (CDNs) to distribute traffic and absorb DDoS attacks closer to their source, reducing the impact on the target infrastructure.

35
Q

SQL Injection (SQLi):

Description: SQL injection involves inserting malicious SQL code into input fields or parameters of a web application to manipulate the application's database and gain unauthorized access to data.

Scenario: An attacker enters a specially crafted SQL command into the login form of a web application. The application fails to sanitize the input, allowing the attacker to bypass authentication and gain access to sensitive data stored in the database.
A

Prevention/Remediation:
Use parameterized queries or prepared statements to sanitize user input and prevent SQL injection vulnerabilities.
Implement input validation and output encoding to filter and sanitize user-supplied data before executing SQL queries.
Regularly conduct security testing, including vulnerability scanning and penetration testing, to identify and remediate SQL injection vulnerabilities.

36
Q

Command Injection:

Description: Command injection involves injecting malicious commands into input fields or parameters of an application, which are then executed by the underlying operating system.

Scenario: An attacker submits a specially crafted command containing system commands (e.g., shell commands) into a form field of a web application. The application fails to properly validate and sanitize the input, allowing the attacker to execute arbitrary commands on the underlying server.
A

Prevention/Remediation:
Implement proper input validation and parameterization to prevent the injection of malicious commands.
Use platform-specific security features such as shell escaping and input sanitization to mitigate command injection vulnerabilities.
Limit the privileges of the application or service executing the commands to minimize the potential impact of successful command injection attacks.

36
Q

Cross-Site Scripting (XSS):

Description: Cross-Site Scripting involves injecting malicious scripts, typically JavaScript, into web pages viewed by other users. This can lead to session hijacking, data theft, or unauthorized actions.

Scenario: An attacker embeds a malicious script into a comment field on a website. When other users view the comment, the script executes in their browsers, allowing the attacker to steal their session cookies and hijack their sessions.
A

Prevention/Remediation:
Implement input validation and output encoding to sanitize user input and prevent the injection of malicious scripts.
Use Content Security Policy (CSP) headers to restrict the execution of scripts and mitigate the impact of XSS attacks.
Educate developers about secure coding practices and the risks associated with XSS vulnerabilities.