Best Practices

In this article, we are going to map some of Akeyless best practices related to both performance and security.

Glossary

Superuser - The user who signed up for Akeyless and owns the account.

RBAC - Akeyless Role Based Access Control.

CSP IAM - Cloud Service Provider Identity and access management.

Customer Fragment - Zero Knowledge Akeyless unique encryption patented technology.

SRA Bastion - Akeyless Secure Remote Access Bastion.

Akeyless Vault platform

  • Do not run as a superuser for general purposes. An akeyless superuser should generate a very strong and long password. The superuser should be used to set up the system initially, particularly for setting up the selected admin users who will be part of your admin role. Those admin users will create the authentication methods so regular users will be able to authenticate.

  • Avoid API Key Authentication on production - Due to the secret zero problem and management challenges, Universal Identity should be used on production for on-premise environments or any CSP IAM on cloud environments for workloads or automated services, as well as SAML or OIDC for human access.

  • Authentication Methods - Shared authentication methods such as SAML, OIDC, LDAP, IAM, JWT, or K8s should be used with sub-claims on role association to avoid mistakes and overriding existing access roles.

  • Access Roles (RBAC) - In general, regular users do not have permission to change their Access Role or Authentication method settings. Make sure your Access Roles are not granting regular users permission to view or create neither Access Roles nor Authentication methods. In addition, avoid creating multiple different Access Roles with a single path. Instead, create an access role for multiple paths.

  • Audit & Analytics - On access roles, it's recommended to let your users view their analytics and logs rather than providing them broader permissions to view your account's entire audit logs and analytics.

Items

  • Storing item - Items location inside Akeyless Vault should not be saved on the default root path, i.e., /. The recommended mode is to create those items under the relevant tree folders that describe the exact unit in your organization. This will enable easier and clearer tenant management.

  • SSH certificates - Should not be set with * on the principals field. Instead, this field should be utilized for special use cases where your users need special permissions. In addition, SSH certificates should be used with a list of allowed users who will be able to log in using those certificates.

  • Dynamic Secrets - Should be used and set while following the Principle Of List Privileges (PoLP). Each dynamic secret has its permission profile which will determine your temporary users' access level.
    E.g., Databases Dynamic secret should be used with the minimum permissions for your users based on the creation statement, where you should limit the access to a specific database and table.

CREATE USER '{{name}}'@'%' IDENTIFIED WITH mysql_native_password BY '{{password}}' PASSWORD EXPIRE INTERVAL 30 DAY;GRANT SELECT ON <DATABASE NAME>.<TABLE_NAME> TO '{{name}}'@'%';
  • Rotated Secrets - This should be used as a break glass admin static credentials, which should automatically rotate strong users' passwords. Primarily for your super users, which their passwords should be rotated automatically.

  • Targets - To save time during Dynamic and Rotated secrets creation and avoid using your privileged user credentials often, you can create Targets.
    Those items should not be shared with regular users, while those who need to use the Targets items can only have 'list' permissions.


Did this page help you?