We just released a new version of Gears! If you haven't been following our roadmap across America, it isn't too late to get up to speed on all of our new features. In this month's release, code name Tennessee, we sought to empower users to keep their devices compliant by alerting them with a popup remediation page. Compliant devices don’t always stay compliant, and therefore secured endpoints and networks don’t always remain secured. By reducing both the time and effort required to remediate a device, both device users and network administrators can better protect their shared network.
CODE NAME "Tennessee" includes:
- Remediation Page Auto Popup
- Usability Improvements for Adallom Integrations
- Gears is Now Compatible with Windows 10
- Other Fixes and Enhancements
Remediation Page Auto Popup
Administrators can kick back and relax as we have made it easier for users to maintain the security status of their managed and unmanaged devices. We know that maintaining the security status of all of the devices in your network is challenging since device configurations and security postures can constantly change. By empowering users to self-remediate their devices, this new feature saves admins time and helps them keep their endpoints secured. Now, Gears empowers users to maintain the compliance status of their devices by launching the remediation page the moment the device is no longer secure, providing instructions to the user on how to fix the issues.
This new feature is made possible by Gears' ongoing monitoring capabilities. Since Gears could already monitor device behavior in real-time, we thought it would be beneficial for the end user to be alerted through their browser about new security issues. This limits the time between the change in status and addressing the potential security issue. To start using the automatic remediation page pop-up, go to your account settings and enable the new option.
Click to Enlarge
Usability Improvements for Adallom Integrations
Integrating Gears with a cloud security program like Adallom can greatly improve the security of your cloud data, and we’ve made it even easier for users to self-remediate their device before accessing cloud based applications. We’ve removed a client certificate from prompting the user to identify their device during remediation in order to both limit confusion, and to reduce remediation time.
Client Certificate Step Eliminated
If you haven't already, watch our latest demonstration on how Gears and Adallom can be used together to protect against security risks inherent in cloud-based applications. The integration with Adallom is seamless, and adds an important layer of security to cloud application access.
Gears is Now Compatible with Windows 10
We are happy to announce that Gears is now compatible with Windows 10! Windows will be releasing the new operating system on July 29th, and we wanted to get all of our Gears administrators ready for the barrage of system updates. Though Gears is completely compatible with Windows 10, a configuration reporting option in the Gears dashboard is irrelevant for Windows 10 devices. The configuration option reports on whether or not automatic OS updates are enabled, but since security updates cannot be disabled in Windows 10, the reporting feature is unnecessary for Windows 10 devices.
Speaking of new releases, we will be unveiling our new Gears clients for Linux and Mobile (both Android and iOS) operating systems soon. If you would like a preview of our new software and application, please contact us and we will be happy to give you a demonstration!
Other Fixes and Enhancements
- Delete device button now removes persistent guest agent
- Fixed issue with infection reporting accuracy
- Miscellaneous UI improvements
- Consolidated two running processes
Known Issues
- Checking for automatic OS update status will return non-compliant for Windows 10. This should always return compliant and will be changed in the next release.
- Checking for third party patch management agent running status will not work if the agent is Windows Update Agent 10.x