Overview
Managing credentials securely in Tines helps protect your integrations, reduce risk, and keep your tenant organized. These best practices ensure that credentials are created, used, and maintained consistently and securely.
Best practices
Restrict direct access
Restrict direct access for all credentials (tenant-level setting). Restricting direct access reduces the risk of credential exposure and misuse. This ensures credentials are only used within controlled stories, rather than being manually retrieved or shared.
Create an approval process for credential creation
Establish a process to get approval for credential creation. Include a collection of relevant information through a page for a user with credential management permissions to create in the tenant. This adds a layer of oversight to ensure new credentials meet all requirements and aren’t created unnecessarily or insecurely.
Establish standards for credential creation
Enforce a standardization for the creation of credentials with the following recommendations:
The credential name is filled in and includes the integration tool's name. For example: Tines Security Automation Team API Key
The credential description field is filled in with a relevant explanation. For example: This Tines credential has read-only access to the Security Automation team
The credential product field is filled in with the product you are integrating with Tines.
The credential is not a duplicate of an existing credential.
The credential is scoped to a service user or similar non-user account.
The credential URLs and domains field for restricting domain access must not be overly permissive.
If you are using change control, make sure the test credential fields are complete and include info for a non-production version of the relevant tool.
If you use the egress allowlist feature, add the relevant information to the egress allowlist to enable connecting to the tool.
Audit credentials
Complete regular audits of the credentials to ensure best practices are met. Build a Tines story to regularly audit credentials for best practices on a daily or weekly cadence. Ongoing validation helps maintain hygiene and ensures standards are continuously met, even as new credentials are added or updated.