Skip to content

Commit 6c2e987

Browse files
elad-ptichaelad-pticha
committed
chore: updated resource titles
1 parent 3d81016 commit 6c2e987

File tree

6 files changed

+21
-21
lines changed

6 files changed

+21
-21
lines changed

‎docs/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,12 @@ The project is structured around individual best practices, each in its own file
1010
| Best Practice | Description | Link |
1111
|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|
1212
| Cluster Separation | Deploy the GitOps agent in a separate Kubernetes cluster from the one it manages to protect against application-level compromises. | [Details](resources/cluster-separation/README.md) |
13-
| Separation Of Concerns | Store Kubernetes manifests that manage GitOps agent resources in a separate repository from its application deployment files to ensure security. | [Details](resources/separation-of-concerns/README.md) |
13+
| GitOps Manifest Segregation | Store Kubernetes manifests that manage GitOps agent resources in a separate repository from its application deployment files to ensure security. | [Details](resources/gitops-manifest-segregation/README.md) |
1414
| Network Policies Enforcement | Implement network policies to restrict access to GitOps Kubernetes resources and ensure that a CNI plugin enforces these rules correctly. | [Details](resources/network-policies-enforcement/README.md) |
1515
| Strict RBAC Policies | Enforce strict RBAC policies to ensure only authorized users can manage the GitOps system and grant appropriate permissions. | [Details](resources/strict-rbac-policies/README.md) |
16-
| Restrict Repository Access | Keep GitOps configuration repositories private, granting access only to authorized teams or individuals. | [Details](resources/restrict-repository-access/README.md) |
17-
| Branch Protection Rules | Implement code review requirements, CI/CD checks, and restrict access to critical branches on the GitOps repository to control deployments. | [Details](resources/branch-protection-rules/README.md) |
18-
| Use Password Management Tool | Store sensitive data in a proper secret management tool rather than in plaintext. | [Details](resources/use-password-management-tool/README.md) |
16+
| Restricted Repository Access | Keep GitOps configuration repositories private, granting access only to authorized teams or individuals. | [Details](resources/restricted-repository-access/README.md) |
17+
| Branch Protection | Implement code review requirements, CI/CD checks, and restrict access to critical branches on the GitOps repository to control deployments. | [Details](resources/branch-protection/README.md) |
18+
| Secure Secret Storage | Store sensitive data in a proper secret management tool rather than in plaintext. | [Details](resources/secure-secret-storage/README.md) |
1919
| SLSA Provenance Verification | Verify the SLSA provenance from GitOps suppliers (e.g., ArgoCD’s signed SLSA provenance) to ensure the integrity of GitOps deployments. | [Details](resources/slsa-provenance-verification/README.md) |
2020

2121

‎docs/resources/branch-protection-rules/README.md ‎docs/resources/branch-protection/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
slug: /branchProtectionRules
3-
id: branchProtectionRules
4-
sidebar_position: 5
2+
slug: /branchProtection
3+
id: branchProtection
4+
sidebar_position: 6
55
---
66

7-
# Branch Protection Rules
7+
# Branch Protection
88

99
## Overview
1010

‎docs/resources/separation-of-concerns/README.md ‎docs/resources/gitops-manifest-segregation/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
slug: /separatingConfig
3-
id: separatingConfig
4-
sidebar_position: 6
2+
slug: /gitOpsManifestSegregation
3+
id: gitOpsManifestSegregation
4+
sidebar_position: 2
55
---
66

7-
# Separation Of Concerns
7+
# GitOps Manifest Segregation
88

99
## Overview
1010
Separate the GitOps Kubernetes configurations (e.g., manifests) into a dedicated Git repository, distinct from your GitOps managed application source code. Isolating application configuration from the codebase enhances deployment control, simplifies auditing, and prevents unintended CI/CD pipeline triggers due to minor configuration changes.

‎docs/resources/network-policies-enforcement/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
slug: /networkPoliciesEnforcement
33
id: networkPoliciesEnforcement
4-
sidebar_position: 2
4+
sidebar_position: 3
55
---
66

77
# Network Policies Enforcement

‎docs/resources/restrict-repository-access/README.md ‎docs/resources/restricted-repository-access/README.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
2-
slug: /restrictRepositoryAccess
3-
id: restrictRepositoryAccess
4-
sidebar_position: 4
2+
slug: /restrictedRepositoryAccess
3+
id: restrictedRepositoryAccess
4+
sidebar_position: 5
55
---
66

77

8-
# Restrict Repository Access
8+
# Restricted Repository Access
99

1010
## Overview
1111
In a GitOps workflow, repositories that store Kubernetes manifests, Helm charts, and other configuration files are essential for managing infrastructure. These repositories should be kept private, with access strictly limited to authorized individuals or teams. Allowing outside collaborators or broad access increases the risk of unauthorized changes, whether accidental or malicious.
1212

1313
## Why It’s Important
1414
1. **Protect Sensitive Data:** Configuration repositories often contain sensitive infrastructure details that must remain secure. Unauthorized access can expose sensitive information or lead to misconfigurations that compromise the system's security.
15-
2. **Enforce Better Access Control:** By separating configuration repositories from source code repositories (as discussed in [Separating Config Vs. Source Code Repositories](resources/separation-of-concerns/README.md)), you can grant access based on roles and needs, further upholding the principle of least privilege.
15+
2. **Enforce Better Access Control:** By separating configuration repositories from source code repositories (as discussed in [GitOps Manifest Segregation](resources/gitops-manifest-segregation/README.md)), you can grant access based on roles and needs, further upholding the principle of least privilege.
1616

1717
## Implementation Steps
1818

‎docs/resources/use-password-management-tool/README.md ‎docs/resources/secure-secret-storage/README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
slug: /passwordManagement
3-
id: passwordManagement
2+
slug: /secureSecretStorage
3+
id: secureSecretStorage
44
sidebar_position: 7
55
---
66

7-
# Use Password Management Tool
7+
# Secure Secret Storage
88

99
## Overview
1010

0 commit comments

Comments
 (0)