Security
Security & authentication
Use secure configuration patterns to protect consent data, API traffic, and customer-facing integrations.
Overview
Digital Anumati security patterns are designed to help teams protect both public browser integrations and private backend systems. Each environment should be configured with the least privilege necessary and reviewed regularly.
Security controls
| Control | Purpose |
|---|---|
| Authentication | Verify the caller identity for every API request. |
| Domain allowlisting | Restrict browser integrations to approved origins. |
| Rate limits | Protect the API from abuse or accidental overload. |
| Secret handling | Keep private keys on server-side systems and rotate as needed. |
Best practices
Use separate credentials for development and production, store secrets in secure secret management, and validate the consent lifecycle through staging tests before production rollout.
Operational note
Security controls should be reviewed as part of the implementation handoff and any change to an application, domain, or team configuration.