A newer version is available. For the latest information, see the
current release documentation.
RPC (Remote Procedure Call) from the Internet
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
RPC (Remote Procedure Call) from the Internet
editDetects network events that may indicate the use of RPC traffic from the Internet. RPC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or back-door vector.
Rule indices:
- filebeat-*
Severity: high
Risk score: 73
Runs every: 5 minutes
Searches indices from: now-6m (Date Math format, see also Additional look-back time)
Maximum signals per execution: 100
Tags:
- Elastic
- Network
Rule version: 2 (version history)
Added (Elastic Stack release): 7.6.0
Last modified (Elastic Stack release): 7.6.1
Rule query
editnetwork.transport: tcp and destination.port: 135 and ( network.direction: inbound or ( not source.ip: (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and destination.ip: (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) ) )
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Initial Access
- ID: TA0011
- Reference URL: https://attack.mitre.org/tactics/TA0011/
-
Technique:
- Name: Exploit Public-Facing Application
- ID: T1190
- Reference URL: https://attack.mitre.org/techniques/T1190/