content-filtering (Security Content Security Policy)
Syntax
content-filtering {
rule-set name {
rule name {
match {
applications [applications];
direction (any | download | upload);
file-types [file-types];
}
then {
action (block | close-client | close-client-and-server | close-server | no-action);
notification {
endpoint {
custom-message custom-message;
(notify-mail-sender | no-notify-mail-sender);
type (message | protocol-only);
}
log;
}
}
}
}
}Hierarchy Level
[edit security utm utm-policy policy-name] [edit logical-systems logical-systems-name security utm utm-policy policy-name] [edit tenants tenant-name security utm utm-policy policy-name]
Description
Configures a Content Security policy for the content filtering protocols and attach this policy to a security profile to implement it. Each supported protocol may implement available content filters differently. Not all filtering capabilities are supported for each protocol. The HTTP protocol supports all content filtering features. The FTP protocol supports only lock Extension List and Protocol Command Block List. The e-mail protocols (SMTP, IMAP, POP3) supports limited to Block Extension List, Protocol Command Block List, and MIME Pattern Filtering.
Starting in Junos OS Release 21.4R1, content filtering is performed by detecting the
file content and not the file extensions. We have introduced the
rule-set and rules configurations under the [edit
security utm utm-policy <utm-policy-name> content-filtering]
hierarchy level. These rules and rule-set allows you to configure direction specific
content filters and connection reset.
So, 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.
Options
| rule-set name |
Name of the content filtering rule set. |
| rule name |
Name of the content filtering rule. |
| application |
List of applications to be inspected. |
| direction |
Direction of the content to be inspected (upload or download). |
| file-type |
List of file-types in match critera. |
| action |
Action to perform for the content filtering match condition. The possible options are:
|
| notification |
Notification for the content filtering action taken based on the rules configured. |
| endpoint |
Endpoint notification options for the content filtering action taken based on the rules configured. |
| type |
Endpoint notification type. |
| notify-mail-sender |
Notify mail sender. |
| no-notify-mail-sender |
Don't notify mail sender. |
| custom-message |
Custom notification message. |
| log |
Generate security event if content is blocked by rule. |
Required Privilege Level
security—To view this statement in the configuration.
security-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 9.5.
Support for configuration in logical systems introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1.
rule-set option introduced in Junos OS Release 21.4R1.