Assigning custom Content Filter policies to local users based on local group membership.
This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. The below resolution is for customers using SonicOS 7.X firmware.
NOTE: CFS Premium version is required to create custom CFS policies.
Configuring Content Filter Policies


NOTE: If no local users or groups currently exist, refer to part 2 of this procedure to create local accounts. For LDAP accounts and CFS via LDAP, refer to Integration of LDAP and multiple/Custom CFS policies for different user groups - ULA + CFS + LDAP. 
TIP: To better understand the way in which Content Filtering 4.0 works, refer to the Content Filtering Service (CFS) 4.0 Overview - SonicOS 6.2.6 and above.Configure Local Users and Groups



Configure ULA Settings
EXAMPLE: If your users are located in the LAN off of X0, you will click configure next to the X0 Interface.

NOTE: LAN will need to be adjusted if your users are located in a different zone.
Action: Allow, Service: HTTP/HTTPS ,
Source: Any,
Destination: Any,
Users Included: Trusted Users,
Schedule: Always on

NOTE: By Specifying the Trusted Users group, you are forcing the SonicWall to determine if the user trying to access the web is a member of the trusted users group. (All users are members of the Trusted Users group, so it is a safe group too use in the Users Included field).
CAUTION: Once you click on "Add", all users trying to access an HTTP based web page, will now be redirected to a SonicWall login page. If you want users to log in when accessing other web services such as FTP or https, you will need to create a service group in: Firewall Services and add any services you wish to have users log into the SonicWall when accessing. After said group is created, you would use it in place of "HTTP" for the service option in the rule shown above.This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.
NOTE: CFS Premium version is required to create custom CFS policies.
Configuring Content Filter Policies


NOTE: If no local users or groups currently exist, refer to part 2 of this procedure to create local accounts. For LDAP accounts and CFS via LDAP, refer to Integration of LDAP and multiple/Custom CFS policies for different user groups - ULA + CFS + LDAP. 
TIP: To better understand the way in which Content Filtering 4.0 works, refer to the Content Filtering Service (CFS) 4.0 Overview - SonicOS 6.2.6 and above.Configure Local Users and Groups



Configure ULA Settings
EXAMPLE: If your users are located in the LAN off of X0, you will click configure next to the X0 Interface.

NOTE: LAN will need to be adjusted if your users are located in a different zone.

![]() | Action: Allow Source: Any Destination: Any Users Included: Trusted Users Schedule: Always on |
NOTE: By Specifying the Trusted Users group, you are forcing the SonicWall to determine if the user trying to access the web is a member of the trusted users group. (All users are members of the Trusted Users group, so it is a safe group too use in the Users Included field).
CAUTION: Once you click on "Add", all users trying to access an HTTP based web page, will now be redirected to a SonicWall login page. If you want users to log in when accessing other web services such as FTP or https, you will need to create a service group in: Firewall Services and add any services you wish to have users log into the SonicWall when accessing. After said group is created, you would use it in place of "HTTP" for the service option in the rule shown above.