ISC · Security and Confidentiality and Privacy · 6 practice questions
DNS Tunneling Signs: When to Activate Incident Response
Long, encoded DNS query labels plus an unexplained outbound spike indicate likely exfiltration and warrant immediate incident response. Below, follow a customer portal server example to identify the trigger without waiting for antivirus detection or confirmed data loss.
Try one first
Hint
Focus on whether the observed combination of unusual outbound data flows and concurrent privileged activity constitutes sufficient indicators to trigger containment and preserve evidence rather than waiting for antivirus confirmation or taking destructive steps immediately.
Answer A. The large, unusual outbound transfer to an unknown external IP combined with concurrent privileged-account activity and creation of a new account are credible indicators of an active compromise and likely data exfiltration. Best practice is immediate activation of the incident response plan and containment (network isolation/segmentation) to stop further loss and preserve volatile forensic evidence (RAM, active connections, logs). Passive monitoring or destructive remediation before proper forensic imaging risks continued exfiltration or destruction of evidence.
Why not B: Tempting because waiting can reduce false positives and avoid disruption, but endpoint AV can miss sophisticated compromises and delaying 24 hours risks continued exfiltration and loss of volatile evidence, so activating containment now is warranted.
Why not C: Tempting as a low-disruption response, but disabling an account and logging a user off may not stop an ongoing data transfer or other attacker persistence and does not ensure preservation of volatile forensic artifacts; containment and evidence capture should come first.
Why not D: Tempting because reimaging appears decisive, but powering off and reimaging before proper forensic imaging destroys volatile evidence (RAM, active network state) needed to determine scope and root cause and can hinder legal or insurance processes; forensic imaging before destructive remediation is preferred.
Step by step
- Identify the DNS pattern
A company's customer portal server sends frequent DNS queries to one external domain. The query names contain unusually long, high-entropy labels resembling base64-encoded strings.
- Correlate the outbound spike
The same server also produces an unexplained 12 GB overnight outbound spike to IP addresses linked to that domain. Together, these indicators support likely DNS-tunneling exfiltration rather than ordinary DNS lookups.
- Reject false reassurance
Antivirus reports no detections, and data loss has not been confirmed. Neither fact negates the correlated network evidence or justifies delaying activation.
- Activate incident response now
Activate the incident response plan immediately so the response team can coordinate containment and evidence preservation.
Key points
- Remember: Credible network evidence can trigger incident response before data loss is confirmed.
- Long, base64-like query labels suggest data may be carried inside DNS requests.
- An outbound spike linked to the same domain strengthens the suspected exfiltration pattern.
How the exam traps you
- Treating suspicious DNS traffic as harmless because antivirus reports no detections. Evaluate the network evidence; a clean antivirus result does not rule out compromise.
- Waiting for confirmed data loss before activating incident response. Activate when correlated DNS activity and an unexplained outbound spike indicate likely exfiltration.
Question 2
Hint
Focus on what the DNS queries contain (very long, base64‑looking subdomain labels and TXT requests) and the absence of substantial HTTP(S) egress, what attack method uses DNS payloads to move data?
Answer A. Very long, base64‑like subdomain labels and frequent TXT queries are classic indicators of chunked data transfer over DNS (DNS tunneling). The traffic pattern of many small DNS request packets carrying encoded payloads, combined with minimal HTTP(S) egress and normal authentication logs, supports covert exfiltration via DNS rather than browser‑based uploads or TLS C2.
Why not B: DNS amplification DDoS typically involves spoofed source IPs and very large response volumes aimed at a target, not numerous internal hosts issuing long, encoded subdomain/TXT queries. The observed pattern looks like payloads embedded in queries rather than amplified response traffic.
Why not C: Mass phishing would usually produce significant outbound HTTP(S) activity, interactive user events, and likely authentication anomalies. Here outbound HTTP(S) is minimal and the DNS queries themselves contain encoded payloads, indicating automated DNS‑based exfiltration instead of browser uploads of data.
Why not D: HTTPS C2 would create outbound TLS sessions and not the repeated long, base64‑like DNS subdomain labels and TXT queries seen here. While some malware uses DNS for C2, the presence of encoded, chunked DNS queries points more directly to data exfiltration than simple periodic HTTPS beaconing.
Question 3
Hint
Which immediate action both contains outbound traffic and preserves volatile RAM evidence for later forensic analysis?
Answer A. Isolating the host via EDR immediately stops or limits ongoing exfiltration while keeping the system powered on preserves volatile evidence (RAM, active sessions, in‑memory credentials, and process state). Capture live memory first, then acquire a full forensic disk image and document chain‑of‑custody, this follows the incident response sequence: containment → evidence collection → eradication.
Why not B: Tempting because powering off appears to stop data transfer quickly; wrong because a shutdown destroys volatile memory (active connections, in‑memory artifacts, credentials) that are often critical for forensic analysis and attribution, an offline disk image alone misses those artifacts.
Why not C: Tempting because blocking looks like immediate containment while allowing continued investigation; wrong because perimeter blocks do not guarantee full containment of an active internal compromise, do not preserve volatile RAM, and attackers can pivot to alternate IPs or channels.
Why not D: Tempting because credential resets address account misuse; wrong because resetting credentials will not stop a process already running in memory and can alter system state or alert the attacker, credential changes should follow containment and evidence preservation.
Question 4
Hint
Prioritize containment that preserves forensic evidence and involve incident response and legal/compliance before irreversible actions like powering down, paying, or restoring.
Answer B. The indicators (active encryption, large outbound transfers, ransom note) point to ransomware with possible data exfiltration. Containment is best achieved by isolating affected systems while preserving volatile forensic evidence (avoid powering off) so investigators can determine scope and exfiltration. Engage incident response and legal/compliance and involve law enforcement as appropriate before restoring from backups to meet regulatory and breach-notification obligations.
Why not A: Powering off may stop active encryption but destroys volatile evidence (memory contents, active network connections, transient logs) needed to determine whether data was exfiltrated and to support regulatory/breach-notification investigations.
Why not C: Paying the ransom can seem expedient but does not guarantee recovery, may not address prior data exfiltration, and can create legal and ethical issues; it should not replace proper investigation and consultation with legal counsel and law enforcement.
Why not D: Cutting power is overly disruptive and can destroy forensic evidence; restoring systems before assessing whether data was exfiltrated or meeting notification obligations risks noncompliance and recurrence.
Question 5
Hint
Which immediate actions best preserve volatile evidence and allow investigators to determine whether client data was exfiltrated before taking irreversible steps such as wiping, restoring, or paying?
Answer C. The ransom note plus large outbound transfers before encryption indicate probable ransomware with data exfiltration (double extortion). First priorities are containment and preservation of forensic evidence (images and logs) so investigators can determine the scope of exfiltration, detect any attacker persistence, and satisfy legal/regulatory obligations. Restoration or payment before these steps risks destroying evidence, missing ongoing access, and hindering response and reporting.
Why not A: This tempts because paying may seem the fastest way to recover files and stop publication, but it is risky and premature: payment does not guarantee decryption or nonpublication, may fund attackers, and bypasses necessary forensic investigation and legal/regulatory reporting needed to determine the true scope of the incident.
Why not B: This tempts because restoring from backups can quickly resume operations, but wiping hosts before collecting forensic images destroys volatile artifacts needed to identify the attack vector, confirm exfiltration, and detect persistence, potentially allowing the attacker to remain or re-enter and complicating regulatory obligations.
Why not D: This tempts because account disables and password resets are reasonable containment steps, but alone they are insufficient here: the indicators point to malware and likely exfiltration, and uncoordinated changes can destroy evidence or alert an active attacker; these actions must be coordinated with incident response while preserving forensic data.
Question 6
Hint
Compare authentication and device activity: who was actually at the machine, what preceded the downloads, and whether backup jobs or local copies explain the transfers.
Answer B. The sequence of many distributed failed login attempts followed by successful foreign-origin VPN logins using Employee J's credentials, combined with J being on leave and their workstation powered off, strongly supports credential compromise rather than insider action. The activity is read-only, low-and-slow, and directed to external cloud accounts; backup configurations and endpoint logs do not support automated backups or local exfiltration, and there are no malware or ransomware indicators.
Why not A: Tempting because the downloads used J's account, but it's unlikely because J was on leave and their workstation was powered off during the events. Authentication and VPN logs show foreign-origin successful sessions and prior distributed failed logins, which are stronger evidence of external account takeover than deliberate insider activity.
Why not C: Large transfers can resemble backups, but the organization has no backup or sync jobs configured to use J's credentials, nightly backups completed to a different appliance (different source IPs and destinations), and the transfers targeted external cloud accounts rather than known backup targets, making an automated backup misconfiguration unlikely.
Why not D: While some ransomware groups exfiltrate data before encrypting, the logs here show only read/download activity with no encryption, destructive writes, or malware indicators. The prolonged low-and-slow pattern and lack of lateral movement or malware signatures are more consistent with credential-based data theft than an active ransomware campaign.
Common questions
What DNS query patterns suggest data exfiltration?
Frequent queries to one external domain with unusually long, encoded subdomain labels suggest DNS tunneling. An unexplained outbound spike linked to that domain strengthens the suspicion.
Can DNS tunneling occur without antivirus alerts?
Yes. No antivirus detections does not negate the server's suspicious DNS queries and correlated outbound transfer.
When should DNS tunneling indicators trigger incident response?
Activate immediately when long, encoded DNS queries and an unexplained outbound spike provide credible evidence of likely exfiltration. Do not wait for confirmed data loss.
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.