What is the difference between tenant configuration modes in Push?

When setting up a Push team (tenant) for the first time, the first administrator can choose between two default configurations for the application:

Moderate: This configuration mode is optimized for rolling out Push for the first time in a production environment. In Moderate mode, the following settings are selected:

• Production detections are enabled. Experimental detections are not enabled.

• The Phishing tool detection control is set to Monitor mode. Detections will be raised in the platform but end-users will not be warned or blocked if a phishing page is detected.

• The Cloned login page detection control is set to Monitor mode. Detections will be raised in the platform but end-users will not be warned or blocked if a cloned login page is detected.

• The Password protection control is set to Monitor mode for SSO applications only. The reuse of protected SSO passwords will not be flagged on known work apps.

Aggressive: This configuration mode is optimized for testing Push, such as during an evaluation period like a proof of concept. In Aggressive mode, the following settings are selected:

• Both production and pre-release detections are enabled.

• The Phishing tool detection control is set to Warn mode. Detections will be raised in the platform and end-users will see a warning page if a phishing page is detected.

• The Cloned login page detection control is set to Warn mode. Detections will be raised in the platform and end-users will see a warning page if a cloned login page is detected.

• The Password protection control is set to Warn mode for all applications. End-users will see a warning page if they reuse a protected password on another app it does not belong to.

• The URL blocking control is set to block any links using URL schema obfuscation, a phishing technique.

You can adjust any of these settings in the Push admin console. Learn more about these controls in our documentation.