Port / TCP
3260iSCSI target
iSCSI presents block storage volumes over TCP so initiators can mount them as local disks.
If it is internet-facing: Finding 3260 open to the internet is a finding in its own right — it warrants an explanation, not just a rule.
Exposure
Trusted network only
Transport
Cleartext
Risk if public
High
Exposure verdict
Port 3260 belongs on a trusted internal network. If a perimeter scan finds it answering, treat that as a firewall defect rather than a configuration preference.
Traffic crosses the network readable and modifiable. Anything sensitive on this port needs a tunnel, a VPN, or a different protocol.
Registered with IANA on request, but bindable by any unprivileged user. Registration records intent — it does not reserve the port, so collisions between products are common.
Grouped with the other file transfer & shares ports so a rule written for one can be checked against its neighbours.
What actually goes wrong
2 notes- Access is block-level: an initiator that attaches to a target can read the raw filesystem regardless of its file permissions.
- CHAP authentication is optional and often left off; keep iSCSI on a dedicated storage network.
Recommended firewall rule
Allow only from 10.0.0.0/8, drop the rest
Swap in the CIDR your administrators or application tier actually come from — the point is that the default answer is no.
ufw
sudo ufw allow from 10.0.0.0/8 to any port 3260 proto tcpiptables
sudo iptables -A INPUT -p tcp -s 10.0.0.0/8 --dport 3260 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 3260 -j DROPIf you do need it open to everyone
sudo ufw allow 3260/tcpWrite down why. An unexplained allow rule outlives the person who added it, and the next reviewer has no way to tell a deliberate exception from an accident.
Check what is really there
Listening locally
sudo ss -tlpn 'sport = :3260'The bind address is the answer that matters: 127.0.0.1 is local-only, 0.0.0.0 and :: mean every interface.
Listening (macOS)
sudo lsof -nP -iTCP:3260 -sTCP:LISTENmacOS ships lsof rather than ss; this names the owning process and user.
From outside
nmap -sV -Pn -p 3260 <host>A version probe confirms whether iSCSI target is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.
Reachability
nc -vz <host> 3260The quick yes/no when you only need to know whether a path exists through the firewall.