
In our environment, we managed a mix of corporate and remote devices used by operational teams handling fintech and healthcare-related workflows, including customer support access, reporting systems, teleconsultation tools, and internal operational platforms. One of the biggest challenges before implementing MaaS360 was maintaining consistent security policies and access governance across different device types and user groups.
What stood out immediately was the centralized control and policy management. Device enrollment, application governance, access restrictions, remote security enforcement, and compliance monitoring could all be managed from a single operational layer instead of relying on separate administrative workflows.
Another major advantage was visibility into endpoint compliance and security posture. During audit reviews and operational security checks, infrastructure and compliance teams could quickly identify non-compliant devices, outdated policies, or risky access behavior without manually reconciling data across multiple systems. Review collected by and hosted on G2.com.
One thing I disliked about IBM MaaS360 is that while the platform is very strong from a security and governance perspective, managing large-scale device environments can sometimes feel operationally complex, especially during advanced policy customization and troubleshooting workflows.
From a UI/UX standpoint, the platform is functional and enterprise-oriented, but some administrative workflows still feel more infrastructure-focused than modern and streamlined. Teams unfamiliar with enterprise mobility management platforms initially faced a noticeable learning curve, particularly around advanced configuration areas and policy hierarchy management.
Another challenge involved troubleshooting device-specific behavior across mixed environments. Managing policy consistency across different operating systems, device manufacturers, and remote user scenarios occasionally introduced operational complexity during rollout and update cycles.
We also found that integrating MaaS360 deeply into evolving identity management, security monitoring, and zero-trust workflows required ongoing operational alignment and careful governance planning. Review collected by and hosted on G2.com.