Skip to content

Commit 232b5d8

Browse files
Merge pull request #18 from segudev/patch-1
Use "secrets management" instead of "secret management"
2 parents 8211815 + 1c7746b commit 232b5d8

File tree

2 files changed

+78
-78
lines changed

2 files changed

+78
-78
lines changed

docs/production/secret-management.md

-78
This file was deleted.

docs/production/secrets-management.md

+78
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
layout: default
3+
title: Secrets Management
4+
parent: Production
5+
---
6+
7+
{: .no_toc }
8+
9+
## Table of contents
10+
{: .no_toc .text-delta }
11+
12+
1. TOC
13+
{:toc}
14+
15+
---
16+
17+
18+
# Secrets Management
19+
{: .no_toc }
20+
21+
22+
Secrets management refers to the process of securely storing, managing, and accessing sensitive information, such as passwords, API keys, and other credentials. Secrets are a critical component of modern applications, and their secure management is essential to ensure the security and integrity of the application.
23+
24+
Secrets management typically involves the use of specialized tools and technologies that provide a secure and centralized location for storing and managing secrets. These tools often use strong encryption and access control mechanisms to protect sensitive information from unauthorized access.
25+
26+
Some of the key features of secrets management tools include:
27+
28+
1. Secure storage: Secrets management tools provide a secure location for storing sensitive information, typically using strong encryption and access control mechanisms to ensure that only authorized users can access the information.
29+
30+
2. Access control: Secrets management tools allow administrators to define access control policies and roles that govern who can access specific secrets and what actions they can perform.
31+
32+
3. Auditing and monitoring: Secrets management tools provide auditing and monitoring capabilities that allow administrators to track who accessed specific secrets and when, providing an audit trail for compliance and security purposes.
33+
34+
4. Integration with other tools: Secrets management tools can be integrated with other DevOps tools, such as build servers, deployment tools, and orchestration frameworks, to provide seamless access to secrets during the application lifecycle.
35+
36+
37+
## Hashicorp Vault
38+
39+
A highly secure and scalable secrets management solution that supports a wide range of authentication methods and storage backends.
40+
41+
```
42+
vault kv put secret/myapp/config username="admin" password="s3cret" API_key="123456789"
43+
```
44+
45+
## AWS Secrets Manager
46+
47+
A fully managed secrets management service provided by Amazon Web Services.
48+
49+
```
50+
aws secretsmanager create-secret --name myapp/database --secret-string '{"username":"admin","password":"s3cret"}'
51+
```
52+
53+
54+
## Azure Key Vault
55+
56+
A cloud-based secrets management service provided by Microsoft Azure.
57+
58+
59+
```
60+
az keyvault secret set --name myapp/config --value s3cret
61+
```
62+
63+
## Git-crypt
64+
65+
A command-line tool that allows you to encrypt files and directories within a Git repository.
66+
67+
```
68+
git-crypt init && git-crypt add-gpg-user [email protected]
69+
```
70+
71+
## Blackbox
72+
73+
A command-line tool that allows you to store and manage secrets in Git repositories using GPG encryption.
74+
75+
76+
```
77+
blackbox_initialize && blackbox_register_new_file secrets.txt
78+
```

0 commit comments

Comments
 (0)