Cyber Recovery includes the security of networked subsystems and interfaces.
Communication security settings
The following table provides the required and optional external network ports for the
Cyber Recovery deployment. External ports enable remote connections.
NOTE:
The table includes generalized recommendations that are based on standard ports and services. Your deployment might use nonstandard ports.
Disable all network ports and interfaces that are not required for your environment.
Table 1. Network portsThis table lists the TCP ports, indicating if they are required, the associated service, and the direction.
Ports
Protocols
Purpose
Description
Direction
Required
22
TCP
SSH
Provides bi-directional communication between the SSH client and the remote systems in the
Cyber Recovery vault.
Inbound
Yes
25
TCP
Notifications
Used for SMTP email notifications about alerts and events.
Outbound
Optional
111
TCP
NFS Client
Used to perform NFS mounts between the
DD system and the
Cyber Recovery management host.
Bi-directional
Yes
123
UDP
NTP
Controls the time synchronization of
Cyber Recovery to another reference time source.
Bi-directional
No
14777
TCP
Nginx
Provides web browsers with HTTPS access to the
Cyber Recovery UI.
Inbound
Yes
14778
TCP
REST API
Provides the HTTPS connection for the user and UI REST interface.
Inbound
Yes
14780
TCP
Swagger
Provides access to the
Cyber Recovery REST API documentation.
Inbound
Optional
2049
TCP
NFS Client
Used to perform NFS mounts between the
DD system and the
Cyber Recovery management host.
Bi-directional
Yes
2052
TCP
NFS Client
Used to mount to the
DD system.
Bi-directional
Yes
NOTE:If you use NFSv4 on your
DD system, ensure that the
NFSv4 ID Map Out Numeric option is set to
always.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\