Time to test the UTM Web Filtering feature.
The first thing to know is that there are 4 different ways to do this on the SRX.
1) Surfcontrol - This is know as Integrated Web Filtering and uses a cloud based Surfcontrol server to categorise URLs. This option requires a license and of course you can test with the 30 day trial license. The cloud based Surfcontrol server doesn't permit or deny anything. When queried by the SRX it provides a category that is permitted or denied by the policy you create on the SRX. The URL-to-category site results from the Surfcontrol server are cached locally which means subsequent requests for the same site don't require a lookup on the Surfcontrol server. This is a sensible approach as it means you dont have to download the whole database from Surfcontrol every time you start the SRX - it just requests the info from Surfcontrol on as as needed realtime basis.
Note: Surfcontrol is now owned by Websense though Juniper still name this option as Surfcontrol.
2) Enhanced Web Filtering - This is another type of Integrated solution which uses the Websense ThreatSeeker Cloud (TSC). Similar to Surfcontrol option above it provides a cattergory for the site to be checked but in addition also provides a reputation for the site.
A license is required for this option.
Juniper consider this option "next-generation URL filtering solution, building upon the existing SurfControl solution".
3) Websense - This is known Redirect Web Filtering and uses your local Websense server. This option does not require a licence. The main difference here to the Surfcontrol option is the the Websense server itself, through its own polices is doing the denying or permitting.
4) Local lists. This option uses local black and white lists to permit or deny access to URLs. No license required.
In this post I will configure and test the Local lists
This post will show you how to get IDP on an SRX100H going and tested to be working.
I will be using a Trial licence which is valid for 30days.
1) GET AND INSTALL THE IDP LICENSE
a) First make sure you can ping a URL from your SRX as the download process will use name lookups.
blogger@LEFTY> ping www.juniper.net inet
PING e1824.dscb.akamaiedge.net (22.214.171.124): 56 data bytes
64 bytes from 126.96.36.199: icmp_seq=0 ttl=54 time=33.373 ms
64 bytes from 188.8.131.52: icmp_seq=1 ttl=54 time=30.299 ms
64 bytes from 184.108.40.206: icmp_seq=2 ttl=54 time=29.531 ms
--- e1824.dscb.akamaiedge.net ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 29.531/31.068/33.373/1.660 ms
If that doesn’t work, setup name servers in the config.