Remote Management and Monitoring tool - SupRemo - Network Connection

Hunt Hypothesis

SupRemo is being used by adversaries to establish covert network connections for command and control or persistence. SOC teams should proactively hunt for this behavior in Azure Sentinel to identify potential compromise of remote systems through abused RMM tools.

KQL Query

let Time_start = now(-5d);
let Time_end = now();
//
DeviceNetworkEvents
| where Timestamp between (Time_start..Time_end)
| where RemoteUrl has_any (
        'supremocontrol.com',
        'nanosystems.it'
    )
    and InitiatingProcessVersionInfoCompanyName has 'NanoSystems'
| summarize FirstSeen=min(Timestamp), LastSeen=max(Timestamp), 
    Report=make_set(ReportId), Count=count() by DeviceId, DeviceName,
    RemoteUrl 

Analytic Rule Definition

id: 889b90bc-599e-4e28-bb19-1ffc04dbf80b
name: Remote Management and Monitoring tool - SupRemo - Network Connection
description: |
    Remote Monitoring and Management (RMM) programs are IT to manage remote endpoints. Attackers have begun to abuse these programs to persist or provide C2 channels.
    https://github.com/jischell-msft/RemoteManagementMonitoringTools
requiredDataConnectors:
- connectorId: MicrosoftThreatProtection
  dataTypes:
  - DeviceNetworkEvents
tactics: CommandAndControl
relevantTechniques: T1219
query: |
  let Time_start = now(-5d);
  let Time_end = now();
  //
  DeviceNetworkEvents
  | where Timestamp between (Time_start..Time_end)
  | where RemoteUrl has_any (
          'supremocontrol.com',
          'nanosystems.it'
      )
      and InitiatingProcessVersionInfoCompanyName has 'NanoSystems'
  | summarize FirstSeen=min(Timestamp), LastSeen=max(Timestamp), 
      Report=make_set(ReportId), Count=count() by DeviceId, DeviceName,
      RemoteUrl 

Required Data Sources

MITRE ATT&CK Context

• Tactic: CommandAndControl
• Technique: T1219 — T1219

References

• [Source Query](https://github.com/Azure/Azure-Sentinel/blob/main/Hunting Queries/Microsoft 365 Defender/RemoteManagementMonitoring/rmm_SupRemo_netconn.yaml)

False Positive Guidance

• Scenario: Scheduled Maintenance Task Using SupRemo
  Description: A system administrator schedules a routine maintenance task using SupRemo to update software on remote endpoints.
  Filter/Exclusion: process.name != "SupRemo.exe" OR event_id == 41 (for scheduled task creation)

• Scenario: Remote System Reboot via SupRemo
  Description: An IT admin uses SupRemo to remotely reboot a server during a planned maintenance window.
  Filter/Exclusion: process.name != "SupRemo.exe" OR event_id == 1006 (for system reboot events)

• Scenario: SupRemo Used for Patch Management
  Description: The IT team deploys patches to multiple endpoints using SupRemo as part of their patch management process.
  Filter/Exclusion: process.name != "SupRemo.exe" OR event_id == 1001 (for patch deployment events)

• Scenario: SupRemo Integration with SIEM for Log Collection
  Description: The security team configures SupRemo to send logs to a SIEM system for centralized monitoring and analysis.
  Filter/Exclusion: process.name != "SupRemo.exe" OR event_id == 1002 (for log forwarding events)

• Scenario: SupRemo Used for Remote Desktop Session Management
  Description: An admin uses SupRemo to establish a remote desktop session to troubleshoot a user’s endpoint.
  Filter/Exclusion: process.name != "SupRemo.exe" OR event_id == 1003 (for remote desktop session events)