Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


The UTM default configuration is used in two scenarios.

  • UTM default configuration for unified policies—For security policies that enable UTM with no custom UTM policy defined, the default UTM policy will be used.

  • UTM default configuration for existing UTM policies—For existing security policies that have a UTM policy enabled, the default UTM policy will NOT be used.



Global default UTM configurations.


Configure the default UTM configuration for antispam feature profile.


Configure the default UTM configuration for antivirus feature profile.


Configure the default UTM configuration for content filtering feature profile.


Configure the default UTM configuration for Web filtering feature profile.


Configure a UTM policy for antivirus, antispam, content filtering, traffic options, and Web filtering protocols and attach this policy to a security profile to implement it.


Define tracing operations for UTM features.


Configure UTM features, antivirus, antispam, content filtering, and Web filtering by creating feature profiles.


Application proxy settings.


Configure custom objects before configuring UTM feature-profile features. Custom category does not take precedence over predefined categories when it has the same name as one of the predefined categories. It is not recommended to have a custom category name be the same as the predefined category name.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

security—To view this statement in the configuration.

security-control—To add this statement to the configuration.

Release Information

Starting in Junos OS Release 21.4R1, the rule-set and rules configurations introduced under the [edit security utm utm-policy <utm-policy-name> content-filtering] hierarchy level can be used from [edit security utm default-configuration content-filtering hierarchy.

Content filtering options based on mime-type, content-type, and protocol command is not supported. After you upgrade to Junos OS Release 21.4R1, previously existing file extension based content filtering options under the [edit security utm utm-policy <utm-policy-name> content-filtering] hierarchy are no more available for configuration.

Junos OS Release 21.4R1 allows you to use legacy functionality if you don’t want to migrate to this modern functionality. You will be allowed to use the legacy configurations but all the legacy configuration knobs are deprecated and are hidden. Also, you will receive system logs and error message warnings when you use all the legacy deprecated knobs.

Statement introduced in Junos OS Release 18.2R1.