How Location Properties Work

Each agent, on which the CPM client resides, receives a complete list of all the Actions deployed from the server through the various Tasks. The individual Agents check themselves against the list and create a short-list of only those Actions that apply to them. In the current example, relevance is determined by IP address. Configuration 1 is going to be deployed to all Agents, but only those Agents running on an endpoint with an IP address in the subnet defined for San Francisco will pick up the configuration. You will be able to see this self-selection at work when you create the second configuration and apply it to a different Location. One Action will be picked up by San Francisco endpoints and the other by German endpoints.

Agents remain in sync with new relevance expressions by frequently checking the server for updates. Agents also maintain a detailed description of themselves that may include hundreds of values describing their hardware, the network, and software.

In short:

• First, define some locations.

• Second, configure your scan, firewall, or URL filtering settings.

• Next, save the settings to a Task and create an Action to target some given endpoints.

When you deploy the Task, the server converts the Action details into a relevance expression, which is sent to all Agents at the endpoints. Each Agent checks itself against the relevance expression and takes the Action required for every match found.