Application Chambers apply to Applications; Chamber settings for individual Applications are managed from Chamber Policy Management > Application Chambering.
As Applications are scoped by App Profile, ensure you have selected the correct App Profile in the top menu bar before proceeding.
This view shows a quick summary of the Chamber Settings of the various Applications in the selected App Profile, and provides quick access to adjust the Security Control Level of individual Applications.
Editing Chamber Settings
Click the edit icon () to the right of the Application in order to bring up the Chamber edit view.
Silo Mode controls whether endpoints assigned to an Application may communicate with each other. This may be used to prevent intra-Application traffic for Applications that do not require it. For example, if an Application corresponds to a group of Apache web servers in a 3-tier web application, direct communication between the Apache servers would be considered unusual and may be reasonable to block.
Silo Mode is only active when the Security Control Level is set to Prevention. If the Security Control Level is set to Detection, intra-Application traffic will generate a Detection Violation, but will be allowed.
This provides a simple control for you to configure the behavior for outbound traffic from this Application.
Allow non-whitelisted Local Network + Internet connections
This setting creates a default allow for outbound traffic to any destination. It provides the least security, but is least disruptive to existing applications, and is the default setting.
Allow non-whitelisted Local Network connections
This setting creates a default allow for outbound traffic to any destination in RFC1918 space. This setting will block outbound traffic to the public Internet that is not specifically allowed by a Chamber Policy, or enabled through a ZTNA connection.
Deny all non-whitelisted connections
This is the most secure setting, and creates a default deny behavior for all traffic that is not specifically exempted by a Chamber Policy or by a ZTNA connection.
The Outbound Traffic setting is active when the Security Control Level is set to Prevention. If the Security Control Level is set to Detection, violating outbound traffic will generate a Detection Violation, but will be allowed.
The Chamber Policies section allows you to specify which Chamber Policy Objects or Chamber Policy Templates to apply to this Application. You may add a Chamber Policy Object/Template from the pick list by double-clicking it.
Chamber Policies are evaluated in order of precedence. You may change the order by dragging the Object/Template to the desired position in the Chamber Policy list.
The Learned Rules section provides a summary of all of the Learned rules for this Application, and provides controls to trigger or reset Learning.
Once you have completed configuring the Chamber settings, click Save.