One of the biggest benefits of cloud computing is the level of accessibility it enables – from anywhere, and at any time. However, it is important to set up certain restrictions in order to protect your sensitive applications and privileged user accounts from being compromised.

One such important security measure involves setting up a device policy within your organization.

What is a device policy?

In essence, a device policy is a set of rules that users are to follow within an organization in order to prevent accidental or intentional compromise of company data. A device policy gives administrators better control over what can and cannot be done by end users, especially with regard to how they use company-owned devices as well as their own personal devices to access company applications and data.

A device policy is important because it limits user access to one or more critical applications and protects your network against potential threats from unauthorized access.

Akku’s device-based restriction

Akku, the Identity and Access Management (IAM) solution from CloudNow, comes with a device-based restriction through which you can:

      • Prevent access to sensitive applications from non-company-owned devices
      • Protect privileged user IDs and admin IDs – by allowing them to be accessed only from recognized devices
      • Maintain filters for company-owned devices even outside the local network

Here’s how Akku’s device-based functionality works.

Certificate-based Authentication

Akku uses a certificate-based authentication method which is platform- and browser-agnostic. When users, for whom device-based restrictions are to be implemented, log in to their applications through Akku (the identity provider) for the first time, a downloadable self-signed certificate by Akku is sent to the user along with a one-time password.

Whichever device this certificate has been downloaded in, it will be considered the default device for the user and the user will not be able to log in using any other device.

Tamper-proof Technology

Content filters – website filtering, YouTube filtering, personal email filtering, and so on – that have been set up for the user are automatically applied to their device where the certificate is installed. Even if the device is taken outside the office network, the same filters will continue to apply.

Once installed, the certificate cannot be reused or downloaded again and, therefore, cannot be installed on another device without admin intervention. This prevents any attempt by users to bypass the restriction.

With Akku, you can also set up IP-based restrictions, location-based restrictions, and time-based restrictions as well. In short, Akku can help you leverage the cloud while letting you stay in complete control. To know how these functionalities work, book a demo today! 

SatyaDev Addeppally

SatyaDev Addeppally is the Chief Technology Officer at Akku, where he drives technology strategy and product innovation for the company’s enterprise IAM platform. With a hands-on approach and deep technical expertise, he inspires his teams to build solutions that balance security, scalability, and usability. Under his leadership, Akku continues to evolve as a cutting-edge platform capable of competing with global leaders in the IAM space. Before joining Akku, SatyaDev held leadership roles at BPA Technologies, Raqmiyat, Nihilent, and FCS Software Solutions, managing enterprise-scale projects across BFSI, healthcare, ERP, and hospitality domains. His work in application modernization, digital transformation, and enterprise architecture has enabled organizations worldwide to strengthen IT infrastructure and accelerate growth.

Share
Published by
SatyaDev Addeppally

Recent Posts

IRDAI Item 10: Dormant Account Controls and the Automated Deprovisioning Requirement

Introduction IRDAI ICS Annexure III Item 10 requires that user accounts inactive beyond a defined…

1 month ago

ISO 27001 A.5.18 Access Reviews: How to Implement With Structured Evidence

Introduction ISO 27001:2022 Annex A.5.18 requires that access rights be reviewed at regular intervals and…

1 month ago

SOC 2 CC5.1 Segregation of Duties: What Technical Enforcement Requires

Introduction SOC 2 Trust Services Criteria CC5.1 requires that the entity selects and develops control…

1 month ago

SEBI CSCRF and Qualified REs: What Higher-Tier Entities Must Implement

Introduction SEBI CSCRF applies to all regulated entities but differentiates requirements by entity tier. Market…

1 month ago

Dormant Account Controls Under SEBI CSCRF: The Access Hygiene Requirement

Introduction SEBI CSCRF PR.AA.S1(G1g) and PR.AA.S1(G1h) require that user accounts inactive beyond a defined threshold…

2 months ago

ISO 27001 A.8.2: Privileged Access Management Requirements and Implementation

Introduction ISO 27001:2022 Annex A.8.2 requires that the allocation and use of privileged access rights…

2 months ago