Command and Control (TA0011)(external, opens in a new tab or window)
text code block:sequence by host.id, process.entity_id with maxspan=1m [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.args == "server" and process.args in ("--port", "-p", "--reverse", "--backend", "--socks5") and process.args_count >= 3 and process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")] [network where host.os.type == "linux" and event.type == "start" and event.action == "connection_accepted" and destination.ip != null and destination.ip != "127.0.0.1" and destination.ip != "::1" and not process.name : ( "python*", "php*", "perl", "ruby", "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk", "java", "telnet", "ftp", "socat", "curl", "wget", "dpkg", "docker", "dockerd", "yum", "apt", "rpm", "dnf", "ssh", "sshd", "hugo")]
Install detection rules in Elastic Security
Detect Potential Protocol Tunneling via Chisel Server in the Elastic Security detection engine by installing this rule into your Elastic Stack.
To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(external, opens in a new tab or window).