No hay notas en la diapositiva.
There are 30+ new enhancements in ZLD v2.20, for example: Support EPS (End Point Security) check Windows 7 ready Support MS AD group Support capturing packet in the USG device We also improve those most-concerned issues: Routing problem, packets go to nowhere because those packets was routed by matching direct route rule, not policy route rule. Dual WAN deployment did not work well because policy route rule did not linking to the interface link up/down status. Inconveniently to deploy many 1-to-1 NAT configuration NAT Loopback design did not fit for customer’s wishes Not support Microsoft AD group
Check if IPSec VPN could work (yes) Check EPS error message could be customized. (yes)
http://www.computerworld.com/s/article/9135795/Study_Facebook_use_cuts_productivity_at_work The original motive of social websites, such as Facebook or LinkedIn, is to connect people, to share information, or to exchange experience through the website. But, the design of social websites is not secure enough, and hackers could easily stole personal information from there. For security concern, we suggest the behavior of accessing social websites should be restricted. Deploy ZyWALL USG as a gateway to block social websites. Blocking Facebook Blocking Plurk Blocking Twitter Blocking youtube Blocking myspace
Check with Lionic, and figure out what can USG do… Lionic did not feedback yet. (11/12)
Virtual Device Easy to monitor what you care (the device status) Customizable Dashboard Easy to change what you see (personalized GUI looking) Object Reference Easy to find out what you need (used objects) User Friendly Table Operation Easy to sort as your wish
Users complained about routing: Why bother to create “policy route” for the following scenarios: NAT 1:1 mapping NAT loopback LAN/WAN traffic routing Site to Site VPN When I setup a policy router rule, why it does not work? Policy route rule did not match because of lower priority than direct route Now ZLD v2.20 fix them all Support policy route auto-creation Change policy route priority higher than direct route
When deploying USG to SMB/Enterprise environment, administrators will leverage existing directory server to manage users. In ZLD current design, grouping of external users is not user-friendly – USG used a big group to represent all external users, and group members must be manually-keyed in. ZLD v2.20 support real MS/AD user group Support as many scenarios as possible. (see next page) Need as few configuration steps as possible. Support user could use at most two different identifiers to login. E.g. use “name” or “e-mail address” to login. Support AAA user setting test, MIS could verify if setting is correct.
Add: History 3G card list