Dwell Time

Dwell Time

One-liner: The duration an attacker remains undetected in a compromised environment from initial breach to discovery.

🎯 What Is It?

Dwell Time (also called Attacker Dwell Time) is the period between when an attacker first compromises a system and when the breach is detected and responded to. It's a critical security metric that measures how long adversaries can operate freely within your environment.

Lower dwell time = Better security posture

πŸ€” Why It Matters

Industry Benchmarks

πŸ”¬ How It Works

Dwell Time Timeline

[Initial Compromise] ────────────────────> [Detection]
        ↑                                      ↑
   T=0 (Breach)                          T=X (Discovery)
        
        <──────── Dwell Time = X ──────────>

During Dwell Time:
β”œβ”€ Reconnaissance
β”œβ”€ Credential Harvesting  
β”œβ”€ Lateral Movement
β”œβ”€ Privilege Escalation
β”œβ”€ Data Exfiltration
└─ Persistence Installation

Factors That Increase Dwell Time

  1. Poor Visibility: Lack of logging or monitoring coverage
  2. Alert Fatigue: Too many false positives, real threats missed
  3. Detection Gaps: Adversary TTPs not covered by detection rules
  4. Insufficient Staffing: SOC can't keep up with alerts
  5. Advanced Adversaries: Sophisticated evasion techniques

Factors That Decrease Dwell Time

  1. Threat Hunting: Proactive search for hidden threats
  2. Strong Detection Engineering: Comprehensive coverage of MITRE ATT&CK TTPs
  3. EDR: Real-time endpoint visibility
  4. Cyber Threat Intelligence (CTI): Intelligence-driven detection
  5. Mature Incident Response: Fast triage and investigation

πŸ›‘οΈ Detection & Prevention

How to Measure Dwell Time

# Calculate dwell time
dwell_time = detection_timestamp - initial_compromise_timestamp

# Example
Initial Compromise: 2024-01-05 08:00:00
Detection:          2024-01-20 14:30:00
Dwell Time:         15 days, 6 hours, 30 minutes

How to Reduce Dwell Time

  1. Implement Proactive Threat Hunting

    • Don't wait for alertsβ€”actively search for threats
    • Use MITRE ATT&CK to guide hunting priorities
  2. Improve Detection Coverage

  3. Deploy EDR

    • Real-time endpoint visibility
    • Behavioral analytics to catch novel attacks
  4. Leverage Cyber Threat Intelligence (CTI)

    • Hunt for IOCs of relevant threat actors
    • Implement detections for relevant TTPs
  5. Reduce Alert Fatigue

    • Tune detection rules to minimize false positives
    • Prioritize high-fidelity alerts
  6. Automate Response

    • SOAR for initial triage and containment
    • Faster mean time to respond (MTTR)

πŸ“Š Dwell Time by Attack Type

Attack Type Typical Dwell Time Detection Method
Ransomware 1-5 days EDR, anomaly detection
Business Email Compromise 30-60 days Email monitoring, suspicious transfers
Nation-State APT 200+ days Threat Hunting, Cyber Threat Intelligence (CTI)
Insider Threat 85+ days Data Loss Prevention (DLP), UBA
Cryptojacking 90+ days Resource monitoring, network analysis

🎀 Interview Angles

Common Questions

STAR Story

Situation: Our organization's average dwell time was 32 daysβ€”significantly above industry average. We were detecting incidents only after major damage had occurred.
Task: Reduce dwell time to under 10 days through improved detection and proactive hunting.
Action: Established a weekly Threat Hunting program focused on high-risk TTPs. Mapped our detection coverage against MITRE ATT&CK and created 20 new rules for gaps. Deployed EDR across all endpoints. Integrated threat intelligence feeds to hunt for relevant APT IOCs. Tuned SIEM rules to reduce false positives by 60%.
Result: Reduced average dwell time from 32 days to 8 days within 6 months. Discovered 3 previously undetected breaches during initial hunts, all with 30+ day dwell times. After improvements, no incident exceeded 48-hour dwell time in the following year.

βœ… Best Practices

❌ Common Misconceptions

πŸ“š References