- Close the port if nothing on the host needs it.
- Identify the process that listens on it (commands below) before opening it in a firewall.
- Expose a service only to the networks that use it.
Port 132: cisco SYSMAINT
Port 132 is assigned by IANA to cisco-sys (cisco SYSMAINT).
How cisco-sys works
Other servicesThe client sends a request to port 132 and the cisco-sys service answers.
- Transport
- TCP · UDP
- Exposure risk
- not rated depends on the program listening
- Encryption
- Unknownnot stated by the registry
- IANA status
- Assigned1 registered service
- Range
- Well-known (0-1023)
- Category
- Other services
Is port 132 dangerous?
We have no specific security note for port 132. Its risk depends on the program actually listening on it. General advice for other services services:
IANA registry entries for port 132
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| cisco-sys | 132 | TCP, UDP | cisco SYSMAINT | - | - |
// source: IANA service name and port number registry
Which program uses port 132, and is it reachable?
Linux
sudo ss -ltnup 'sport = :132' # process listening on 132
sudo lsof -nP -i :132macOS
sudo lsof -nP -i :132
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 132 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 132 netstat -ano | findstr :132
From another machine
nmap -p 132 -sV <host> sudo nmap -sU -p 132 <host> nc -zv <host> 132
Block it in the firewall
sudo ufw deny 132/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 132" -Direction Inbound -LocalPort 132 -Protocol TCP -Action Block # Windows
What is port 132 used for?
Port 132 is assigned by IANA to cisco-sys (cisco SYSMAINT).
Is port 132 TCP or UDP?
Port 132 is registered for TCP and UDP.
Is it safe to open port 132?
It depends on the program that listens on it. Open it only for a service you know and only to the networks that need it. Close the port if nothing on the host needs it.
How do I check if port 132 is open?
On Linux run "ss -ltnup 'sport = :132'", on macOS "lsof -nP -i :132", and on Windows "netstat -ano | findstr :132" to see the local process. From another machine, "nmap -p 132 <host>" shows whether it is reachable.