Security Controls

Protect Cloud Synchronization Requirements and Usage Notes


Must be running Security Controls Standard or Security Controls Advanced

Must have a Protect Cloud account

Applies only to agents that are configured to use Protect Cloud synchronization

The console must have a reliable Internet connection

Outgoing TCP ports 80 (http) and 443 (https) must be available when communicating with Protect Cloud

The URL must be accessible when communicating with Protect Cloud

Usage Notes

When using Protect Cloud synchronization, the agent check-in process is as follows: At the scheduled check-in time, the agent will attempt to check in with the console. If the agent can access the console it will check in directly with the console. If the agent does not have access to the console but it does have Internet access, it will perform the check-in using the cloud.

When a disconnected agent checks in with the cloud it reports the same information (scan results, etc.) that it would to the Security Controls console. Protect Cloud provides a generous amount of storage to cache results until the consoles retrieves the data. The console will automatically retrieve data from the cloud several times every hour.

Engine components and data files are not a part of the Protect Cloud synchronization process. Agents will continue to receive updated engines and data files from either the console or the vendor websites. If an agent is using a policy that specifies the use of a distribution server, it is strongly recommended that you enable the Use vendor as backup source check box.

A listening agent is treated no differently than any other agent. If a listening agent is on the local network and receives notice from the console that there is a policy change, it will receive the updated policy from the console. If a listening agent is away from the local network and unable to communicate with the console, it will perform its check-in using the cloud.

Was this article useful?