System communications and network ports
The core of the application manages the discovery and reasoning engines. It consistently interacts with the security engine to ensure user authentication and request authorization so that each action taken by the application can only be triggered from the application itself or by a user through the application UI or command line. External communications between the user and the application are only permitted to use HTTPS.
The encryption of communication between the discovery engine (appliance or Windows proxy) and the target depends on the discovery method used. For example, ssh is encrypted, but telnet and rlogin (which might both be disabled) are not. Discovery credentials can be configured to use a user-supplied SSH key per credential. These keys and their associated passphrases are stored in the credential vault. It is recommended that SSH keys are always protected with a strong passphrase.
The rlogin access method that is used to connect to an endpoint is not a secure protocol as communication is not encrypted. Rlogin is not available in the BMC Discovery Outpost UI. If required, you can use rlogin in the appliance UI.
Secure communications between elements of the system use CORBA over TLS (Transport Layer Security) with the following details:
- Protocol: TLSv1.2
- Encryption: AES_256_CBC
- Message hashing: SHA-256
- Key Exchange: DHE_RSA (2048)
It is enabled using certificates in the following locations:
- Each appliance (scanning or consolidation)
- Each Windows proxy
Certificate Authority public certificate on each appliance and proxy
This refers to communications between components of the BMC Discovery system, not communications between BMC Discovery and discovery targets, or between the user's web browser and the appliance UI.
Security of communication and data between BMC Discovery Outpost and the appliance
- You must register the Outpost with the BMC Discovery appliance, and the BMC Discovery appliance with the Outpost. The registration process ensures that:
- The BMC Discovery appliance listens only for Outposts that you have registered it with.
Your Outposts only ask for jobs from the BMC Discovery appliance that you have registered them with.
- Communication between the Outpost and the BMC Discovery appliance is always encrypted, and always sent over HTTPS .
- The registration process establishes the second level of encryption of the messages between the Outpost and the appliance, which means that we do not just rely on the security of HTTPS communications. The Outpost can communicate with the appliance by using web proxies, and even if a decrypting web proxy is used to transport the messages, the content cannot be read.
- Messages are encrypted by using tokens exchanged at registration that are used for AES encryption, ensuring that only that Outpost and that appliance can read the messages.
- The encrypted messages are sent over HTTPS.
- Communication between the Outpost and the BMC Discovery appliance is always from the Outpost to the BMC Discovery appliance. Communication is never initiated by the BMC Discovery appliance.
- Credentials to access and discover your infrastructure never leave your premises.
For more information, see Secure deployment.
Apache SSL key passphrases
BMC recommend that you do not passphrase the Apache SSL server key used by the appliance. Doing so requires entry of the passphrase at service start-up, which conflicts with the following operations:
- Resetting configuration of a machine (invoked from the Cluster Management UI and when a machine leaves the cluster)
- Configuring HTTPS (via the UI and possibly when sending configuration to cluster members). A specific issue is that once a passphrase is applied it is no longer possible to restart HTTPS via the UI, without first regenerating the server key.
- Remedy SSO
- Backup/Restore (as SSL keys are restored)
End-user application authentication is critical to the security of the entire solution. BMC Discovery supports a number of Web authentication plug-ins and various levels of authentication strength, requiring one of many authentication factors:
- SSL Client Certificate Verification–Strong authentication using a public key infrastructure certificate. The client's SSL Certificate is verified by the Web server. The user name is extracted from the certificate and used for authorization via LDAP.
- SSL Certificate Lookup–The user is authenticated by looking up custom parts of the client's SSL Certificate via LDAP. The certificate is not verified, but it must be valid.
- LDAP Authentication–The user is authenticated against an LDAP server by entering a username and password.
- Standard Web Authentication–The user is authenticated as a local user by entering a username and password.
Secure export to CMDB
The preferred communication between BMC Discovery and BMC CMDB uses the CMDB REST API, and for this, we recommend using HTTPS rather than HTTP.
The legacy CMDB API is still supported, though the CMDB REST API access mechanism is preferred as it uses a more secure encryption protocol.
Ports used for System Communication
The following ports are used by the BMC Discovery and you might need to open them on a firewall for correct operation. These will be required in addition to the ports directly used for Network ports used for discovery communications.
Incoming Appliance User Interface ports
These ports need to be open to access the UI and CLI for both normal operation and administration of updates. HTTPS in BMC Discovery only accepts TLS v1.2.
The appliance accepts incoming client connections on the following ports:
Appliance CLI access
Main UI Secure
HTTP access to the appliance is not permitted.
Incoming / Outgoing Appliance port for communication with the BMC Discovery Outpost
See Security of communication and data between BMC Discovery Outpost and appliance.
Main BMC Discovery Outpost
Incoming / Outgoing Appliance Consolidation port
Consolidation uses TLS communication. The scanning appliances connect to the consolidation appliance using TLS 1.2 to transfer CORBA messages:
Incoming / Outgoing Appliance Clustering ports
Clusters use TLS communication to communicate between members. All members of the cluster both create outgoing connections to these ports and accept incoming connections on them:
Outgoing Appliance Service ports
These ports will be used in general operation. If configured, email alerts will be sent under certain conditions and an SMTP relay needs to be accessible to do this. As part of discovery the current domain names of IPs will be looked up, so access to your DNS infrastructure is required for this to work. It is essential for correct operation of the system that accurate time is kept for timestamps and access to an NTP service might be required for this. If Active Directory (AD) or Lightweight Directory Access Protocol (LDAP) UI user authentication is required, then access to your AD or LDAP infrastructure is also required.
Domain Name Lookup
LDAP UI User Authentication
Secure LDAP UI User Authentication
Outgoing appliance backup ports (Windows server)
These ports are used for communication when you back up an appliance or cluster onto a Windows server.
DCE RPC Endpoint Manager.
Appliance backup to Windows server
Netbios Session Service
Appliance backup to Windows server
|445||Microsoft Directory Services SMB|
Appliance backup to Windows server
Outgoing Appliance CMDB Sync ports
The BMC Remedy CMDB is built on the AR System platform, which uses a portmapper approach to do RPC calls in much the same way that WMI access occurs. As such, unless action is taken the ports used are 111 to contact the portmapper and an ephemeral port is used for the duration of the connection. You are advised to avoid having a firewall between the appliance and the CMDB unless your CMDB is set to use a fixed port by setting the ARTCPPORT variable.
The BMC Discovery appliance can also sync to the BMC Remedy CMDB using the REST API.
|8443||AR System REST API||CMDB sync|
Incoming Windows Proxy / Outgoing Appliance ports
The Windows proxies listen for incoming connections from appliances. Communication uses TLS 1.2 connections containing CORBA messages. You can configure the ports by using the Windows Proxy Manager. The default port numbers are:
|Active Directory Proxy|
|4322||TLS/CORBA||Obsolete Workgroup Proxy|
Log in or register to comment.