Secure Shell Communications

To use Secure Shell Communications, follow these steps:

Select option 2 on the IPSec Communications menu to access the Secure Shell Communications screen. This screen allows you to select up to three levels of security.
Select options 1-High (Telnet and FTP disabled), 2-Medium (Telnet disabled), or 3-Low (insecure services available).
Exit to return to the Secure Shell screen.
Select option 2 to access the Manage Secure Shell Known Hosts screen. The SSH client keeps a list of hosts it has connected to. Keys become invalid when keys are moved to different IP address or regenerated. The invalid information needs to be purged for further communication.
Choose a user with a known_hosts file.
Exit to return to the Secure Shell screen.
Select option 3 to access the Host Key Operations screen.
Here you have two options, 1-Delete host key and generate a new one, or 2-Delete host key. Make your selection. With key pairs, you need a public and a private key. The encrypted messages can only be decrypted with the proper key. The server generates the host key pair when the server is first started. Regenerate the key if it becomes suspect. If the key is regenerated, all the hosts that have communicated with the server will have to have the old key pair cleared from their cache in order to communicate in the future.
Exit and reboot.

Note
IPSec is resource-intensive on the sensor. Excessive processing due to IPSec can cause intrusion alarms to go undetected and ultimately unreported.