cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
594
Views
0
Helpful
4
Replies

AsyncOS 5.6.0 for Web is now Generally Available

chhaag
Beginner
Beginner

I am pleased to announce the "GA" release of 5.6.0. Code named "Maui" internally, this release is primarily focused on core proxy functionality. We have had great feedback from our beta testers and early adopters. I encourage customers to give 5.6.0 a try.

A few notes:

We have changed the way policies work and also added a new authentication layer called "identities". After upgrade we strongly recommend customers verify the post upgrade configuration to ensure policies and identities have been migrated appropriately to match your business needs.

If HTTPS was enabled and then is disabled at the time of upgrade, any archived decryption policies will not be maintained during the upgrade.

To enhance the security of the WSA, we explicitly prevent the WSA from proxying requests on the P2 interface. Customers who need this functionality may want to wait for the 5.6.2 release, which will support this configuration.

New Features in 5.6.0

* New Feature: Multi-core scanning (for improved performance)
* New Feature: Time-based policies for URL filtering
* New Feature: Enhanced routing policies (failover, load balancing, and conditional routing to multiple upstream proxies)
* New Feature: User-agent based policies
* New Feature: Policy trace tool
* New Feature: Custom EUN pages
* New Feature: SNMP enhancements (SNMPv1, 2, and 3, with support for traps and community strings)
* New Feature: Transparent bypass list
* New Feature: PAC file hosting
* New Feature: Active mode FTP over HTTP
* New Feature: GUI-based packet capture

Let us know what you think.

Regards,

Chris Haag
Manager, Technical Support

4 Replies 4

jowolfer
Beginner
Beginner

Thanks for the heads up. The 5.6 release is great! I'm enjoying the new Identity policies.

It does take getting used to, but in the end, you have much better control over authentication.

thomascollins
Participant
Participant

Agreed, 5.6 is excellent.

One comment about identities: Shouldn't the users be listed in the identity, not the Access Policy? For example, all my users come from a domain called CORP.

Then let's say I need an Access Policy that lets CORP\spresley get to financial sites. Then other Access Policy that lets CORP\jsmith get to streaming sites.

I need two identical identity policies that just say the authentication is CORP. Then in the access policies I limit the users. It would seem the user limiting should be done in the Identity Policy.

Looking forward to Continue Pages in 6.0

Doc_ironport
Beginner
Beginner