Case Studies

Addressing the Data Security and Audit Worries of a Leading Manufacturer

Company X is a leading automotive hardware manufacturer. In the competitive manufacturing environment, documentation of activity are standardization of processes are critical requirements.

In the case of Company X, this was already in place, and in fact they had achieved ISO certifications for their process-based approach and class-leading quality.

However, certification brought with it a constant stream of audits to ensure that processes were in fact being followed, and standards maintained. This posed a recurring problem, since a single failed audit could result in the loss of certification and loss of business.

The employees of Company X were well equipped – every employee was given an email address, and employees above a certain grade were provided with a laptop and a smartphone as well. But being an ISO-certified enterprise, the security of devices and data were vital.

Diagnosis and Prognosis

Given the background and the critical business impact of a failed audit, potential problem areas were quickly identified, along with solutions.

One of the first problem areas that needed to be addressed was that many employees tended to set weak, easy-to-crack passwords that exposed the company to data security threats, while also failing to comply with ISO standards.

A strong, universal, standards-compliant password policy was necessary to ensure uniformly high security across user accounts.

A mandatory ISO-compliant password policy for all users could easily be set up with Akku.

The next point of concern was the possibility that sensitive business data could be compromised by employees.

The solution to this was to enable employees to access their company email accounts only from the devices provided by the company.

Akku enabled restricting access to company mail only from devices with its SSL Key installed.

Another issue identified was that website browsing restrictions were implemented only on the company’s firewall. Therefore, exposure of company devices to malware and external threats while outside the firewall was a looming worry.

A DNS filter to restrict browsing access even outside the firewall became essential.

Akku’s website filter provided this functionality with powerful control and ease of use. This helped to keep the company’s devices secure, whether they were located within the company firewall or not.

This type of device-based access control offered by Akku seemed to tick all the boxes, but it would fail to serve its purpose if it could be tampered with by a user.

Many legacy solutions built using plugins were found to be vulnerable to misuse – with these solutions, it was possible for users to find a way to circumvent the access control by simply removing the plugin to enable unrestricted access. The device could then be made to appear uncompromised by reinstalling the plugin later. Such a solution was far from water-tight.

With Akku on the other hand, the implementation of a certificate-based architecture overcame this potential challenge. This was because any attempt to tamper with Akku’s certificate would completely restrict access to their authorized services like official email and other SaaS-based applications. Reactivation would require a certificate password, available only with the systems admin.

By enabling easy identification of any attempts to evade the implemented access restrictions, potential leaks were plugged and accountability enforced.

Trial by Fire

The road to full implementation of Akku was a challenging one.

After the problem areas at Company X were identified and Akku was presented as the solution, a PoC was run successfully with 30 users to confirm that all requirements were in fact addressed completely.

With this first hurdle crossed, the client next proposed implementation and testing at their Japanese parent company. Stringent testing on every parameter of Akku’s performance was carried out over a period of several weeks in Japan.

At the end of this process, Akku was approved for the final roll-out across 300 users.

Bhaskar RV

Bhaskar is Product Lead at Akku, where he plays a key role in shaping the roadmap and development of our identity and access management platform. He collaborates closely with cross-functional teams to ensure that solutions are robust, scalable, and aligned with evolving customer needs. His focus is on driving innovation and continuous improvement to deliver maximum value to clients. Before Akku, Bhaskar worked as a System Administrator at Megha IT Consulting and Smilax Laboratories, where he managed IT infrastructure and enterprise systems, gaining strong hands-on experience in networks, servers, and application environments.

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…

4 weeks 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…

4 weeks 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…

1 month 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