API Access Monitoring
In many large organizations, multiple groups want to have access to the API of private clouds and various other sensitive systems. Access control and tracking are difficult, making system owners hesitant to provide access, and potentially vulnerable if too much access is granted for a user. With Pliant, you can easily allow access on a per-user, per API call basis and abstract credentials so you can allow control without sharing passwords or keys.
Pliant Acts as an API Gateway to Keep Access Keys Safe.
Pliant provides per-user-role access control down to individual calls, tracks API execution, can be used to throttle and most importantly tracks every successful and unsuccessful access attempt.
Further, Pliant sandboxes API keys so users never actually see the key nor interact with it. Thus if an employee or contractor leaves, they would not be able to use the key.
Obfuscate Credentials
Obfuscate credentials such as passwords and API keys from users while still allowing them to use APIs and login information to access systems. This enables a broader set of employees to interact with the system without giving them the “keys to the kingdom”.
Limit Access on a per-API call basis
By limiting the API access an individual has based on his or her role, organizations leverage Pliant as a single point of enforcement into the infrastructure. Users are given read or view access on a per API call basis to ensure they can access only the calls needed to do their job and nothing more.
Monitor Access to Infrastructure
Easily monitor and audit API access to infrastructure with Pliant, as every single API call is logged and available for compliance auditing at a later date.
Allow Root Access Without Risking Your Critical Infrastructure.
One user wanted to pull certain stats from an OpenStack deployment. However, they found that to do so, the user collecting the stats would need near root permissions and a username/password that would essentially give them access to perform any function in the OpenStack environment.
With Pliant, the administrator allowed the user limited root access by only allowing the individual API calls the user needed to complete the task. The user was then able to create automated workflows without knowing the usernames and passwords to systems. This user could then execute API calls to extract needed data – and then load this data into a network management system in an automated fashion with Pliant.
