Port 402Altiris Deployment Client
Altiris Deployment Client port 402 facilitates communication for Symantec's Altiris Deployment Solution, a remote management suite for device deployment, imaging, and maintenance within enterprise environments. It supports client-server interactions to streamline the automation of provisioning, software distribution, and system updates, enabling efficient management of large-scale IT infrastructures..
- transport
- tcp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 4/10
- lookups
- 10,194
single transport
payload readable on path
used by convention
caution
rank 449 of 993 · top 45%
Technical Details
what runs on :402Port 402 is predominantly utilized by Symantec's Altiris Deployment Solution, which is an enterprise-grade product used to provision and configure computers remotely. Leveraging this port, the Altiris Deployment Client software establishes a connection to Deployment Servers, enabling centralized management, device discovery, and orchestrated operational tasks.
Communication over port 402 allows the client to receive task commands, status updates, and deployment images. This port supports essential data flow including software distribution payloads, imaging commands, and logging information. Since it primarily uses TCP, it ensures reliable data transfer necessary for sensitive provisioning processes.
Typically, this port does not use encryption by default, although it can be secured via underlying VPN tunnels or additional security layers. Altiris environments often operate within controlled networks, but port 402’s accessibility should be carefully managed to avoid exposing critical deployment workflows.
Security Information
exposure of :402risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
network services averages 3.9 across 604 ports — this one sits 0.1 above.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp
every listening transport is another surface to filter at the edge
security overview
Common vulnerabilities associated with port 402 stem largely from weak access controls, lack of encryption, and unmonitored open exposure. An attacker exploiting this port could intercept deployment commands, inject malicious images, or gather network reconnaissance data, potentially gaining unauthorized control over devices.
Mitigation strategies include:
- Restricting network access to trusted management subnets
- Employing strong authentication and access controls for Altiris services
- Using VPNs or network segmentation to isolate deployment traffic
- Applying the latest vendor patches and security updates
- Monitoring port activity and implementing intrusion detection systems
- Disabling the port when not actively used for deployments
By applying these safeguards, administrators can substantially reduce the attack surface related to port 402.
Related Ports
the 8 most looked-up other ports in network services — 604 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :6543 | Jetnet | UDP | Network Services | caution | 65.3k |
| :5938 | TeamViewer | TCPUDP | Remote Access | caution | 65.0k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :3233 | WhiskerControl Protocol | TCPUDP | Network Services | caution | 61.9k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :3128 | Tatsoft Default HTTP Proxy | TCP | Web Services | caution | 46.8k |
risk mix of the 8 listed
- caution100%
0 of 8 encrypted