Connection to Internal Network via Telnet

  1[metadata]
  2creation_date = "2020/04/23"
  3integration = ["endpoint", "sentinel_one_cloud_funnel"]
  4maturity = "production"
  5updated_date = "2025/03/20"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Telnet provides a command line interface for communication with a remote device or server. This rule identifies Telnet
 11network connections to non-publicly routable IP addresses.
 12"""
 13false_positives = [
 14    """
 15    Telnet can be used for both benign or malicious purposes. Telnet is included by default in some Linux distributions,
 16    so its presence is not inherently suspicious. The use of Telnet to manage devices remotely has declined in recent
 17    years in favor of more secure protocols such as SSH. Telnet usage by non-automated tools or frameworks may be
 18    suspicious.
 19    """,
 20]
 21from = "now-9m"
 22index = ["logs-endpoint.events.network*", "logs-endpoint.events.process*", "logs-sentinel_one_cloud_funnel.*"]
 23language = "eql"
 24license = "Elastic License v2"
 25name = "Connection to Internal Network via Telnet"
 26note = """## Triage and analysis
 27
 28> **Disclaimer**:
 29> This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.
 30
 31### Investigating Connection to Internal Network via Telnet
 32
 33Telnet is a protocol offering a command-line interface for remote device management, often used in network environments. Adversaries may exploit Telnet to move laterally within a network, accessing non-public IPs to execute commands or exfiltrate data. The detection rule identifies Telnet connections to internal IP ranges, flagging potential unauthorized access attempts, thus aiding in early threat detection and response.
 34
 35### Possible investigation steps
 36
 37- Review the process details to confirm the Telnet connection initiation by examining the process.entity_id and process.name fields to ensure the process is indeed Telnet.
 38- Analyze the destination IP address to determine if it falls within the specified non-public IP ranges, indicating an internal network connection attempt.
 39- Check the event.type field to verify that the Telnet process event is of type "start", confirming the initiation of a connection.
 40- Investigate the source host by reviewing host.os.type and other relevant host details to understand the context and legitimacy of the connection attempt.
 41- Correlate the Telnet activity with any other suspicious network or process activities on the same host to identify potential lateral movement or data exfiltration attempts.
 42- Consult historical logs and alerts to determine if there have been previous similar Telnet connection attempts from the same source, which might indicate a pattern or ongoing threat.
 43
 44### False positive analysis
 45
 46- Routine administrative tasks using Telnet within internal networks can trigger false positives. To manage this, create exceptions for known IP addresses or specific user accounts that regularly perform these tasks.
 47- Automated scripts or monitoring tools that use Telnet for legitimate purposes may be flagged. Identify these scripts and whitelist their associated processes or IP addresses to prevent unnecessary alerts.
 48- Internal testing environments often simulate network activities, including Telnet connections. Exclude IP ranges associated with these environments to reduce false positives.
 49- Legacy systems that rely on Telnet for communication might generate alerts. Document these systems and apply exceptions based on their IP addresses or hostnames to avoid repeated false positives.
 50- Regularly review and update the list of excluded IPs and processes to ensure that only legitimate activities are exempted, maintaining the effectiveness of the detection rule.
 51
 52### Response and remediation
 53
 54- Immediately isolate the affected host from the network to prevent further lateral movement or data exfiltration.
 55- Terminate any active Telnet sessions on the affected host to stop unauthorized access.
 56- Conduct a thorough review of the affected host's system logs and Telnet session logs to identify any unauthorized commands executed or data accessed.
 57- Change all credentials that may have been exposed or used during the unauthorized Telnet sessions to prevent further unauthorized access.
 58- Apply security patches and updates to the affected host and any other systems that may be vulnerable to similar exploitation.
 59- Implement network segmentation to limit Telnet access to only necessary systems and ensure that Telnet is disabled on systems where it is not required.
 60- Escalate the incident to the security operations center (SOC) or incident response team for further investigation and to determine if additional systems have been compromised."""
 61references = ["https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml"]
 62risk_score = 47
 63rule_id = "1b21abcc-4d9f-4b08-a7f5-316f5f94b973"
 64setup = """## Setup
 65
 66This rule requires data coming in from one of the following integrations:
 67- Elastic Defend
 68- Auditbeat
 69
 70### Elastic Defend Integration Setup
 71Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 72
 73#### Prerequisite Requirements:
 74- Fleet is required for Elastic Defend.
 75- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
 76
 77#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
 78- Go to the Kibana home page and click "Add integrations".
 79- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
 80- Click "Add Elastic Defend".
 81- Configure the integration name and optionally add a description.
 82- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
 83- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. [Helper guide](https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html).
 84- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
 85- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
 86For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
 87- Click "Save and Continue".
 88- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
 89For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
 90
 91### Auditbeat Setup
 92Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
 93
 94#### The following steps should be executed in order to add the Auditbeat on a Linux System:
 95- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
 96- To install the APT and YUM repositories follow the setup instructions in this [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html).
 97- To run Auditbeat on Docker follow the setup instructions in the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html).
 98- To run Auditbeat on Kubernetes follow the setup instructions in the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html).
 99- For complete “Setup and Run Auditbeat” information refer to the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html).
100"""
101severity = "medium"
102tags = [
103    "Domain: Endpoint",
104    "OS: Linux",
105    "Use Case: Threat Detection",
106    "Tactic: Lateral Movement",
107    "Data Source: Elastic Defend",
108    "Data Source: SentinelOne",
109    "Resources: Investigation Guide",
110]
111type = "eql"
112
113query = '''
114sequence by process.entity_id
115  [process where host.os.type == "linux" and process.name == "telnet" and event.type == "start"]
116  [network where host.os.type == "linux" and process.name == "telnet" and cidrmatch(
117     destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
118     "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
119     "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
120     "192.175.48.0/24", "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
121     "FF00::/8"
122    )
123  ]
124'''
125
126
127[[rule.threat]]
128framework = "MITRE ATT&CK"
129[[rule.threat.technique]]
130id = "T1021"
131name = "Remote Services"
132reference = "https://attack.mitre.org/techniques/T1021/"
133
134
135[rule.threat.tactic]
136id = "TA0008"
137name = "Lateral Movement"
138reference = "https://attack.mitre.org/tactics/TA0008/"