Cloud Platform Release v23.7.0

Today we released a number of updates to our platform. Below are the details of these exciting enhancements.

• DNS Zone/Domain Restoration Feature: A significant feature released with this update is the ability to restore entire domains or even specific records within a domain to their prior state. On occasion a user will accidentally delete a domain (although we still can’t understand exactly how, but it does happen) or delete or update a record incorrectly and need to restore it to the prior setting. The new restore option on the Domains > DNS tab will allow you to choose the domain and select to restore it entirely, or choose specific record(s) you wish to restore. This is a powerful new feature that can provide added comfort when managing DNS.
  
  
  
  
• DNS Reporting/Charts: We released a number of changes to our DNS Reporting/Charts. We added reporting for new record types, we improved the performance, and we added the ability to expand the Query Rate table rows to show record hit/lookup detail per time period. We also resolved a back-end glitch that prevented newly added domains for gathering data as well as all DNS data from capturing for a couple of weeks in July. We apologize for that!
  
  
• Networking Stats: In this release we made a slight improvement to the performance of the networking/stats page (although we’re still working on improving it for users with millions of hits per day). We also improved the date range selection capability in the networking stats section to better allow choosing the exact data time period you wish to see. The prior method of a free-form date/time field did not validate entries well and often displayed incorrect data or no data at all. With these straightforward drop-down date range options, it consistently produces the right results for these reports.
  
  
• DDoS Statistics: We corrected an issue that was preventing DDoS attack data from properly charting for some customers. Many other customers also ask why these charts are often blank, and that’s actually a good thing! No attack data means no attack needed blocking, which is rather ideal, in our opinion.
  
  
• WAF Log Export: We corrected a bug with the WAF log export file to properly show data when certain data conditions were met. On occasion the export file would be blank, and this fix resolves that.
  
  
• Rate Limit Control: We made a correction to the rate limit control dialog in the ADC-as-a-Service public facing ports to correctly display long names and to support numerous additional rate-limiting options we recently added.
  
  
• Secure Cookies: We added a feature to Web Application and API Protection (WAAP) to force all cookies sent from a server to be optionally upgraded to secure. This will easily help make sites compliant.
  
  
• API User Logging & Security: As more and more customers automate changes and create an “API User” (a user that can have a specific role and cannot log into the UI) we upgraded how API users are managed and tracked. These users can now be restricted to only make API calls from allowed IP addresses (just like regular users) and we now also track and log every change made by the API user into the change log. While this has the potential to increase log data significantly, the information can be valuable for audit and compliance purposes.
  
  
• DUO and TLS 1.2: Per DUO’s request we locked DUO API calls to use a minimum of TLS 1.2 for enhanced security. Previously it would also use TLS 1.1 in some instances, and DUO has ceased TLS 1.1 support recently.
  
  
• U.K. Mobile Long Code Blocking: We made a change to comply with U.K. mobile operators to no longer show our international long code number for SMS messages. Mobile operators began blocking international long code SMS messages to cut down on spam. Inbound messages for 2FA or device up/down alerting will now display “TotalUptime” as the originator of the message to meet compliance requirements and improve deliverability.
  
  
• Improved Server Adding: We improved performance when adding new servers/devices into the ADC-as-a-Service section. When a new server/device is added, the IP is checked/validated on our back-end platform. We improved the speed of this validation process by about 2 seconds.
  
  
• Trial Email Suppression: We resolved a bug where some users who had canceled their trial or where their trial had expired still received marketing emails.
  
  

Please send us your feedback! As we continue to evolve our solution to be the leading ADC-as-a-Service platform, we want to know what you think. Tell us the good and the bad. Let us know what features you think we should have and which ones are a waste of time, buggy, or don’t make sense. The more feedback you give us, the better our product becomes because we really do listen! Please contact us! We love hearing from our customers.