CompTIA Sec+ SY0-701 Cyber Attacks
This content covers three major cybersecurity threats: ransomware, Trojan horses, and spyware. Each section describes the nature of the attack, provides real-life scenarios, and offers preventive and remedial measures to protect against these threats.
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.
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.
Key Terms
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.
Preventive Measures: Employ email and web filtering solutions to block malicious attachments and links, keep systems and software updated with secu...
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.
Preventive Measures: Exercise caution when downloading files or software from untrusted sources, use reputable antivirus software to scan for and r...
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.
Preventive Measures: Install reputable anti-spyware software to detect and remove spyware, avoid clicking on suspicious links or pop-up ads, and re...
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
Preventive Measures: Keep systems and software updated with security patches, segment network traffic to contain potential worm outbreaks, and depl...
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.
Preventive Measures: Install reputable ad-blocking extensions or software, be cautious when downloading free software from the internet, and regula...
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.
Preventive Measures: Regularly update system firmware and security patches, use secure boot processes to prevent unauthorized modifications, and im...
Related Flashcard Decks
Study Tips
- Press F to enter focus mode for distraction-free studying
- Review cards regularly to improve retention
- Try to recall the answer before flipping the card
- Share this deck with friends to study together
Term | Definition |
---|---|
Ransomware: | 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. |
Trojan Horse: | 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. |
Spyware: | 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. |
Worms: | 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. |
Adware: | 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. |
Rootkits: | 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. |
Botnets: | 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. |
Cryptojacking: | 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. |
Fileless Malware: | 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. |
Mobile Malware: | 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. |
Scareware: | 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. |
Backdoors: | 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. |
Exploit Kits: | 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. |
Email Phishing Attacks: | Prevention/Remediation: |
Spear Phishing Attacks: | Prevention/Remediation: |
Vishing (Voice Phishing) Attacks: | Prevention/Remediation: |
Smishing (SMS Phishing): | Prevention/Remediation: |
Whaling Attacks: | Prevention/Remediation: |
Email Spoofing: | Prevention/Remediation: |
DNS Spoofing (DNS Cache Poisoning): | Prevention/Remediation: |
ARP Spoofing (Man-in-the-Middle): | Prevention/Remediation: |
GPS Spoofing: | Prevention/Remediation: |
IP Spoofing: | Prevention/Remediation: |
Credential Stuffing: | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
Kerberoasting: Description: Scenario: | 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. |
Man-in-the-Middle (MitM) Attack: Description: Scenario: | 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. |
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. | 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. |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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: | 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. |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |
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. | Prevention/Remediation: |