Firewall Port Summary
For convenience a summary of ports potentially used are listed here. Please see other references in the Security Document for full details of the use of these ports. Ports that may well be customized in your environment are written in italics
Appliance Ports
Standalone Appliance Ports
Port Number |
Port assignment |
Direction |
Use |
Reference |
---|---|---|---|---|
4 |
Closed Port |
Outbound |
Base Device Detection |
|
21 |
FTP |
Outbound |
Base Device Detection |
|
22 |
SSH |
Inbound |
Appliance CLI access |
|
22 |
SSH |
Outbound |
UNIX Discovery |
|
23 |
telnet |
Outbound |
UNIX Discovery |
|
25 |
SMTP |
Outbound |
Email Relay |
|
53 |
DNS |
Outbound |
Domain Name Lookup |
|
80 |
HTTP |
Inbound |
Main UI Standard |
|
80 |
HTTP |
Outbound |
Base Device Detection |
|
123 |
NTP |
Outbound |
Time Synchronisation |
|
135 |
DCE RPC Endpoint Manager. |
Outbound |
Windows Discovery |
|
161 |
SNMP |
Outbound |
SNMP Discovery |
|
389 |
LDAP |
Outbound |
LDAP UI User Authentication |
|
443 |
HTTPS |
Inbound |
Main UI Secure |
|
513 |
rlogin |
Outbound |
UNIX Discovery |
|
636 |
LDAPS |
Outbound |
Secure LDAP UI User Authentication |
|
902 |
vSphere API |
Outbound |
VMware ESX/ESXi Discovery |
|
1433 |
MS SQL |
Outbound |
MS SQL Extended Discovery |
|
1521 |
Oracle SQL |
Outbound |
Oracle SQL Extended Discovery |
|
3306 |
MySQL SQL |
Outbound |
MySQL SQL Extended Discovery |
|
3940 |
Discovery for z/OS Agent |
Outbound |
Mainframe Discovery |
|
4100 |
Sybase SQL |
Outbound |
Sybase ASE SQL Extended Discovery |
|
4321 |
CORBA |
Outbound |
AD Windows proxy |
|
4323 |
CORBA |
Outbound |
Credential Windows proxy |
|
7001 |
JMX |
Outbound |
J2EE Extended Discovery |
|
ARTCPPORT Value |
AR System |
Outbound |
CMDB Sync |
Scanning Appliance Ports
Scanning appliance will not sync to CMDB, this will done from the consolidation appliance.
Port Number |
Port assignment |
Direction |
Use |
Reference |
---|---|---|---|---|
4 |
Closed Port |
Outbound |
Base Device Detection |
|
21 |
FTP |
Outbound |
Base Device Detection |
|
22 |
SSH |
Inbound |
Appliance CLI access |
|
22 |
SSH |
Outbound |
UNIX Discovery |
|
23 |
telnet |
Outbound |
UNIX Discovery |
|
25 |
SMTP |
Outbound |
Email Relay |
|
53 |
DNS |
Outbound |
Domain Name Lookup |
|
80 |
HTTP |
Inbound |
Main UI Standard |
|
80 |
HTTP |
Outbound |
Base Device Detection |
|
123 |
NTP |
Outbound |
Time Synchronisation |
|
135 |
DCE RPC Endpoint Manager. |
Outbound |
Windows Discovery |
|
161 |
SNMP |
Outbound |
SNMP Discovery |
|
389 |
LDAP |
Outbound |
LDAP UI User Authentication |
|
443 |
HTTPS |
Inbound |
Main UI Secure |
|
513 |
rlogin |
Outbound |
UNIX Discovery |
|
636 |
LDAPS |
Outbound |
Secure LDAP UI User Authentication |
|
902 |
vSphere API |
Outbound |
VMware ESX/ESXi Discovery |
|
1433 |
MS SQL |
Outbound |
MS SQL Extended Discovery |
|
1521 |
Oracle SQL |
Outbound |
Oracle SQL Extended Discovery |
|
3306 |
MySQL SQL |
Outbound |
MySQL SQL Extended Discovery |
|
3940 |
Discovery for z/OS Agent |
Outbound |
Mainframe Discovery |
|
4100 |
Sybase SQL |
Outbound |
Sybase ASE SQL Extended Discovery |
|
4321 |
CORBA |
Outbound |
AD Windows proxy |
|
4323 |
CORBA |
Outbound |
Credential Windows proxy |
|
7001 |
JMX |
Outbound |
J2EE Extended Discovery |
|
25032 |
CORBA |
Outbound |
Consolidation |
Consolidation Appliance Ports
Consolidation appliance will not normally do local discovery it will purely consolidate data from scanning appliances.
Port Number |
Port assignment |
Direction |
Use |
Reference |
---|---|---|---|---|
22 |
SSH |
Inbound |
Appliance CLI access |
|
25 |
SMTP |
Outbound |
Email Relay |
|
53 |
DNS |
Outbound |
Domain Name Lookup |
|
80 |
HTTP |
Inbound |
Main UI Standard |
|
123 |
NTP |
Outbound |
Time Synchronisation |
|
389 |
LDAP |
Outbound |
LDAP UI User Authentication |
|
443 |
HTTPS |
Inbound |
Main UI Secure |
|
636 |
LDAPS |
Outbound |
Secure LDAP UI User Authentication |
|
ARTCPPORT Value |
AR System |
Outbound |
CMDB Sync |
|
25032 |
CORBA |
Inbound |
Consolidation |
Windows proxy Ports
Proxy port changes in 8.3 SP2
In BMC Atrium Discovery 8.3 SP2, proxies are not limited to the default ports. It is also possible to install multiple proxies of each type on a single host. Consequently, in BMC Atrium Discovery 8.3 SP2 you must check the proxy manager to determine which ports the proxies are using. The defaults are the same as previous releases, but installations of additional proxies use incremental ports. You can also use the proxy manager to modify the port that each proxy uses.
Port Number |
Port assignment |
Direction |
Use |
Reference |
---|---|---|---|---|
135 |
DCE RPC Endpoint Manager. |
Outbound |
Windows Discovery |
|
139 |
Netbios Session Service |
Outbound |
Windows Discovery |
|
389 |
LDAP |
Outbound |
AD User Authentication |
|
445 |
Microsoft Directory Services SMB |
Outbound |
Windows Discovery |
|
636 |
LDAPS |
Outbound |
Secure LDAP UI User Authentication |
|
1024-1030 |
Firewall Restricted DCOM |
Outbound |
Windows Discovery |
|
1024-65535 |
Unrestricted DCOM |
Outbound |
Windows Discovery |
|
4321 |
CORBA |
Inbound |
AD Windows proxy |
|
4323 |
CORBA |
Inbound |
Credential Windows proxy |
Comments
This table really needs to specify the IP level protocol such as ICMP vs. UDP vs. TCP. Is the reader supposed to assume that TCP is meant unless the record obviously indicates otherwise, such as the "ICMP Echo" entry?
Yes, exactly that.
The only non TCP entry above that is not an otherwise well known protocol is port 4. As port 4 is unusual it's explained in the link, and the opening paragraph makes it clear that this is only a summary and the links provided provide more detail where needed.
Too many columns will make the page very difficult to read and I decided that it is more important for firewall admins to understand the direction the port is going to be opened in than the protocol; if they don't know what ICMP and SNMP is they probably shouldn't be maintaining security critical firewalls.
A lot of people use this table who are not strictly firewall admins. People in security and other roles use this table to gauge risk or upcoming work, and afterwards for troubleshooting purposes. But besides that, because a port is "well known" does not mean that TCP vs. UDP for that service is well known. There are lots of firewall admins who rely on the documentation at hand to know whether Corba, JMX, NTP, etc. are TCP vs. UDP, especially in the several cases where the relevant specs allows for both UDP and TCP but only one is used in typical setups. Following the links provided here do not answer these questions.
Agreed that another full column here would be bad, but that's not the only way to provide the information. Reference documentation should be complete. Can't we afford a few asterisks and a footnote?
Another example where clients often need to know but it is not documented anywhere I can find, is whether the 111 + (presumably non-system) ports used by CMDB default Remedy portmapper connections are UDP or TCP; and same question if CMDB is configured to use a single port. We should make basic information which is needed for basic network security configuration easily accessible. We shouldn't have to research details of "CMDB Protocol" to administer ADDM.
Log in or register to comment.