;
};
Dynamic secrets are available under Infisical's [Advanced](https://infisical.com/pricing) plan.
If you're self-hosting Infisical, contact [sales@infisical.com](mailto:sales@infisical.com) to purchase an Advanced license.
## Introduction
Contrary to static key-value secrets, which require manual input of data into the secure Infisical storage, **dynamic secrets are generated on-demand upon access**.
**Dynamic secrets are unique to every identity using them**. Such secrets are generated only at the moment they're retrieved, eliminating the possibility of theft or reuse by another identity. Thanks to Infisical's integrated revocation capabilities, dynamic secrets can be promptly invalidated post-use, significantly reducing their lifespan.
## Supported services
## Benefits of dynamic secrets
This approach offers several advantages in terms of security and management:
* **Enhanced Security**: By frequently changing secrets, dynamic secrets minimize the risk associated with secret compromise. Even if an attacker manages to obtain a secret, it would likely be invalid by the time they attempt to use it.
* **Reduced Secret Lifetime**: The limited validity period of dynamic secrets means that they're less valuable targets for attackers. This inherently reduces the time window during which a secret can be exploited.
* **Automated Management**: Dynamic secrets enable automated systems to handle the generation, distribution, revocation, and rotation of secrets without human intervention, thus reducing the risk of human error.
* **Auditing and Traceability**: The generation of dynamic secrets can be tightly controlled and monitored. This allows for detailed auditing of who accessed what secret and when, improving overall security posture and compliance with regulatory standards.
* **Scalability**: Dynamic secret management systems can scale more effectively to handle a large number of services and applications, as they automate much of the overhead associated with manual secret management.
Dynamic secrets are particularly useful in environments with stringent security requirements, such as cloud environments, distributed systems, and microservices architectures, where they help to manage database credentials, API keys, tokens, and other types of secrets.
**FAQ**
This usually happens when the SQL statements defined for creating or revoking the secret aren't compatible with your database provider.
Different SQL engines have different expectations for quoting identifiers and values. For example, some use backticks (`` `username` ``), others use single quotes (`'username'`), and some expect double quotes (`"username"`). A statement that works on one provider might fail on another.
**Recommendation:**\
Make sure to adjust your SQL statements to follow the syntax required by your specific database provider. Always test them directly on your target database to ensure they execute without errors.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.