Security Controls

Architecture Considerations

Security Controls is extremely scalable. You can use it in its most basic state immediately after installation to perform a number of agentless operations. If needed, you can choose to implement a number of different architectural features to accommodate large and complex environments. Review the following list and click the provided links to learn more about each feature.

Agentless: Allows you to perform scans and deploy patches immediately after you install the ISeC console. Used to manage Windows-based networked machines. Can be used to deploy Microsoft and 3rd party vendor patches.

Agent-based: Agents can be installed on both Windows and Linux machines.

Windows environment: Agents are frequently used on disconnected machines and machines that reside in a DMZ. Agents are required in order to use Application Control.

Linux environment: Agents are required in order to perform patch management tasks.

Distribution Servers: Used at remote office locations.

Remote ISeC Consoles: Used within disparate geographic locations and managed regions.

Data Rollup: A central console receives data about machines managed by remote consoles.

Protect Cloud: Enables your agents to check in and receive policy updates from the cloud.

Disconnected Environments: A remote console that is located in a network that does not have internet access.

The following diagram illustrates a number of these architectural features.


Was this article useful?