T1546.014 Emond no MITRE ATT&CK

Contexto para AppSec

Em uma auditoria de AppSec, Emond deve ser usada para revisar caminhos em que código, configuração, dependências ou infraestrutura podem viabilizar o comportamento descrito pela MITRE. No ATT&CK, ela aparece em Privilege Escalation e Persistence. As plataformas mapeadas pela MITRE incluem macOS. No Vigly, esse contexto ajuda a conectar evidências do repositório com priorização e remediação.

Tática/fase Privilege Escalation, Persistence

Plataformas MITRE macOS

Descrição oficial original do MITRE ATT&CK

Adversaries may gain persistence and elevate privileges by executing malicious content triggered by the Event Monitor Daemon (emond). Emond is a Launch Daemon that accepts events from various services, runs them through a simple rules engine, and takes action. The emond binary at /sbin/emond will load any rules from the /etc/emond.d/rules/ directory and take action once an explicitly defined event takes place. The rule files are in the plist format and define the name, event type, and action to take. Some examples of event types include system startup and user authentication. Examples of actions are to run a system command or send an email. The emond service will not launch if there is no file present in the QueueDirectories path /private/var/db/emondClients, specified in the Launch Daemon configuration file at/System/Library/LaunchDaemons/com.apple.emond.plist. Adversaries may abuse this service by writing a rule to execute commands when a defined event occurs, such as system start up or user authentication. Adversaries may also be able to escalate privileges from administrator to root as the emond service is executed with root privileges by the Launch Daemon service.

Ver fonte oficial no MITRE ATT&CK

T1546.014: Emond

Contexto para AppSec

Descrição oficial original do MITRE ATT&CK

Como o Vigly audita a técnica Emond automaticamente na sua pipeline