Where Awingu as a default runs in the browser ‘on any device’, it is hard to restrict access to specific end-points or the context of this end-point. This is where partner solutions such as OPSWAT MetaAccess come into play.
Businesses can leverage the MetaAccess solution on top of Awingu to guarantee compliance of their end-points.
MetaAccess is both a central admin platform (on-prem or cloud) and a local agent that can be installed on your end-point (such as Windows PC or an Apple Macbook).
Businesses can choose their desired minimum level of security on the end-point, and this could differ for BYOD (Bring Your Own Device) user-groups compared to users with company owned and managed devices.
When configured with Awingu, MetaAccess will act as a security context for Awingu. More specifically, when users attempt a login via the browser, Awingu will await feedback from the OPSWAT MetaAccess service. Only when MetaAccess provides a positive assessment will the user be enabled to access Awingu via the browser. This also implies that users in this setup will not be able to access Awingu from end-points that are not enabled with MetaAccess.
Do you have any more questions about Awingu? Reach out to our Awingurus!