[ Update, 21-May-2016: Maintenance is now complete ]
On Saturday, 21-May–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 after the maintenance is complete. There is no customer nor end user action required.
In addition to a number of internal improvements, this maintenance window will address:
- We’ve updated Anti-Malware scan configuration screen layout to improve usability.
- Deep Security can now connect to Azure using the Resource Manager interface, which allows Cloud Service including Web Role and Worker Role to be displayed in the Deep Security Manager console.
- If an account does not have a User with a valid email address set as the Primary Contact the next time you log in you will be prompted to provide a valid email address.
- New alert has been added to notify of an Azure virtual machine that is not mapped to an Azure cloud connector.
- AMI’s containing activated Deep Security Agents will now automatically re-activate when new EC2 instances are created from that AMI.
- The platform field will now show the correct operating system when Windows 2016 is being used.
- Fixed and issue where UTF-8 characters were not being properly displayed in reports when opened in Excel.
If you have any questions about this update, please get in touch with us by clicking Support > Contact Support from within the DSaaS console.