Symantec (Blue Coat)

This guide covers Symantec (formerly Blue Coat) ProxySG appliances and Security Gateways running SGOS.

Create a backup account

Create a dedicated administrative login — for example netwatch-backup — for CLI access, either as a local console account in the Management Console or through the authentication realm you use for administrators.

SGOS requires enabled (privileged) mode to display the full appliance configuration, so read-only console access alone is not sufficient. Make sure the account is permitted to enter enabled mode, and record the enable password — QUARK supplies it after login, exactly as an administrator would. QUARK only issues show and display operations; it never changes the configuration.

Enable SSH access

SGOS provides an SSH console as one of its management services, and it is normally enabled by default on port 22. Verify in the Management Console that the SSH console service is enabled on the management interface the collector will reach.

If your SGOS release lets you restrict management services by source address, limit the SSH console to the Netwatch collector's IP. Otherwise, restrict TCP port 22 to the collector with a firewall in front of the appliance.

Platform notes

• The enable password is separate from the account password; enter both when adding the device in QUARK.
• If administrators authenticate through an external realm, make sure the netwatch-backup account maps to a policy that allows CLI login and enabled mode.

Enable backup in Netwatch

Once the device is prepared, open its host in Netwatch (Data collection > Hosts) and add the Config Backup macros — the supported status flag, the model code for this platform, and the credentials you created. See Getting started for the full macro list and values.