1.6 Implementation Checklist

Use the following checklist to plan, install, and configure Change Guardian.

If you are upgrading from a previous version of Change Guardian, do not use this checklist. For information about upgrading, see Section 6.0, Upgrading Change Guardian.

 

Checklist Items

If you have purchased Change Guardian, ensure that you have the following license keys:

  • Change Guardian server

  • Change Guardian Module Keys

  • NCC channel registration codes (only for appliance installations)

If you have not yet purchased Change Guardian, you may use the 60-day built-in trial license. For more information about licensing, see Section 2.0, Understanding License Information. Contact your Sales Associate for further assistance.

Determine whether you want to perform a traditional or appliance installation of the Change Guardian server. For more information, see Section 4.0, Installing the Change Guardian Server.

Ensure the Change Guardian server is up and running by issuing the following command:

netstat -an | grep LISTEN | grep 8443

Ensure that the following line is not commented in the /etc/hosts file:

127.0.0.1 localhost

Synchronize the time on your Change Guardian server and monitored computers by using the Network Time Protocol (NTP).

Verify whether the Change Guardian web console can connect to the server by specifying the following URL in your web browser:

https:// IP_Address_Change_Guardian_server :8443

Install the Change Guardian Policy Editor. For more information, see Installing the Policy Editor.

(Conditional) If you want to monitor events on UNIX computers, you can deploy and configure the Security Agent for UNIX using the following:

  • UNIX Agent Manager (UAM)

  • Change Guardian Agent Manager (CG AM)

For more information, see Security Agent for UNIX Configuration and Installation Guide.

(Conditional) If you want to monitor events on Windows computers, install the Windows agent. For more information, see Section 5.0, Installing the Change Guardian Components.

(Conditional) If you change the IP address of the Change Guardian server, there is a break down of communication between the server and agent. This requires reconfiguration of the server to restore communication. Therefore, it is recommended to use static IP addresses in your Change Guardian deployment.