keepcalculator

06 Numbers and Powers

Detect & Contain Data Exfiltration from Financial Systems

Card No. 06·76092 · Updated · Standard formula, shown below

This guide walks you through detecting and containing data exfiltration from financial systems—covering the signs to watch for, the tools to use, and the immediate steps to stop the bleeding. You’ll learn how to spot suspicious activity, isolate affected systems, and preserve evidence for investigation, all while minimizing disruption to business operations.

What You’ll Need

  • Access to your SIEM (Security Information and Event Management) platform, or at least centralised logs from your financial systems.
  • Network monitoring tools or the ability to run packet captures (e.g., Wireshark, tcpdump) on the affected network segments.
  • Credentials with administrative privileges to firewall, proxy, and endpoint security solutions (to block traffic and isolate systems).
  • An incident response plan or at least a clear chain of command for who makes containment decisions.
  • A secure, isolated location (like a separate VLAN or a forensics workstation) to move affected systems to for analysis.
  • Write-protected storage or a forensic imaging tool (e.g., FTK Imager, dd) to preserve evidence.

Step-by-Step

  1. Establish a baseline. Before you can detect anomalies, you need to know what normal looks like. Review typical data transfer volumes, user access patterns, and outbound traffic from your financial systems. This baseline will help you spot deviations.
  2. Monitor outbound data transfers. Pay special attention to large or unusual outbound transfers. Use your SIEM to alert on:
    • Transfers exceeding a certain size (e.g., >100 MB) from financial servers.
    • Data sent to external IPs that aren’t on your approved vendor list.
    • Unusual protocols (e.g., FTP, SCP, or even HTTP POST requests to cloud storage) from servers that normally only use HTTPS to known domains.
  3. Watch for suspicious user behaviour. Look for signs like:
    • Users logging in at odd hours (e.g., 3 AM) or from unusual locations.
    • Users accessing financial records they don’t normally need for their role.
    • Multiple failed login attempts followed by a successful one (possible brute-force).
    • Users downloading entire databases or running bulk queries (e.g., SELECT * FROM transactions) when they typically only view individual records.
  4. Inspect network traffic for data exfiltration signatures. Use network monitoring tools to look for:
    • Encrypted traffic to unknown destinations—encryption itself isn’t bad, but if it’s going to a new IP, it’s suspicious.
    • DNS queries that look like encoded data (e.g., long subdomains like “aGVsbG8=.malicious.com”).
    • Traffic on unusual ports (e.g., SSH on port 443, or HTTP on port 22).
    • Data being sent to cloud storage services (like Dropbox or Google Drive) that aren’t sanctioned by your company.
  5. Check for data staging. Attackers often collect data into a single file before exfiltrating it. Look for:
    • Newly created compressed files (e.g., .zip, .rar) in unusual locations, especially on servers.
    • Large files appearing in temp directories or user home folders.
    • Files with names that don’t match the usual naming convention (e.g., “backup_2024.zip” on a server that never has backups).
  6. Isolate the affected system(s). Once you’ve confirmed a breach, immediately do the following:
    • Disconnect the affected server(s) from the network—either by pulling the cable, disabling the switch port, or using a firewall rule to block all traffic to/from that IP.
    • Do NOT shut down the system yet—you’ll lose volatile evidence (like memory contents).
    • If you must keep the system running (e.g., it’s a critical server), block only the outbound connections that are suspicious, and monitor it closely.
  7. Block the exfiltration path. In your firewall or proxy, block the destination IPs/domains you’ve identified as receiving the data. Also, block the user accounts involved—both locally and in Active Directory—to prevent further access.
  8. Preserve evidence. Before you start cleaning up, make a forensic image of the affected system’s hard drive and capture the contents of memory (RAM) if possible. Use write-protected media to store the images. Log all actions you take, with timestamps.
  9. Contain broader access. If the attacker had credentials to other systems, change those passwords immediately. Reset all service accounts that were used. Consider forcing a password reset for all users who have access to financial data.
  10. Monitor for re-infection. After containment, keep monitoring the network for signs of the attacker returning. They may have left backdoors. Run a full malware scan on the affected systems and review all scheduled tasks and startup entries.

Common Mistakes

  • Shutting down the system immediately. This destroys volatile evidence and may trigger the attacker to wipe data remotely.
  • Focusing only on the symptom. If you see a large outbound transfer, don’t just block that one IP—the attacker may have multiple paths. Look for the root cause (e.g., a compromised account).
  • Not baselining first. Without a baseline, you’ll miss subtle exfiltration that blends in with normal traffic.
  • Alerting too broadly. If you set alerts for every large transfer, you’ll get flooded with false positives and miss the real ones. Tune alerts to your environment.
  • Forgetting about cloud storage. Many financial systems now integrate with cloud services. If you don’t monitor those, exfiltration can happen via sanctioned tools.

Tips

  • Use data loss prevention (DLP) tools. They can automatically block sensitive data (like credit card numbers) from leaving the network, even if the user is unaware.
  • Enable detailed logging. Ensure your financial systems log all data access, including who, what, when, and from where. Centralize these logs in a SIEM for correlation.
  • Implement user behaviour analytics (UBA). These tools can flag anomalous behaviour (like a user downloading 10,000 records) that would be missed by rule-based alerts.
  • Test your incident response plan. Run tabletop exercises to ensure everyone knows their role in a data exfiltration scenario.
  • Segment your network. If financial systems are on a separate VLAN, you can quickly block all traffic to that segment without affecting the rest of the company.

Troubleshooting

You suspect exfiltration but can’t find the source. Start by reviewing DNS logs for suspicious queries, and check for any new user accounts or scheduled tasks that might be running on financial servers. If you have a network tap, capture all traffic to/from the financial segment for a few hours and analyse it for anomalies.

You’ve blocked an IP, but the data keeps leaking. The attacker may be using multiple IPs or a proxy. Look for patterns in the outbound traffic—like the same data being sent to different destinations. Also, check for encrypted tunnels (e.g., VPN over DNS) that might be bypassing your firewall.

You’ve contained the system, but you’re not sure if the exfiltration is still happening. Monitor the network for any new connections to known malicious IPs. Also, check for any changes to firewall rules or proxy settings that might have been made by the attacker.

You’re overwhelmed by false positives. Re-tune your alerts. Start with a high threshold (e.g., only alert on transfers >1 GB) and gradually lower it as you get comfortable with the noise. Use correlation rules to combine multiple low-severity events into a single high-severity alert.

Frequently Asked Questions

Q: What is the most common way data is exfiltrated from financial systems?
A: The most common methods are via email (sending sensitive files to external addresses), using cloud storage services (like Dropbox or Google Drive), or via FTP/SFTP to an attacker-controlled server. Sometimes attackers use DNS queries to encode data, but that’s less common.

Q: How quickly should I respond to a suspected exfiltration?
A: Immediately. The longer you wait, the more data can be stolen. Even if you’re not sure it’s a real incident, it’s better to isolate the system and investigate than to let it continue.

Q: Can I just delete the malicious files and move on?
A: No. You need to preserve evidence for potential legal action and to understand the full scope of the breach. Deleting files can destroy evidence and may not remove the attacker’s access.

Q: Should I notify law enforcement?
A: That depends on your jurisdiction and company policy. In many places, data breaches involving financial data must be reported to regulators. Consult your legal team before contacting law enforcement.

Q: How can I prevent data exfiltration in the future?
A: Implement a multi-layered approach: use DLP tools, enforce least-privilege access, encrypt sensitive data at rest and in transit, monitor all outbound traffic, and regularly review user access rights. Also, train employees to recognize phishing attempts, which are a common entry point.

Q: What’s the difference between data exfiltration and a data breach?
A: Data exfiltration is the act of stealing data (the exfiltration itself). A data breach is a broader term that includes any unauthorized access to data, even if no data is taken. Exfiltration is a type of breach, but not all breaches involve exfiltration.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →