[ Update, 7-May-2016: Maintenance is now complete ]

Updated 30-Apr-2016 at 11:10 AM EDT (UTC -4)
We’ve decided to push the original maintenance window (10:00–12:00 EDT (UTC -4)) one week to 07-May.

While preparing to deploy to production we noticed some performance and stability issues that require further investigation. We want to make sure that we continue to provide a high level of service so we decided to hold off deploying the planned enhancements.


Original Maintenance Notice

On Saturday, 30-Apr–2016, we will be upgrading the Deep Security Manager and completing some operational tasks on Deep Security as a Service (DSaaS).

The maintenance window is scheduled for approximately 2 hours between 10:00 to 12:00 EDT (UTC –4). Our goal during this window is to improve the overall service experience.

No impact to protection

During the maintenance window, your existing, activated agents will continue to provide the protection you expect from Deep Security. Events are automatically queued and will be accessible from the Deep Security Manager (DSM) after the maintenance is complete. There is no customer nor end user action required.

Improvements

In addition to a number of internal improvements, this maintenance window will address:

  • AWS instances added to DSM will automatically be moved to an appropriate AWS cloud connector.
  • Deep Security can now connect to Azure via the Resource Manager allowing both Classic and Resource Manager virtual machines to be displayed in the Deep Security Manager console.
  • Japan has been re-listed in the “Country” field of the DSaaS Sign-up page.
  • New DSaaS accounts will now accurately reflect the timezone selected during account creation.
  • Deep Security Agent scan configuration settings are no longer truncated in certain browsers.

Questions?

If you have any questions about this update, please get in touch with us by clicking Support > Contact Support from within the DSaaS console.