Tag: 내부자위협

  • Departing Employee Data Exfiltration: A 5-Step Detection Procedure That Closes the Gap Content DLP Can’t See

    Departing Employee Data Exfiltration: A 5-Step Detection Procedure That Closes the Gap Content DLP Can’t See

    Key Takeaways

    • Content-based DLP creates a blind spot: when a file contains no blocking pattern, it cannot distinguish a legitimate download from data exfiltration, so no alert is ever triggered.
    • The remaining tenure after a resignation notice (a 2-week window in the source discussion) consistently serves as a concentrated exfiltration window, during which data movement to personal email, personal cloud storage, USB drives, and web uploads spikes sharply.
    • The detection signals that matter are behavioral metadata rather than file contents. Confidence rises when account context, time of day, data volume, external destination, and unusual file extensions are combined.

    practice

    Table of Contents

    The day after a resignation notice, a sales rep starts moving three years of pipeline and customer lists to a personal Gmail and personal cloud account. Content-matching DLP barely catches this activity disguised as normal work. Departing employee data exfiltration concentrates within a short 2-week window right after the notice, and by the time departing employee data exfiltration is suspected, copies are often already sitting outside the organization.

    Why Departing Employee Data Exfiltration Keeps Happening

    Content DLP only fires alerts when a file contains explicit patterns like “confidential” or “restricted,” or when attachment size crosses a threshold. Sales pipeline CSVs, customer meeting notes, and proposal PDFs are files that normally flow in everyday work, so they get classified as legitimate downloads. Departing employee data exfiltration has an inherent blind spot: a normal file without any pattern can’t itself become a signal of suspicion. From a practitioner’s standpoint, the visible problem is that DLP stays silent even when the same copy flows only during usual business hours.

    It takes one to three business days for a resignation notice to be recorded in the HR system and for the IT team to receive an access revocation request. During the 2-week gap that follows, many organizations repeatedly observe a pattern in which external email attachments, personal cloud sync, USB copies, and web uploads surge to more than 5x the normal rate.

    Which Signals Should You Treat as Suspicious?

    Behavioral metadata matters more than file contents. Confidence rises sharply when the following five signals appear alone or, better, in combination.

    Signal Normal Range Suspicion Threshold
    Time of day 9 AM to 7 PM, business hours Overnight or early-morning, large weekend transfers
    Volume 5–20 transfers per day Hundreds within a short window, or 5x+ normal rate
    External destination Corporate email, corporate cloud Personal email, personal cloud, external URL
    File extension .docx, .xlsx, .pdf .zip, .7z, split archives, base64-encoded payloads
    Account context Corporate IP, managed device New tokens, MFA bypass, unmanaged device

    5-Step Detection and Containment Procedure for Departing Employee Data Exfiltration

    The following procedure consolidates solutions repeatedly proposed in the community. The focus is on shortening the time from the moment departing employee data exfiltration is suspected to the point of access revocation.

    Step 1. Establish a baseline of normal behavior

    Even without a resignation notice, record each department’s and individual’s external transfer patterns for at least 30 days. Define normal ranges for the share of after-hours transfers, average attachment size, and frequently used external domains. Without a baseline, the very definition of “abnormal” is empty, and alerts become meaningless.

    Step 2. Cap external email attachment size and add topology-based alerts

    Set per-email attachment caps at 10–25 MB, and trigger an alert when cumulative attachments to the same recipient exceed 50 MB. Outbound sends to external domains outside the whitelist are sorted into a separate category.

    Step 3. File activity logs from endpoint agents

    Retain file creation, movement, and external storage connection events from managed devices for at least 90 days. Track USB mounts, external hard drive connections, large clipboard copies, and local path changes by cloud sync clients.

    Step 4. Anomalous events in the identity layer

    Add to the risk score whenever there is a new device token issuance, repeated MFA failures, or a login from a geographic location the user has not used before. Abnormal external sharing events on document links previously shared with the departing employee’s account are routed to a dedicated alert channel.

    Step 5. HR–Security collaboration checklist

    As soon as a resignation notice is recorded in the HR system, the IT security team receives an automatic alert. Define a 4-hour SLA from notice to access revocation, and run the following items as a checklist.

    • Block corporate SSO/IdP login or strengthen MFA for the account
    • Block inbound external email or set the attachment cap to 0
    • Bulk-revoke all externally shared links
    • Invalidate cloud drive sync client tokens
    • Prepare a remote lock for managed devices

    3 Common Mistakes

    Mistake 1. Gradual access revocation — Reducing the original account’s privileges a little at a time, in the name of knowledge transfer, simply gives the departing employee a window to exfiltrate. Operate a separate knowledge-transfer account and read-only copies of documents separately from the original account.

    Mistake 2. No baseline — Treating every transfer as suspicious without a quantitative definition of “different from normal” causes alert volume to explode, which eventually breeds a culture of ignoring them. A numeric baseline must be managed as a team KPI.

    Mistake 3. Mismatched timing between HR and security notifications — The most common structure is one in which HR keeps the notice private while the security team is only informed at the time of public announcement. The notification channel and timing must be aligned at the system level.

    Post-Incident Response Procedure

    Once a suspicious event has already occurred, log preservation comes first. Retain endpoint logs, mail gateway logs, and identity layer logs for at least one year, and isolate all activity logs of the departing employee’s account in a dedicated case folder. At the post-incident stage, proving departing employee data exfiltration depends most heavily on identity layer logs.

    Content DLP alone cannot distinguish files disguised as normal work, and the same limitation is repeatedly reported in the original thread cataloguing departing employee exfiltration detection cases. Behavioral signals become more reliable when collected simultaneously from three layers — endpoint, network, and identity — and the same limitation is also addressed in the 5-step practical procedure for AI-driven data leak prevention.

    Practical Application Points

    Relying on content DLP alone creates a blind spot. Behavioral signals must be collected simultaneously from three layers — endpoint, network, and identity — to become reliable, and teams that hold a numeric baseline connect suspicious events to follow-up action within an average of 4 hours. Locking the notice-to-revocation SLA at 4 hours or less is the critical operational variable.

    What to Do Right Now

    • Integrate the HR system with the IdP so that a notice triggers an automatic access-revocation alert within 4 hours
    • Extract 30 days of external transfer baselines by department and document the normal ranges for time of day, volume, and external domains
    • Lower the external email attachment cap to 10–25 MB and apply a rule that fires an alert when cumulative attachments to the same recipient reach 50 MB
    • Extend endpoint agent log retention to at least 90 days and collect USB and cloud sync events separately
    • Document a post-hoc detection procedure for activity that occurs outside managed devices, with notifications delivered within 24 hours

    Frequently Asked Questions

    Won’t revoking access immediately after the resignation notice block knowledge transfer?

    Knowledge transfer is carried out through a separate transfer account, with documents provided as read-only copies, separated from the original account. The original account’s access should, as a rule, be revoked within 4 hours.

    Couldn’t we catch it with content-based DLP if we just add more detection rules?

    Pattern-based DLP simply multiplies the bypass techniques. It cannot reliably counter paths such as compression, image capture, or copy-and-paste of text. Collecting behavioral metadata in parallel is the practical approach.

    How do you catch activity that happens outside a managed device?

    It can only be reconstructed from corporate system logs: the mail gateway, cloud audit logs, and SSO logs. When no endpoint agent is present, identity layer events become the most important clue.

    Does departing employee data exfiltration risk persist beyond the 2-week post-notice window?

    Up to 30–90 days after departure, follow-on activity has been observed, such as re-uploads of copies that remained in personal cloud storage and reactivation of previously shared links. It is prudent to maintain monitoring for up to 90 days post-departure.

    Reference Source

    This article was written after reviewing the following original thread: r/AskNetsec — How do companies actually detect departing employees bulk-downloading or exfiltrating files?