https://feed.craftedsignal.io/tags/opencanary/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSat, 26 Oct 2024 18:22:34 +0000https://feed.craftedsignal.io/briefs/2024-10-opencanary-httpproxy/Sat, 26 Oct 2024 18:22:34 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-10-opencanary-httpproxy/Detection of attempted HTTP proxy use on an OpenCanary node, indicating potential reconnaissance or lateral movement by an attacker attempting to proxy another page.This threat brief focuses on detecting malicious attempts to use an OpenCanary node as an HTTP proxy. OpenCanary is a low-interaction honeypot designed to detect intruders on a network. An attacker attempting to use an OpenCanary node as an HTTP proxy is a strong indicator of reconnaissance or lateral movement, as they are attempting to route their traffic through the honeypot. This activity is logged by OpenCanary and can be detected with appropriate monitoring. The default configuration of OpenCanary includes an HTTPPROXY service that listens for proxy requests. Defenders should monitor OpenCanary logs for event ID 7001, which indicates an attempted HTTP proxy login.

Attack Chain

1. Attacker gains initial access to a network (e.g., through phishing or exploiting a vulnerability).
2. Attacker performs network reconnaissance to identify potential targets, including the OpenCanary node.
3. Attacker attempts to configure their system or tools to use the OpenCanary node as an HTTP proxy.
4. The attacker sends HTTP requests through the configured proxy, attempting to reach other systems on the network.
5. OpenCanary logs the attempted proxy connection with event ID 7001.
6. The defender detects the suspicious HTTP proxy attempt in the OpenCanary logs.

Impact

A successful HTTP proxy attempt indicates that an attacker is actively exploring the network and attempting to move laterally. This could lead to further compromise of sensitive systems and data exfiltration. While the OpenCanary node itself is a honeypot and not a production asset, the detection of proxy attempts signals a breach and ongoing malicious activity within the network.

Recommendation

• Deploy the provided Sigma rule OpenCanary HTTPPROXY Login Attempt to your SIEM and tune for your environment to detect unauthorized proxy attempts on OpenCanary nodes.
• Investigate any alerts generated by the Sigma rule to determine the source and target of the attempted proxy connection.
• Review OpenCanary configuration to ensure that the HTTPPROXY service is properly configured and secured.
• Implement network segmentation to limit the impact of potential lateral movement by attackers.

]]>highadvisoryopencanaryhoneypothttpproxylateral-movementhttps://feed.craftedsignal.io/briefs/2024-10-opencanary-telnet-login/Sat, 26 Oct 2024 14:30:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-10-opencanary-telnet-login/The OpenCanary Telnet Login Attempt detection identifies unauthorized login attempts to a Telnet service monitored by an OpenCanary node, indicating potential reconnaissance or intrusion attempts targeting the network.OpenCanary is a low-interaction honeypot designed to detect attackers on a network. This detection focuses on Telnet login attempts, a protocol rarely used legitimately in modern networks and thus a strong indicator of malicious activity. When an attacker attempts to log into a Telnet service on an OpenCanary node, it triggers this alert. This provides early warning of potential intrusion attempts, reconnaissance activities, or lateral movement by attackers who have already gained a foothold. The detection is based on OpenCanary’s logging functionality which records such login attempts, generating a log event with code 6001. This event signifies an attacker interacting with the Telnet service, which is unlikely in a well-secured and properly configured environment.

Attack Chain

1. Attacker scans the network for open ports, identifying a Telnet service.
2. Attacker attempts to connect to the Telnet service on the OpenCanary node.
3. Attacker enters credentials (username and password) in an attempt to authenticate.
4. OpenCanary logs the Telnet login attempt, generating an event with logtype 6001.
5. The detection rule triggers based on the OpenCanary log event.
6. Security team investigates the alert to determine the source and intent of the Telnet login attempt.
7. If the attempt is malicious, the security team takes steps to block the attacker and prevent further access.

Impact

A successful Telnet login could provide an attacker with unauthorized access to the network or specific systems. While Telnet itself may not grant immediate access to sensitive data, it can be used as a stepping stone for further exploitation and lateral movement. The compromise of even a single system can lead to data breaches, ransomware deployment, and significant disruption of services. OpenCanary serves as an early warning system, allowing defenders to identify and respond to such attempts before significant damage occurs.

Recommendation

• Deploy the Sigma rule OpenCanary - Telnet Login Attempt to your SIEM to detect unauthorized Telnet login attempts.
• Investigate any alerts generated by the OpenCanary - Telnet Login Attempt rule to determine the source and intent of the connection.
• Review the OpenCanary configuration to ensure it is properly deployed and monitoring the appropriate network segments.
• Consider disabling the Telnet service on all legitimate systems on the network to reduce the attack surface.

]]>highadvisoryhoneypottelnetreconnaissanceintrusionopencanary