120 likes | 356 Views
Zoran AKA Zscaler Project AKA Project Scrubber Project Update Pack 1. Index: Zscaler Project Detailed Requirements Solution AU & NZ Solution Global Scope, Constraints & Assumptions Deployment Timeline Noteworthy points Appendix 1: Rule sets to be enforced
E N D
Zoran AKA Zscaler ProjectAKA Project ScrubberProject Update Pack 1 Index: • ZscalerProject • Detailed Requirements • Solution AU & NZ • Solution Global • Scope, Constraints & Assumptions • Deployment Timeline • Noteworthy points • Appendix 1: Rule sets to be enforced • Appendix 2: Policy Exclusion Process Zoran Island, Phuket, Thailand
ZscalerProject Mission Statement Establish a common web filtering and monitoring platform High Level Requirements • Clientless • Centrally ‘located’ • De-Centralised Manageable • Reduction in IS managed infrastructure • Common rule set
Solution AU & NZ (logical flow) • Client configured to Auto detect Proxy setting\ • Central PAC (WPAD) file directs traffic to trusted sites to Squid Proxy • All other traffic to zScaler where user will be authenticated (login or cookie)
Solution Global (logical flow) • Central PAC (WPAD) file directs all traffic to zScaler(gateway.zscaler.net:80) • No user authentication
Scope, Constraints & Assumptions • Scope; • IE browser • PC and Laptops on Windows OS only • Enforcement and or traceability of adherence to Group Web Usage Policy • Starting with a ‘clean slate’ by not bringing across hundreds of ‘old’ and undocumented rules • Universal PAC (WPAD) file for all regions • Deployment limited to AU, NZ, UK, US and HK • Constraints; • Resource availability • Users without email address can not access non trusted sites (AU & NZ only)
Scope, Constraints & Assumptions cont’d • Assumptions; • Trusted sites list to be defined ‘out side’ of Project • Internal resources are available as scheduled • Minimal calls to Service Desk • ‘Regional’ Assumptions; • Australia & NZ • All Desktops are MOEd and will accept Group Policies • All users arein AD • User have email addresses (for access to ‘non trusted’ sites) • Global • All PCs will accept Group Policies • Root certificates (HTTPS) can be deployed to desktops • All Desktops are on IE7 or above
Deployment Timeline Highlights • Melbourne HO will be on Zscaler by 27/8 • Australia by 9/9 • NZ by 13/9 • Global by October (TBC) *Timing for Global deployment is indicative and subject to confirmation with and acceptance by regional IS and Business
Noteworthy points • Plan has been developed with the assistance of and agreed to the IS team • Melbourne HO on line with Zscaler by 27/8 is achievable • AU and NZ online with Zscaler by 13/9 is achievable • Global deployment by October is feasible but subject to further planning and agreement • PAC file is universal and same version (multiple instances) of file will be used by ALL regions • PAC file is modular, documented and readily configurable should the need arise • PAC file will be accessed as a WPAD and defined via DNS • Proxy settings will be deployed via Group Policy • As AD.Internal is rolled out PAC file will be centralised and regional instances removed
Appendix 1:Rule sets to be enforced • Adult Material • Drugs • Gambling • Violence • Weapons/Bombs • Tasteless • Militancy/Hate and Extremism • Illegal or Questionable • Games • Internet Communication • Peer to Peer Site • Security • Society and Lifestyle • Social Networking (i.e. Facebook etc.)