Skip to content

MITRE ATT&CK Mitigations

MITRE ATT&CK mitigations represent the “what” of defense - the security controls and countermeasures that can prevent or limit the effectiveness of adversary techniques. This section provides detailed implementation guidance for each mitigation category.

Manage the creation, modification, use, and permissions associated with privileged accounts.

# eBPF security rule for privileged account changes
- rule: Privileged Account Changes
desc: Detect changes to privileged accounts
condition: >
(proc.name = "usermod" or proc.name = "useradd" or proc.name = "passwd") and
(proc.cmdline contains "root" or proc.cmdline contains "admin" or proc.cmdline contains "sudo")
output: >
Privileged account change detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for permission changes
- rule: Permission Changes
desc: Detect changes to user permissions
condition: >
(proc.name = "chmod" or proc.name = "chown" or proc.name = "usermod") and
(proc.cmdline contains "777" or proc.cmdline contains "root" or proc.cmdline contains "admin")
output: >
Permission change detected
(user=%user.name command=%proc.cmdline)
  • Account creation and modification monitoring
  • Permission changes tracking and alerting
  • Privileged access logging and auditing
  • User behavior analysis and monitoring
  • Account lifecycle management and monitoring
  1. Configure user monitoring in AlertKick
  2. Set up privilege escalation detection rules
  3. Implement account lifecycle management
  4. Enable privilege access logging and auditing
  5. Configure user behavior analysis

Set and enforce secure password policies throughout the organization.

# eBPF security rule for password policy violations
- rule: Password Policy Violation
desc: Detect password policy violations
condition: >
(proc.name = "passwd" or proc.name = "chpasswd") and
(proc.cmdline contains "weak" or proc.cmdline contains "simple" or proc.cmdline contains "default")
output: >
Password policy violation detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for authentication failures
- rule: Authentication Failures
desc: Detect multiple authentication failures
condition: >
(proc.name = "sshd" or proc.name = "login" or proc.name = "su") and
(proc.cmdline contains "failed" or proc.cmdline contains "denied" or proc.cmdline contains "invalid")
output: >
Authentication failure detected
(user=%user.name service=%proc.name)
  • Password complexity requirements and enforcement
  • Password history tracking and prevention
  • Account lockout policies and monitoring
  • Multi-factor authentication implementation
  • Password management system integration
  1. Configure password policy monitoring in AlertKick
  2. Set up authentication failure detection
  3. Implement account lockout policies
  4. Enable multi-factor authentication monitoring
  5. Configure password management integration

Configure operating systems securely to reduce the attack surface.

# eBPF security rule for system configuration changes
- rule: System Configuration Changes
desc: Detect system configuration changes
condition: >
(proc.name = "sysctl" or proc.name = "systemctl" or proc.name = "chkconfig") and
(proc.cmdline contains "disable" or proc.cmdline contains "enable" or proc.cmdline contains "modify")
output: >
System configuration change detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for service management
- rule: Service Management
desc: Detect service management activities
condition: >
(proc.name = "systemctl" or proc.name = "service" or proc.name = "chkconfig") and
(proc.cmdline contains "start" or proc.cmdline contains "stop" or proc.cmdline contains "restart")
output: >
Service management detected
(user=%user.name command=%proc.cmdline)
  • System hardening and configuration management
  • Service management and monitoring
  • Configuration drift detection and alerting
  • System compliance monitoring and reporting
  • Change management and approval processes
  1. Configure system hardening monitoring in AlertKick
  2. Set up service management detection
  3. Implement configuration drift detection
  4. Enable system compliance monitoring
  5. Configure change management processes

Perform audits or scans of systems, permissions, insecure software, insecure configurations, etc.

# eBPF security rule for audit activities
- rule: Audit Activities
desc: Detect audit and scanning activities
condition: >
(proc.name = "auditctl" or proc.name = "ausearch" or proc.name = "aureport") and
(proc.cmdline contains "audit" or proc.cmdline contains "scan" or proc.cmdline contains "check")
output: >
Audit activity detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for security scanning
- rule: Security Scanning
desc: Detect security scanning activities
condition: >
(proc.name = "nmap" or proc.name = "nessus" or proc.name = "openvas") and
(proc.cmdline contains "scan" or proc.cmdline contains "audit" or proc.cmdline contains "check")
output: >
Security scanning detected
(user=%user.name tool=%proc.name)
  • Regular security audits and assessments
  • Vulnerability scanning and management
  • Configuration compliance monitoring
  • Security posture assessment and reporting
  • Remediation tracking and management
  1. Configure audit monitoring in AlertKick
  2. Set up vulnerability scanning detection
  3. Implement compliance monitoring and reporting
  4. Enable security posture assessment
  5. Configure remediation tracking and management

M1048: Application Isolation and Sandboxing

Section titled “M1048: Application Isolation and Sandboxing”

Isolate applications from each other and from the underlying system.

# eBPF security rule for container activities
- rule: Container Activities
desc: Detect container creation and management
condition: >
(proc.name = "docker" or proc.name = "podman" or proc.name = "containerd") and
(proc.cmdline contains "run" or proc.cmdline contains "create" or proc.cmdline contains "start")
output: >
Container activity detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for sandbox activities
- rule: Sandbox Activities
desc: Detect sandbox creation and management
condition: >
(proc.name = "firejail" or proc.name = "bubblewrap" or proc.name = "sandbox") and
(proc.cmdline contains "sandbox" or proc.cmdline contains "isolate" or proc.cmdline contains "jail")
output: >
Sandbox activity detected
(user=%user.name command=%proc.cmdline)
  • Container security and monitoring
  • Sandbox isolation and management
  • Application whitelisting and blacklisting
  • Process isolation and monitoring
  • Resource limits and monitoring
  1. Configure container monitoring in AlertKick
  2. Set up sandbox isolation detection
  3. Implement application whitelisting and blacklisting
  4. Enable process isolation monitoring
  5. Configure resource limits and monitoring

Use capabilities to prevent suspicious code from executing.

# eBPF security rule for antivirus activities
- rule: Antivirus Activities
desc: Detect antivirus and antimalware activities
condition: >
(proc.name = "clamav" or proc.name = "sophos" or proc.name = "mcafee") and
(proc.cmdline contains "scan" or proc.cmdline contains "quarantine" or proc.cmdline contains "remove")
output: >
Antivirus activity detected
(user=%user.name tool=%proc.name)
# eBPF security rule for malware detection
- rule: Malware Detection
desc: Detect malware and suspicious activities
condition: >
(proc.name in (malware_processes)) and
(proc.cmdline contains "malicious" or proc.cmdline contains "suspicious" or proc.cmdline contains "trojan")
output: >
Malware detected
(user=%user.name process=%proc.name)
  • Real-time scanning and protection
  • Signature-based detection and updates
  • Behavioral analysis and monitoring
  • Quarantine management and isolation
  • Incident response and remediation
  1. Configure antivirus monitoring in AlertKick
  2. Set up malware detection and alerting
  3. Implement behavioral analysis and monitoring
  4. Enable quarantine management and isolation
  5. Configure incident response and remediation

Perform regular backups of data and test restoration procedures.

# eBPF security rule for backup activities
- rule: Backup Activities
desc: Detect backup and restore activities
condition: >
(proc.name = "rsync" or proc.name = "tar" or proc.name = "dd") and
(proc.cmdline contains "backup" or proc.cmdline contains "restore" or proc.cmdline contains "archive")
output: >
Backup activity detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for data recovery
- rule: Data Recovery
desc: Detect data recovery activities
condition: >
(proc.name = "testdisk" or proc.name = "photorec" or proc.name = "ddrescue") and
(proc.cmdline contains "recover" or proc.cmdline contains "restore" or proc.cmdline contains "rescue")
output: >
Data recovery detected
(user=%user.name tool=%proc.name)
  • Regular backup scheduling and monitoring
  • Backup integrity verification and testing
  • Restore procedure testing and validation
  • Backup storage security and encryption
  • Disaster recovery planning and testing
  1. Configure backup monitoring in AlertKick
  2. Set up backup integrity verification
  3. Implement restore procedure testing
  4. Enable backup storage security monitoring
  5. Configure disaster recovery planning and testing

Architect sections of the network to isolate critical systems, functions, or resources.

# eBPF security rule for network traffic
- rule: Network Traffic
desc: Detect network traffic and connections
condition: >
(fd.sport in (80, 443, 22, 21, 25, 53)) and
(not fd.sip in (trusted_networks))
output: >
Network traffic detected
(user=%user.name connection=%fd.name)
# eBPF security rule for network segmentation
- rule: Network Segmentation
desc: Detect network segmentation violations
condition: >
(proc.name = "iptables" or proc.name = "firewall" or proc.name = "ufw") and
(proc.cmdline contains "block" or proc.cmdline contains "allow" or proc.cmdline contains "deny")
output: >
Network segmentation detected
(user=%user.name command=%proc.cmdline)
  • Network segmentation and isolation
  • Traffic filtering and monitoring
  • Access control and authentication
  • Network monitoring and alerting
  • Security policy enforcement
  1. Configure network monitoring in AlertKick
  2. Set up traffic filtering and monitoring
  3. Implement access control and authentication
  4. Enable network monitoring and alerting
  5. Configure security policy enforcement

Use network intrusion prevention systems to identify and prevent malicious network activity.

# eBPF security rule for intrusion detection
- rule: Intrusion Detection
desc: Detect network intrusion attempts
condition: >
(proc.name = "snort" or proc.name = "suricata" or proc.name = "zeek") and
(proc.cmdline contains "intrusion" or proc.cmdline contains "attack" or proc.cmdline contains "threat")
output: >
Intrusion detection triggered
(user=%user.name tool=%proc.name)
# eBPF security rule for threat detection
- rule: Threat Detection
desc: Detect network threats and attacks
condition: >
(proc.name = "threat" or proc.name = "attack" or proc.name = "malware") and
(proc.cmdline contains "detect" or proc.cmdline contains "prevent" or proc.cmdline contains "block")
output: >
Threat detected
(user=%user.name threat=%proc.name)
  • Network intrusion detection and prevention
  • Threat intelligence integration and monitoring
  • Real-time alerting and response
  • Network traffic analysis and monitoring
  • Incident response and remediation
  1. Configure intrusion detection in AlertKick
  2. Set up threat detection and monitoring
  3. Implement real-time alerting and response
  4. Enable network traffic analysis
  5. Configure incident response and remediation

Use multi-factor authentication for user and privileged accounts.

# eBPF security rule for MFA activities
- rule: MFA Activities
desc: Detect multi-factor authentication activities
condition: >
(proc.name = "google-authenticator" or proc.name = "authy" or proc.name = "duo") and
(proc.cmdline contains "authenticate" or proc.cmdline contains "verify" or proc.cmdline contains "token")
output: >
MFA activity detected
(user=%user.name tool=%proc.name)
# eBPF security rule for authentication
- rule: Authentication
desc: Detect authentication activities
condition: >
(proc.name = "sshd" or proc.name = "login" or proc.name = "su") and
(proc.cmdline contains "authenticate" or proc.cmdline contains "login" or proc.cmdline contains "verify")
output: >
Authentication detected
(user=%user.name service=%proc.name)
  • Multi-factor authentication implementation
  • Authentication monitoring and logging
  • User training and awareness
  • Authentication policy enforcement
  • Incident response and remediation
  1. Configure MFA monitoring in AlertKick
  2. Set up authentication monitoring and logging
  3. Implement user training and awareness
  4. Enable authentication policy enforcement
  5. Configure incident response and remediation

Use data loss prevention (DLP) solutions to monitor and prevent data exfiltration.

# eBPF security rule for DLP activities
- rule: DLP Activities
desc: Detect data loss prevention activities
condition: >
(proc.name = "dlp" or proc.name = "data" or proc.name = "prevention") and
(proc.cmdline contains "monitor" or proc.cmdline contains "prevent" or proc.cmdline contains "block")
output: >
DLP activity detected
(user=%user.name tool=%proc.name)
# eBPF security rule for data exfiltration
- rule: Data Exfiltration
desc: Detect data exfiltration activities
condition: >
(proc.name = "scp" or proc.name = "rsync" or proc.name = "ftp") and
(proc.cmdline contains "upload" or proc.cmdline contains "send" or proc.cmdline contains "transfer")
output: >
Data exfiltration detected
(user=%user.name command=%proc.cmdline)
  • Data classification and labeling
  • Data monitoring and protection
  • User training and awareness
  • Policy enforcement and monitoring
  • Incident response and remediation
  1. Configure DLP monitoring in AlertKick
  2. Set up data classification and labeling
  3. Implement data monitoring and protection
  4. Enable user training and awareness
  5. Configure policy enforcement and monitoring

Restrict software installation to authorized personnel and applications.

# eBPF security rule for software installation
- rule: Software Installation
desc: Detect software installation activities
condition: >
(proc.name = "apt" or proc.name = "yum" or proc.name = "pip") and
(proc.cmdline contains "install" or proc.cmdline contains "add" or proc.cmdline contains "upgrade")
output: >
Software installation detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for package management
- rule: Package Management
desc: Detect package management activities
condition: >
(proc.name = "dpkg" or proc.name = "rpm" or proc.name = "snap") and
(proc.cmdline contains "install" or proc.cmdline contains "remove" or proc.cmdline contains "update")
output: >
Package management detected
(user=%user.name command=%proc.cmdline)
  • Software whitelisting and blacklisting
  • Installation monitoring and logging
  • User permissions and access controls
  • Software inventory and management
  • Policy enforcement and monitoring
  1. Configure software monitoring in AlertKick
  2. Set up software whitelisting and blacklisting
  3. Implement installation monitoring and logging
  4. Enable user permissions and access controls
  5. Configure software inventory and management

Restrict hardware installation to authorized personnel and devices.

# eBPF security rule for hardware installation
- rule: Hardware Installation
desc: Detect hardware installation activities
condition: >
(proc.name = "modprobe" or proc.name = "insmod" or proc.name = "usb") and
(proc.cmdline contains "install" or proc.cmdline contains "add" or proc.cmdline contains "connect")
output: >
Hardware installation detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for device management
- rule: Device Management
desc: Detect device management activities
condition: >
(proc.name = "udev" or proc.name = "systemd" or proc.name = "hal") and
(proc.cmdline contains "device" or proc.cmdline contains "hardware" or proc.cmdline contains "peripheral")
output: >
Device management detected
(user=%user.name command=%proc.cmdline)
  • Hardware whitelisting and blacklisting
  • Device monitoring and logging
  • User permissions and access controls
  • Hardware inventory and management
  • Policy enforcement and monitoring
  1. Configure hardware monitoring in AlertKick
  2. Set up hardware whitelisting and blacklisting
  3. Implement device monitoring and logging
  4. Enable user permissions and access controls
  5. Configure hardware inventory and management

Configure policies and procedures for the appropriate use of organizational accounts.

# eBPF security rule for account policy
- rule: Account Policy
desc: Detect account policy violations
condition: >
(proc.name = "useradd" or proc.name = "usermod" or proc.name = "passwd") and
(proc.cmdline contains "policy" or proc.cmdline contains "violation" or proc.cmdline contains "breach")
output: >
Account policy violation detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for user behavior
- rule: User Behavior
desc: Detect suspicious user behavior
condition: >
(proc.name = "su" or proc.name = "sudo" or proc.name = "login") and
(proc.cmdline contains "suspicious" or proc.cmdline contains "anomalous" or proc.cmdline contains "unusual")
output: >
Suspicious user behavior detected
(user=%user.name command=%proc.cmdline)
  • Account policy development and enforcement
  • User behavior monitoring and analysis
  • Policy violation detection and alerting
  • User training and awareness
  • Incident response and remediation
  1. Configure account policy monitoring in AlertKick
  2. Set up user behavior monitoring and analysis
  3. Implement policy violation detection and alerting
  4. Enable user training and awareness
  5. Configure incident response and remediation

Filter network traffic to prevent access to unauthorized services and resources.

# eBPF security rule for network filtering
- rule: Network Filtering
desc: Detect network filtering activities
condition: >
(proc.name = "iptables" or proc.name = "firewall" or proc.name = "ufw") and
(proc.cmdline contains "filter" or proc.cmdline contains "block" or proc.cmdline contains "allow")
output: >
Network filtering detected
(user=%user.name command=%proc.cmdline)
# eBPF security rule for traffic analysis
- rule: Traffic Analysis
desc: Detect network traffic analysis
condition: >
(proc.name = "tcpdump" or proc.name = "wireshark" or proc.name = "tshark") and
(proc.cmdline contains "capture" or proc.cmdline contains "analyze" or proc.cmdline contains "monitor")
output: >
Traffic analysis detected
(user=%user.name tool=%proc.name)
  • Network filtering and access controls
  • Traffic monitoring and analysis
  • Policy enforcement and monitoring
  • User training and awareness
  • Incident response and remediation
  1. Configure network filtering monitoring in AlertKick
  2. Set up traffic monitoring and analysis
  3. Implement policy enforcement and monitoring
  4. Enable user training and awareness
  5. Configure incident response and remediation