January 2025 Summaries
2 posts from Infisical
Filter
Month:
Year:
Post Summaries
Back to Blog
Azure Key Vault is a cloud-based service that securely stores and manages cryptographic keys, secrets, and certificates. It offers two service tiers: Standard Tier with software-protected keys and Premium Tier with HSM-protected keys for enhanced security. The pricing structure varies between the two tiers, with the Premium tier being more expensive due to the additional security features. Key Vault provides a comprehensive solution for secrets management, integrating seamlessly with other Azure services, but may lack certain functionalities compared to alternative solutions like Infisical. It follows a pay-as-you-go model with no upfront costs and can be used with applications hosted anywhere, not just in Azure.
Jan 28, 2025
1,083 words in the original blog post.
GitOps is a set of practices that uses Git as the single source of truth for declarative infrastructure and applications, automating the deployment process through version control. Managing secrets in GitOps workflows presents unique challenges that require careful consideration of security, automation, and developer experience. This guide explores different approaches to secrets management in GitOps, with a focus on integrating Infisical into your workflow. It discusses why modern cloud-native architectures often require a more dynamic secrets management approach and introduces three options for implementing secrets management in GitOps: the Infisical Operator, External Secrets Operator, and Secrets Store CSI Driver. Each option has its advantages and best use cases, and the guide also provides security best practices for GitOps secrets management, including implementing least privilege access, regularly rotating secrets, enabling audit trails, and securing CI/CD pipeline configuration. The guide concludes by highlighting Infisical's approach to managing its own secrets in production and looking forward to the future of GitOps secrets management.
Jan 22, 2025
2,340 words in the original blog post.