Registered · Cross-platform

8089 Splunk management

TCP Unofficial
UDP No
SCTP
DCCP

What it is

Splunk daemon management (splunkd).

When / why

Splunk REST/management. Restrict to admin sources.

Protocol status detail

TransportStatusMeaning
TCP Unofficial Not assigned by IANA, but standardized, specified, or widely used on this port.
UDP No Not assigned, standardized, or widely used on this port.
SCTP Not applicable for this transport.
DCCP Not applicable for this transport.

Port range

Registered (1024–49151). Assigned by IANA on request; usable without elevated privileges on most systems.

Browse all ports →

Firewall rules for port 8089

Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.

ufw

sudo ufw allow proto tcp from <source> to any port 8089

Allow TCP 8089 (Splunk management). Replace <source> with the network/host that should reach it.

firewalld

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="8089" protocol="tcp" accept'

Allow TCP 8089 (Splunk management) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> tcp dport 8089 accept

Allow TCP 8089 (Splunk management). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p tcp -s <source> --dport 8089 -j ACCEPT

Allow TCP 8089 (Splunk management). Persist with iptables-save/netfilter-persistent.

Azure NSG

az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-splunkmanagement-8089 --priority 1000 --access Allow --direction Inbound --protocol TCP --source-address-prefixes <source> --destination-port-ranges 8089

Inbound rule for 8089 (Splunk management). Set <source> to a CIDR; lower priority number = higher precedence.

AWS Security Group

aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=tcp,FromPort=8089,ToPort=8089,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 8089 (Splunk management). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-splunkmanagement-8089 --direction=INGRESS --action=ALLOW --rules=tcp:8089 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 8089 (Splunk management). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow Splunk management 8089/TCP" dir=in action=allow protocol=TCP localport=8089 remoteip=<source>

Inbound TCP 8089 (Splunk management). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow Splunk management 8089/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 8089 -RemoteAddress <source>

Inbound TCP 8089 (Splunk management). Replace <source> with a host or subnet.

Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.