ISC · Security and Confidentiality and Privacy · 9 practice questions
Phishing vs. Spear Phishing vs. Pharming: Payroll Portal Examples
A deceptive message points to phishing, tailored details make it spear phishing, and manipulated DNS points to pharming. Below: sort payroll portal examples by the message's targeting and how users reached the fake page.
Try one first
Hint
Focus on the attacker's method for getting access: was it by overwhelming a system, exploiting application code, intercepting a real session, or deceiving a user?
Answer D. The clerk was deceived by a tailored email that impersonated a known vendor and directed them to a fraudulent site controlled by the attacker. Because the attacker used social engineering and a fake login page to collect credentials (and the real vendor site was not compromised), this is best classified as spear phishing aimed at credential theft.
Why not A: Denial-of-service attacks aim to make systems unavailable by overwhelming resources, not to harvest credentials through impersonation. The primary harm here is credential theft via deception, not service unavailability.
Why not B: This may seem plausible because credentials were captured, but a man-in-the-middle attack involves intercepting a legitimate session or communications between two real parties in transit. Here the attacker collected credentials via a fake site rather than intercepting a live session, so it's phishing not MITM.
Why not C: SQL injection is an application-layer exploit where malicious input manipulates database queries; it requires exploiting a vulnerability in an application's handling of input. In this scenario the attacker simply spoofed a login page to trick the user into entering credentials, which is social engineering rather than SQL injection.
Sort it
A deceptive message seeks information or unsafe action without details tailored to a specific person or role.
A deceptive message targets a specific person or role using personal or organizational details.
Manipulated DNS or host settings redirect a correct URL or legitimate bookmark to a fake site.
| Item | Goes to |
|---|---|
| Employees receive an identical email warning that payroll portal passwords expire today. Its link opens a fake login page. | Generic phishingThe generic warning uses a deceptive link without tailored personal or business details. |
| The payroll manager receives an email referencing the actual year-end bonus process. Its link opens a fake payroll login page. | Spear phishingThe real bonus process makes the message specific to the manager's role. |
| Employees type the correct payroll portal URL. Altered internal DNS records send them to a fake login page without any message. | PharmingManipulated DNS, not a deceptive message, redirects the correct address. |
| An identical email tells employees to verify payroll access through a link. The fake page requests passwords and current MFA codes. | Generic phishingRequesting an MFA code does not change the generic message-based credential theft into another attack category. |
| Employees use legitimate payroll bookmarks. A poisoned DNS resolver sends them to a fake page that later forwards them to the real portal. | PharmingThe bookmark is legitimate; DNS manipulation causes the initial redirection. Forwarding users afterward does not change the mechanism. |
| Several payroll employees receive fake portal emails. Each message names its recipient and references that employee's actual payroll responsibilities. | Spear phishingMultiple recipients do not make the campaign generic when each message contains tailored role details. |
| Employees receive the same urgent payroll verification email with the company's logo. Its button opens an attacker-controlled login page. | Generic phishingUrgency and a copied logo do not establish targeting; the message remains generic. |
| The payroll manager receives a fake controller email naming the manager and referencing a real payroll correction. It links to a fraudulent portal. | Spear phishingThe manager's name and real payroll correction establish targeted deception. |
| Office users type the correct payroll URL but reach a fake portal. Internal DNS returns altered records; home users reach the genuine site. | PharmingThe altered internal DNS records explain why correct URLs redirect only office users. |
| A personalized email references the payroll manager's actual bonus review. The linked fake portal has a valid TLS certificate for its look-alike domain. | Spear phishingThe tailored message determines the classification. A valid certificate does not make the attacker-controlled portal genuine. |
| Employees receive an identical account-lock warning linking to a fake payroll portal. Investigators find no DNS or host-file manipulation. | Generic phishingThe deceptive email supplies the route to the fake page; the facts exclude pharming's technical redirection. |
| Employees enter the correct payroll URL. Malicious host-file entries map that hostname to an attacker-controlled login page. | PharmingAltered host settings redirect the legitimate hostname without requiring a deceptive message. |
Key points
- Remember: Classify how the user reached the fake page, then check whether a deceptive message used tailored details.
- Spear phishing is a subtype of phishing. Choose it when the question asks for the most specific classification.
- Logos, urgency, and HTTPS do not decide the category. The delivery mechanism and targeting do.
How the exam traps you
- Calling every fake login page pharming. Look for manipulated DNS or host settings, not merely a fake page reached through an email link.
- Calling an urgent message spear phishing just because it looks official. Look for details tailored to a specific person or role, such as a real payroll process.
Question 2
Hint
Connect the email click to the subsequent remote authenticated sessions, what attack explains valid logins from a new location without endpoint infection?
Answer A. The timeline (clicking an unsolicited email followed shortly by successful logins from a foreign IP using the same user's credentials), access to folders the user does not typically use, and outbound transfers are classic for credential compromise via phishing. The absence of endpoint infection indicators or ransom artifacts further points to remote reuse of stolen credentials rather than a malware infection or an insider action.
Why not B: Although exfiltration with valid credentials can indicate an insider, the rapid appearance of remote sessions from an overseas IP right after the email click and the user's atypical access pattern make account takeover via phishing more likely than intentional insider misuse.
Why not C: Modern ransomware sometimes exfiltrates data, but such incidents typically show local indicators (file encryption, ransom notes, or antivirus alerts). Those endpoint signs were not observed here, and the clear sequence of email click to remote authenticated logins better fits credential theft.
Why not D: A MITM can capture credentials, but it usually involves intercepting traffic rather than producing distinct new authenticated sessions from an overseas IP. The pattern here, email click followed by new remote logins using the employee's credentials, more directly supports credential harvesting and reuse.
Question 3
Hint
Focus on how the user arrived at the fake site. The absence of a deceptive message matters.
Answer A. Pharming silently redirects users from a legitimate address to a fraudulent site, typically through DNS manipulation, hosts-file/router compromise, or similar redirection methods. Because the users typed the correct URL but were still sent to the attacker's login page, pharming best fits this scenario.
Why not B: Tempting because phishing often uses fake login pages to harvest credentials, but phishing normally relies on social-engineering lures (malicious emails, texts, or links) to get users to the fake site. Here, users entered the correct URL and were redirected without clicking a deceptive message.
Why not C: Tempting because the fraudulent page is impersonating the real site, and spoofing broadly means falsifying identity or origin. However, spoofing is a general term; it doesn't specifically explain the silent redirection from a correct URL the way pharming does.
Why not D: Tempting because a MITM can intercept or alter web traffic and present false content, but MITM implies interception of communications in transit. The key distinguishing fact here is redirection despite typing the correct URL, which is more indicative of pharming (DNS/redirect compromise) than a classic MITM.
Question 4
Hint
Focus on what the attacker now controls and select the action that immediately removes or neutralizes that access.
Answer B. The facts indicate credential harvesting (users entered credentials on a look‑alike site and attackers then logged in). Immediate containment is to invalidate those credentials (password reset and session revocation), require password changes and add MFA to prevent replay, and review logs for unauthorized activity or lateral movement. Network/email blocking or endpoint remediation alone does not neutralize stolen credentials.
Why not A: This is tempting because it addresses the phishing source and observed attacker infrastructure, but it fails as immediate containment: blocking domains/IPs and monitoring reduce noise but do not invalidate credentials the attacker already has, and attackers can shift infrastructure quickly.
Why not C: Reimaging is tempting because it would remove a possible endpoint compromise, but scans show no malware and reimaging does not stop an attacker who already holds valid credentials; resetting credentials is a faster, higher-priority containment action.
Why not D: This distractor tempts by prioritizing remediation of infrastructure, but it misclassifies the incident: the indicators point to credential harvesting via a cloned site rather than a server-side exploit. Patching the portal will not prevent misuse of stolen credentials.
Question 5
Hint
Avoid interacting with the attachment; choose the option that uses formal reporting and an independent way to confirm the request.
Answer B. The email shows classic phishing indicators (mismatched sender address, unusual urgent request, and instructions to enable macros). Reporting via the organization's phishing process lets security investigate without interacting with the message, and verifying the request through a trusted, separate channel (phone, in‑person, or internal directory) confirms authenticity safely.
Why not A: This tempts because protected view seems to allow safe inspection, but opening attachments still interacts with potentially malicious files and may expose information or lead to unsafe follow‑up actions. The safer first step is to report and verify before opening the file.
Why not C: Replying is tempting as a quick way to confirm, but it uses the same channel that may be fraudulent and can allow an attacker to continue the deception. Use an independent, known contact method to verify instead.
Why not D: Forwarding might seem helpful, but it can spread the malicious email and bypasses formal incident response procedures. The organization's reporting process lets security investigate and notify others safely if needed.
Question 6
Hint
Focus on the earliest confirmed impact of the attack, not on later investigative or communication steps.
Answer B. Because the credentials were entered into a spoofed site, the account should be treated as compromised immediately. The first priority is containment, which means cutting off any attacker access by changing the password and terminating active sessions or tokens tied to that account. Additional investigation and device review may still be needed, but they come after the compromised credentials are addressed.
Why not A: Tempting because it seeks confirmation, but confirmed submission of credentials to a phishing site is itself sufficient evidence of exposure. Waiting risks the attacker using the credentials before containment.
Why not C: Reimaging may be appropriate if device compromise is found, but the immediate and confirmed impact is credential exposure. Containing the account comes before device remediation in this scenario.
Why not D: Notifying others can be useful, but it does not contain the known compromise. Leaving exposed credentials active while waiting for suspicious activity is unsafe.
Question 7
Hint
Focus on what makes the attack type distinct, not just on a common delivery detail.
Answer A. Phishing is a social-engineering attack that relies on deception to persuade victims to reveal sensitive information or take unsafe actions. In this case, employees were misled into entering credentials on a fraudulent site, the defining element of phishing. Other details (apparent sender, distribution size, or a link) are common features but not what makes the incident phishing.
Why not B: This is tempting because attackers often spoof internal addresses to gain trust. However, a spoofed or look-alike sender is a technique used in phishing, not the defining characteristic; the core issue is the deceptive request for credentials.
Why not C: Many phishing campaigns are sent broadly, so mass distribution is common. Still, whether the message targeted one person or many doesn't determine the attack type, the decisive factor is the deceptive solicitation of sensitive information.
Why not D: Links to fake login pages are a common phishing delivery method, but phishing can also use attachments, texts, or other channels. The delivery method is secondary to the social-engineering attempt to capture credentials.
Question 8
Hint
Identify the attack by focusing on how users arrived at the fake site, not just on the fact that credentials were stolen.
Answer D. The facts show users reached a fraudulent site despite using legitimate bookmarks because the company's internal DNS resolver temporarily mapped the payroll hostname to an attacker-controlled domain. That DNS-based redirection to a spoofed site is characteristic of pharming. There is no evidence traffic to the legitimate payroll site was intercepted nor that credentials were pre-existing from breaches, so pharming best explains how credentials were harvested.
Why not A: Tempting because users were tricked into entering credentials on a fake site, which commonly occurs in phishing. However, investigators found no suspicious messages and users arrived via saved bookmarks, indicating the deception came from altered name resolution rather than a targeted message-induced click.
Why not B: Tempting because compromised credentials were used by the attacker. Credential stuffing implies the attacker already possessed valid username/password pairs and automated login attempts; here the attacker obtained credentials directly from users entering them at the spoofed site caused by DNS redirection.
Why not C: Tempting because credentials were captured and users were redirected to the real portal, which might suggest interception. But the investigation found no evidence of traffic interception to the legitimate payroll site; the credentials were harvested on the spoofed site created via DNS manipulation, not by live session interception.
Question 9
Hint
Focus on which network component is returning the wrong IP address for the bank's domain and choose the containment action that stops further redirection first.
Answer D. The DNS trace indicates the internal resolver is returning poisoned A records (pharming). Immediate containment requires isolating the compromised resolver, flushing caches so clients stop being redirected, and temporarily pointing clients at a trusted DNS while the server is investigated and restored from a known-clean image. DNSSEC and other longer-term controls are appropriate later; credential resets and takedown requests are secondary actions after containment.
Why not A: Takedown requests and law enforcement involvement are important follow-up steps, but they are typically slower and do not immediately stop the poisoned DNS responses that are redirecting internal users. Immediate containment and remediation of the internal DNS resolver take priority.
Why not B: Credential resets and MFA reduce risk if credentials were captured, but they do not stop the DNS-level redirection itself, users will continue to be sent to the fraudulent site until the poisoned DNS responses are contained. Containment must focus on the resolver first.
Why not C: Phishing warnings and training are useful overall, but the incident evidence points to DNS poisoning from the internal resolver rather than an email-based phishing campaign; those actions won't stop the immediate redirection.
Common questions
What is the difference between phishing and spear phishing?
Spear phishing is targeted phishing. A generic payroll password warning is phishing; a message referencing the payroll manager's actual bonus process is spear phishing.
Is a fake payroll login page phishing or pharming?
The fake page alone does not decide. A deceptive email link points to phishing; a correct URL redirected by manipulated DNS points to pharming.
Does HTTPS mean a fake login page is not phishing?
No. An attacker-controlled site can have a valid TLS certificate for its own domain. Classify the attack by the message's targeting or the DNS redirection, not the padlock.
Watch it solved
A full CPA ISC task-based simulation on Threats and attacks, worked step by step.
SIEM Attack Identification | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Threats and attacks
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.