Remote Management and Monitoring tool - Naverisk - Network Connection

Hunt Hypothesis

Adversaries may be using Naverisk, a Remote Management and Monitoring tool, to establish covert network connections for command and control or persistence. SOC teams should proactively hunt for this behavior in Azure Sentinel to detect potential abuse of legitimate RMM tools by threat actors leveraging T1219 techniques.

KQL Query

let Time_start = now(-5d);
let Time_end = now();
//
DeviceNetworkEvents
| where Timestamp between (Time_start..Time_end)
| where InitiatingProcessVersionInfoCompanyName has_any (
        'naverisk', 
        'NavMK1 Limited'
    )
| summarize FirstSeen=min(Timestamp), LastSeen=max(Timestamp), 
    Report=make_set(ReportId), Count=count() by DeviceId, DeviceName,
    RemoteUrl 

Analytic Rule Definition

id: 6a9e8751-beb2-48b3-b7c9-c86f57385b99
name: Remote Management and Monitoring tool - Naverisk - 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 InitiatingProcessVersionInfoCompanyName has_any (
          'naverisk', 
          'NavMK1 Limited'
      )
  | 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_Naverisk_netconn.yaml)

False Positive Guidance

• Scenario: Scheduled system maintenance using Naverisk to perform remote diagnostics
  Filter/Exclusion: Exclude connections initiated by scheduled tasks with the task name containing “SystemMaintenance” or “DiagnosticCheck”

• Scenario: Admin uses Naverisk to remotely update endpoint software
  Filter/Exclusion: Exclude connections where the source IP is a known internal management IP range (e.g., 10.0.0.0/8, 192.168.0.0/16) and the destination port is 80 or 443

• Scenario: IT team uses Naverisk to monitor network traffic for compliance purposes
  Filter/Exclusion: Exclude connections where the destination port is 443 and the user agent string contains “NaveriskMonitor” or “ComplianceCheck”

• Scenario: Admin runs a remote PowerShell script via Naverisk to configure firewall rules
  Filter/Exclusion: Exclude connections where the command line includes “powershell.exe” and the script path is within a known internal script repository (e.g., C:\ITScripts\)

• Scenario: Automated backup job uses Naverisk to transfer data between servers
  Filter/Exclusion: Exclude connections where the source and destination IPs are within the same internal subnet and the job name includes “BackupJob” or “DataTransfer”