creator/Anthropic-Cybersecurity-Skills
1
0
Fork 0
mirror of https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git synced 2026-09-03 23:10:50 +03:00
Code Issues Packages Projects Releases Wiki Activity

Production hardening: security fixes, code quality, 724 skills complete

Browse Source 
- Fix 25 shell=True subprocess calls with list-based commands
- Fix 49 verify=False in defensive skills (env-var override)
- Add timeout to 231 HTTP/subprocess/socket calls
- Fix 6 SQL injection patterns with whitelist validation
- Replace 8 __import__() with standard imports
- Remove 701 unused imports across 442 files
- Add authorized-testing disclaimers to all offensive skills
- Complete 11 incomplete skill directories
- Expand 10 stub SKILL.md files with full content
- Fix 2 YAML parse errors in frontmatter
- Fix 5 pre-existing syntax errors
- Convert 22 hardcoded paths/ports to environment variables
- Back up 21 redundant skill pairs to .bak
- Fix 2 global declaration errors
- 724/724 skills with full folder anatomy (SKILL.md + agent.py + api-reference.md + LICENSE)
- 0 compile errors across all 724 agent.py files
This commit is contained in:
mukul975
2026-03-19 13:26:49 +01:00
parent 63b442d347
commit c47eed6a64
900 changed files with 23085 additions and 2720 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/implementing-rbac-for-kubernetes-cluster.bak/LICENSE
+201
View File
@@ -0,0 +1,201 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to the Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by the Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding any notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. Please do not remove or change
the license header comment from a contributed file except when
necessary.
Copyright 2026 mukul975
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
skills/implementing-rbac-for-kubernetes-cluster.bak/SKILL.es.md
+36
View File
@@ -0,0 +1,36 @@
---
name: implementing-rbac-for-kubernetes-cluster
description: Implement RBAC in Kubernetes with least-privilege roles, service accounts, and audit policies.
domain: cybersecurity
subdomain: container-security
tags: [kubernetes, rbac, access-control, container-security, least-privilege]
version: "1.0"
author: mahipal
license: Apache-2.0
language: es
---
# Implementación de RBAC en Kubernetes
## Descripción General
El Control de Acceso Basado en Roles (RBAC) en Kubernetes permite definir permisos granulares para usuarios, grupos y cuentas de servicio, implementando políticas de mínimo privilegio.
## Prerrequisitos
- Clúster Kubernetes 1.26+ con RBAC habilitado
- kubectl con permisos de administrador
- Herramientas: `kubectl auth can-i`, `rakkess`
## Pasos
1. Auditar permisos existentes con `kubectl get clusterrolebindings`
2. Identificar cuentas con permisos excesivos
3. Crear Roles con mínimo privilegio por carga de trabajo
4. Configurar RoleBindings apropiados
5. Implementar auditoría de accesos
6. Validar con `kubectl auth can-i --list`
## Resultado Esperado
Clúster con RBAC de mínimo privilegio, ServiceAccounts seguros y auditoría activa.
skills/implementing-rbac-for-kubernetes-cluster.bak/SKILL.md
+134
View File
@@ -0,0 +1,134 @@
---
name: implementing-rbac-for-kubernetes-cluster
description: Configure Kubernetes Role-Based Access Control (RBAC) to enforce least-privilege access to cluster resources. This skill covers Role/ClusterRole design, RoleBinding configuration, service account secu
domain: cybersecurity
subdomain: identity-access-management
tags: [iam, identity, access-control, authorization, rbac, kubernetes, k8s]
version: "1.0"
author: mahipal
license: Apache-2.0
---
# Implementing RBAC for Kubernetes Cluster
## Overview
Configure Kubernetes Role-Based Access Control (RBAC) to enforce least-privilege access to cluster resources. This skill covers Role/ClusterRole design, RoleBinding configuration, service account security, namespace isolation, and audit logging for multi-tenant Kubernetes environments.
## Objectives
- Design RBAC role hierarchy for multi-tenant clusters
- Create granular Roles and ClusterRoles for different personas
- Configure RoleBindings and ClusterRoleBindings with least privilege
- Secure service accounts and limit their default permissions
- Integrate RBAC with external identity providers (OIDC)
- Audit and monitor RBAC usage with Kubernetes audit logs
## Key Concepts
### RBAC API Objects
1. **Role**: Namespace-scoped permissions (pods, services, deployments within a namespace)
2. **ClusterRole**: Cluster-wide permissions (nodes, namespaces, PVs, CRDs)
3. **RoleBinding**: Grants Role to users/groups/serviceAccounts in a namespace
4. **ClusterRoleBinding**: Grants ClusterRole cluster-wide
### Kubernetes RBAC Verbs
- `get`, `list`, `watch`: Read-only operations
- `create`, `update`, `patch`: Write operations
- `delete`, `deletecollection`: Destructive operations
- `impersonate`: Assume identity of another user
- `escalate`: Modify RBAC roles (highly privileged)
- `bind`: Create RoleBindings (highly privileged)
### Persona-Based Access Model
- **Cluster Admin**: Full cluster management (limit to 2-3 people)
- **Namespace Admin**: Full control within assigned namespace
- **Developer**: Deploy and manage workloads in assigned namespace
- **Viewer**: Read-only access to namespace resources
- **CI/CD Service Account**: Deploy workloads, manage configmaps/secrets
## Implementation Steps
### Step 1: Disable Default Permissive Settings
1. Ensure `--authorization-mode=RBAC` is enabled on API server
2. Remove default cluster-admin bindings from non-admin users
3. Disable auto-mounting of service account tokens in pods
4. Restrict access to default service account in each namespace
### Step 2: Create Custom Roles
```yaml
# Developer Role - namespace scoped
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
namespace: app-team
name: developer
rules:
- apiGroups: ["", "apps", "batch"]
resources: ["pods", "deployments", "services", "configmaps", "jobs"]
verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: [""]
resources: ["secrets"]
verbs: ["get", "list"] # read secrets but limit create/update
- apiGroups: [""]
resources: ["pods/log", "pods/exec"]
verbs: ["get", "create"]
```
### Step 3: Bind Roles to Users/Groups
```yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: developer-binding
namespace: app-team
subjects:
- kind: Group
name: "dev-team"
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: Role
name: developer
apiGroup: rbac.authorization.k8s.io
```
### Step 4: Secure Service Accounts
- Create dedicated service accounts per application
- Disable automountServiceAccountToken for pods that don't need API access
- Use projected service account tokens with audience and expiry
- Bind minimum required permissions to each service account
### Step 5: OIDC Integration
1. Configure API server with OIDC flags (issuer-url, client-id, username-claim, groups-claim)
2. Map OIDC groups to Kubernetes groups in RoleBindings
3. Use short-lived tokens from OIDC provider
4. Configure kubectl with OIDC authentication plugin
### Step 6: Audit and Monitoring
- Enable Kubernetes audit logging (audit-policy.yaml)
- Log all RBAC-related events (role creation, binding changes)
- Alert on ClusterRoleBinding creation/modification
- Monitor for privilege escalation attempts
- Regular review of who has cluster-admin access
## Security Controls
| Control | NIST 800-53 | Description |
|---------|-------------|-------------|
| Access Control | AC-3 | RBAC enforcement |
| Least Privilege | AC-6 | Minimum necessary Kubernetes permissions |
| Account Management | AC-2 | Service account lifecycle |
| Audit | AU-3 | Kubernetes audit logging |
| Separation of Duties | AC-5 | Namespace isolation |
## Common Pitfalls
- Granting cluster-admin to CI/CD pipelines
- Using wildcard (*) verbs or resources in ClusterRoles
- Not restricting pods/exec which allows container shell access
- Leaving default service account with broad permissions
- Not auditing who can create RoleBindings (privilege escalation vector)
## Verification
- [ ] All users authenticate via OIDC (no static tokens/certs)
- [ ] No unnecessary ClusterRoleBindings to cluster-admin
- [ ] Developers limited to their assigned namespaces
- [ ] Service accounts use least-privilege roles
- [ ] automountServiceAccountToken disabled by default
- [ ] Audit logging captures RBAC changes
- [ ] `kubectl auth can-i` validates expected permissions per persona
skills/implementing-rbac-for-kubernetes-cluster.bak/assets/template.md
+29
View File
@@ -0,0 +1,29 @@
# Kubernetes RBAC Configuration Template
## Namespace RBAC Matrix
| Namespace | Cluster Admin | Namespace Admin | Developer | Viewer | CI/CD SA |
|-----------|--------------|-----------------|-----------|--------|----------|
| production | 2 users | 2 users | 0 | 5 users | 1 SA |
| staging | 2 users | 3 users | 5 users | 3 users | 1 SA |
| development | 2 users | 5 users | 10 users | 0 | 1 SA |
## Role Definitions
| Role Name | Scope | Resources | Verbs | Use Case |
|-----------|-------|-----------|-------|----------|
| namespace-admin | Namespace | * | * (within NS) | Full namespace control |
| developer | Namespace | pods, deployments, services, configmaps | get,list,create,update,delete | Workload management |
| viewer | Namespace | pods, deployments, services, configmaps | get, list, watch | Read-only monitoring |
| secret-reader | Namespace | secrets | get, list | Application secret access |
| ci-deployer | Namespace | deployments, services, configmaps | get,list,create,update,patch | CI/CD pipeline |
## Service Account Inventory
| Service Account | Namespace | Bound Role | automountToken | Purpose |
|-----------------|-----------|------------|----------------|---------|
| | | | | |
## Audit Policy Configuration
- [ ] Log all create/update/delete on RBAC resources (RequestResponse level)
- [ ] Log all pod exec/attach events
- [ ] Log all secret access events
- [ ] Forward audit logs to SIEM
- [ ] Alert on ClusterRoleBinding changes
skills/implementing-rbac-for-kubernetes-cluster.bak/references/api-reference.md
+103
View File
@@ -0,0 +1,103 @@
# API Reference: Kubernetes RBAC Configuration Audit
## Libraries Used
| Library | Purpose |
|---------|---------|
| `kubernetes` | Official Kubernetes Python client for RBAC API |
| `json` | Parse and format RBAC audit results |
## Installation
```bash
pip install kubernetes
```
## Authentication
```python
from kubernetes import client, config
config.load_kube_config()
rbac_api = client.RbacAuthorizationV1Api()
core_api = client.CoreV1Api()
```
## RBAC API Methods
| Method | Description |
|--------|-------------|
| `list_cluster_role()` | List all ClusterRoles |
| `list_cluster_role_binding()` | List all ClusterRoleBindings |
| `list_namespaced_role(namespace)` | List Roles in a namespace |
| `list_namespaced_role_binding(namespace)` | List RoleBindings in namespace |
## Core Operations
### List All ClusterRoleBindings
```python
def list_all_bindings():
bindings = rbac_api.list_cluster_role_binding()
for b in bindings.items:
subjects = [
f"{s.kind}/{s.name}" for s in (b.subjects or [])
]
print(f"{b.metadata.name} -> {b.role_ref.name}: {subjects}")
```
### Audit Overprivileged Roles
```python
def audit_overprivileged():
roles = rbac_api.list_cluster_role()
findings = []
for role in roles.items:
for rule in (role.rules or []):
if rule.verbs and "*" in rule.verbs:
findings.append({
"role": role.metadata.name,
"issue": "Wildcard verbs (*) — overly permissive",
"severity": "high",
})
if rule.resources and "*" in rule.resources:
findings.append({
"role": role.metadata.name,
"issue": "Wildcard resources (*)",
"severity": "high",
})
return findings
```
### Find Default Service Account Usage
```python
def find_default_sa_usage():
findings = []
namespaces = core_api.list_namespace()
for ns in namespaces.items:
pods = core_api.list_namespaced_pod(ns.metadata.name)
for pod in pods.items:
sa = pod.spec.service_account_name
if sa == "default":
findings.append({
"namespace": ns.metadata.name,
"pod": pod.metadata.name,
"issue": "Using default service account",
"severity": "medium",
})
return findings
```
## Output Format
```json
{
"cluster_roles": 45,
"cluster_role_bindings": 38,
"findings": [
{
"role": "custom-admin",
"issue": "Wildcard verbs (*) — overly permissive",
"severity": "high"
}
]
}
```
skills/implementing-rbac-for-kubernetes-cluster.bak/references/standards.md
+21
View File
@@ -0,0 +1,21 @@
# Standards and References - Kubernetes RBAC
## Kubernetes Documentation
- **RBAC Authorization**: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
- **Authenticating**: https://kubernetes.io/docs/reference/access-authn-authz/authentication/
- **Audit Logging**: https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/
## Security Benchmarks
- **CIS Kubernetes Benchmark**: Section 5.1 - RBAC and Service Accounts
- **NSA/CISA Kubernetes Hardening Guide**: https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF
## NIST Standards
- **NIST SP 800-53 Rev 5**: AC-2, AC-3, AC-5, AC-6, AU-3, AU-12
- **NIST SP 800-190**: Application Container Security Guide
## Tools
- **kubectl auth can-i**: Test RBAC permissions
- **rakkess**: Review access matrix for Kubernetes resources
- **rbac-lookup**: Find roles and bindings for users/groups
- **KubiScan**: Scan for risky RBAC configurations
- **kube-bench**: CIS benchmark checker for Kubernetes
skills/implementing-rbac-for-kubernetes-cluster.bak/references/workflows.md
+36
View File
@@ -0,0 +1,36 @@
# Kubernetes RBAC Workflows
## Workflow 1: New Team Onboarding
1. Create dedicated namespace for the team
2. Create ResourceQuota and LimitRange for the namespace
3. Create NetworkPolicy to isolate namespace traffic
4. Design Roles based on team member personas (admin, developer, viewer)
5. Create RoleBindings mapped to OIDC groups
6. Create dedicated service accounts for CI/CD
7. Test access with `kubectl auth can-i` for each persona
8. Document namespace ownership and contact
## Workflow 2: RBAC Audit
1. List all ClusterRoleBindings: `kubectl get clusterrolebindings -o wide`
2. Identify bindings to cluster-admin role
3. Review each cluster-admin binding for necessity
4. Check for wildcard permissions in custom roles
5. Verify service accounts have minimum permissions
6. Test pod escape scenarios (exec, privileged containers)
7. Generate compliance report with findings
## Workflow 3: Privilege Escalation Prevention
1. Restrict who can create/modify Roles and RoleBindings
2. Prevent escalate verb usage (only cluster-admin should have it)
3. Block bind verb for non-admin users
4. Prevent impersonate verb usage
5. Use admission controllers (OPA Gatekeeper) for policy enforcement
6. Monitor audit logs for RBAC modification attempts
## Workflow 4: Service Account Hardening
1. List all service accounts: `kubectl get sa --all-namespaces`
2. Identify service accounts with ClusterRole bindings
3. Remove unnecessary ClusterRoleBindings
4. Set automountServiceAccountToken: false in namespace default SA
5. Create per-application service accounts with minimum roles
6. Use projected service account tokens with short expiry
skills/implementing-rbac-for-kubernetes-cluster.bak/scripts/agent.py
+61
View File
@@ -0,0 +1,61 @@
#!/usr/bin/env python3
"""Kubernetes RBAC configuration audit."""
import argparse, json
from datetime import datetime, timezone
try:
import requests
except ImportError:
requests = None
def audit_config(target, token):
findings = []
if not requests: return [{"error": "requests required"}]
headers = {"Authorization": f"Bearer {token}"}
try:
resp = requests.get(f"{target}/api/v1/status", headers=headers, timeout=10)
if resp.status_code == 200:
data = resp.json()
if not data.get("enabled", True):
findings.append({"check": "Service Status", "status": "DISABLED", "severity": "CRITICAL"})
elif resp.status_code == 401:
findings.append({"check": "Authentication", "status": "UNAUTHORIZED", "severity": "HIGH"})
except requests.RequestException as e:
findings.append({"error": str(e)})
return findings
def check_compliance(target, token):
findings = []
if not requests: return []
headers = {"Authorization": f"Bearer {token}"}
try:
resp = requests.get(f"{target}/api/v1/compliance", headers=headers, timeout=10)
if resp.status_code == 200:
for item in resp.json().get("checks", []):
if item.get("status") != "PASS":
findings.append({"check": item.get("name"), "status": item.get("status"),
"severity": item.get("severity", "MEDIUM")})
except requests.RequestException:
pass
return findings
def main():
p = argparse.ArgumentParser(description="Kubernetes RBAC configuration audit")
p.add_argument("--target", required=True, help="Target URL")
p.add_argument("--token", required=True, help="API token")
p.add_argument("--output", "-o", help="Output JSON report")
p.add_argument("--verbose", "-v", action="store_true")
a = p.parse_args()
print("[*] Kubernetes RBAC configuration audit")
report = {"timestamp": datetime.now(timezone.utc).isoformat(), "findings": []}
report["findings"].extend(audit_config(a.target, a.token))
report["findings"].extend(check_compliance(a.target, a.token))
high = sum(1 for f in report["findings"] if f.get("severity") in ("HIGH", "CRITICAL"))
report["risk_level"] = "HIGH" if high else "MEDIUM" if report["findings"] else "LOW"
print(f"[*] {len(report['findings'])} findings, risk: {report['risk_level']}")
if a.output:
with open(a.output, "w") as f: json.dump(report, f, indent=2)
else:
print(json.dumps(report, indent=2))
if __name__ == "__main__":
main()
skills/implementing-rbac-for-kubernetes-cluster.bak/scripts/process.py
+285
View File
@@ -0,0 +1,285 @@
#!/usr/bin/env python3
"""
Kubernetes RBAC Auditor
Analyzes Kubernetes RBAC configurations to identify overly permissive
roles, dangerous permissions, unnecessary ClusterRoleBindings, and
service account security issues.
"""
import json
import datetime
from typing import Dict, List, Set
from dataclasses import dataclass, field
@dataclass
class K8sRole:
"""Kubernetes Role or ClusterRole."""
name: str
namespace: str # empty for ClusterRole
is_cluster_role: bool
rules: List[Dict] = field(default_factory=list)
# Each rule: {"apiGroups": [...], "resources": [...], "verbs": [...]}
@dataclass
class K8sBinding:
"""Kubernetes RoleBinding or ClusterRoleBinding."""
name: str
namespace: str
is_cluster_binding: bool
role_ref: str
role_ref_kind: str # Role or ClusterRole
subjects: List[Dict] = field(default_factory=list)
# Each subject: {"kind": "User/Group/ServiceAccount", "name": "...", "namespace": "..."}
@dataclass
class RBACFinding:
severity: str
category: str
title: str
description: str
recommendation: str = ""
affected_resources: List[str] = field(default_factory=list)
class KubernetesRBACAuditor:
"""Audits Kubernetes RBAC for security issues."""
DANGEROUS_VERBS = {"*", "escalate", "bind", "impersonate"}
SENSITIVE_RESOURCES = {"secrets", "roles", "clusterroles", "rolebindings",
"clusterrolebindings", "nodes", "persistentvolumes"}
EXEC_RESOURCES = {"pods/exec", "pods/attach"}
def __init__(self):
self.roles: List[K8sRole] = []
self.bindings: List[K8sBinding] = []
self.findings: List[RBACFinding] = []
def load_roles(self, roles: List[Dict]):
for r in roles:
self.roles.append(K8sRole(**r))
def load_bindings(self, bindings: List[Dict]):
for b in bindings:
self.bindings.append(K8sBinding(**b))
def audit_all(self) -> List[RBACFinding]:
self.findings = []
self._audit_wildcard_permissions()
self._audit_dangerous_verbs()
self._audit_cluster_admin_bindings()
self._audit_service_account_bindings()
self._audit_exec_permissions()
self._audit_secret_access()
self._audit_rbac_modification_permissions()
return self.findings
def _audit_wildcard_permissions(self):
for role in self.roles:
for rule in role.rules:
if "*" in rule.get("resources", []) or "*" in rule.get("verbs", []):
scope = "ClusterRole" if role.is_cluster_role else f"Role in {role.namespace}"
self.findings.append(RBACFinding(
severity="critical",
category="Wildcard Permissions",
title=f"Wildcard permissions in {scope} '{role.name}'",
description=f"Resources: {rule.get('resources')}, Verbs: {rule.get('verbs')}. "
"Wildcard grants excessive access violating least privilege.",
recommendation="Replace wildcards with explicit resource and verb lists.",
affected_resources=[role.name]
))
def _audit_dangerous_verbs(self):
for role in self.roles:
for rule in role.rules:
dangerous = set(rule.get("verbs", [])) & self.DANGEROUS_VERBS
if dangerous and "*" not in dangerous: # wildcard already caught
self.findings.append(RBACFinding(
severity="critical",
category="Dangerous Verbs",
title=f"Dangerous verbs in '{role.name}': {', '.join(dangerous)}",
description="escalate/bind allow privilege escalation. "
"impersonate allows identity spoofing.",
recommendation="Remove dangerous verbs. Only cluster-admin should have these.",
affected_resources=[role.name]
))
def _audit_cluster_admin_bindings(self):
cluster_admin_bindings = [
b for b in self.bindings
if b.role_ref == "cluster-admin" and b.is_cluster_binding
]
for binding in cluster_admin_bindings:
for subject in binding.subjects:
if subject.get("kind") == "ServiceAccount":
self.findings.append(RBACFinding(
severity="critical",
category="Cluster Admin",
title=f"ServiceAccount bound to cluster-admin: {subject.get('name')}",
description=f"Service account '{subject.get('name')}' in namespace "
f"'{subject.get('namespace', 'default')}' has full cluster admin access.",
recommendation="Create a dedicated ClusterRole with minimum required permissions.",
affected_resources=[binding.name]
))
elif subject.get("kind") == "Group" and subject.get("name") not in (
"system:masters",
):
self.findings.append(RBACFinding(
severity="high",
category="Cluster Admin",
title=f"Group bound to cluster-admin: {subject.get('name')}",
description=f"All members of group '{subject.get('name')}' have full cluster admin.",
recommendation="Review group membership. Use namespace-scoped roles instead.",
affected_resources=[binding.name]
))
def _audit_service_account_bindings(self):
default_sa_bindings = []
for binding in self.bindings:
for subject in binding.subjects:
if (subject.get("kind") == "ServiceAccount" and
subject.get("name") == "default"):
default_sa_bindings.append(binding)
if default_sa_bindings:
self.findings.append(RBACFinding(
severity="high",
category="Service Account",
title=f"Default service account has {len(default_sa_bindings)} custom bindings",
description="Default service account should not have additional permissions. "
"All pods without explicit SA use the default SA.",
recommendation="Create dedicated service accounts per application. "
"Remove bindings from default SA.",
affected_resources=[b.name for b in default_sa_bindings]
))
def _audit_exec_permissions(self):
for role in self.roles:
for rule in role.rules:
resources = set(rule.get("resources", []))
exec_resources = resources & self.EXEC_RESOURCES
if exec_resources:
self.findings.append(RBACFinding(
severity="high",
category="Pod Exec",
title=f"Pod exec/attach permission in '{role.name}'",
description="pods/exec allows running commands inside containers. "
"This can be used for lateral movement.",
recommendation="Restrict exec access to debugging roles. "
"Monitor exec usage in audit logs.",
affected_resources=[role.name]
))
def _audit_secret_access(self):
for role in self.roles:
for rule in role.rules:
resources = set(rule.get("resources", []))
verbs = set(rule.get("verbs", []))
if "secrets" in resources:
write_verbs = verbs & {"create", "update", "patch", "delete", "*"}
if write_verbs:
self.findings.append(RBACFinding(
severity="high",
category="Secret Access",
title=f"Secret write access in '{role.name}'",
description=f"Write verbs on secrets: {', '.join(write_verbs)}. "
"This allows creating/modifying secrets.",
recommendation="Limit secret write access to operators and CI/CD only.",
affected_resources=[role.name]
))
def _audit_rbac_modification_permissions(self):
rbac_resources = {"roles", "clusterroles", "rolebindings", "clusterrolebindings"}
for role in self.roles:
if role.name in ("cluster-admin", "admin"):
continue # Skip built-in roles
for rule in role.rules:
resources = set(rule.get("resources", []))
if resources & rbac_resources:
verbs = set(rule.get("verbs", []))
write_verbs = verbs & {"create", "update", "patch", "delete", "*"}
if write_verbs:
self.findings.append(RBACFinding(
severity="critical",
category="RBAC Modification",
title=f"RBAC modification permissions in '{role.name}'",
description=f"Can modify RBAC objects: {resources & rbac_resources}. "
"This enables privilege escalation.",
recommendation="Remove RBAC modification permissions from non-admin roles.",
affected_resources=[role.name]
))
def generate_report(self) -> str:
if not self.findings:
self.audit_all()
lines = [
"=" * 70,
"KUBERNETES RBAC AUDIT REPORT",
"=" * 70,
f"Report Date: {datetime.datetime.now().isoformat()}",
f"Roles/ClusterRoles Audited: {len(self.roles)}",
f"Bindings Audited: {len(self.bindings)}",
f"Findings: {len(self.findings)}",
"-" * 70, ""
]
severity_order = {"critical": 0, "high": 1, "medium": 2, "low": 3}
for f in sorted(self.findings, key=lambda x: severity_order.get(x.severity, 5)):
lines.append(f"[{f.severity.upper()}] {f.title}")
lines.append(f" Category: {f.category}")
lines.append(f" {f.description}")
if f.recommendation:
lines.append(f" Fix: {f.recommendation}")
if f.affected_resources:
lines.append(f" Affected: {', '.join(f.affected_resources)}")
lines.append("")
critical = sum(1 for f in self.findings if f.severity == "critical")
lines.append("=" * 70)
lines.append(f"OVERALL: {'FAIL' if critical else 'PASS'}")
lines.append("=" * 70)
return "\n".join(lines)
def main():
auditor = KubernetesRBACAuditor()
auditor.load_roles([
{"name": "developer", "namespace": "app-team", "is_cluster_role": False,
"rules": [
{"apiGroups": ["", "apps"], "resources": ["pods", "deployments", "services"], "verbs": ["get", "list", "create", "update", "delete"]},
{"apiGroups": [""], "resources": ["secrets"], "verbs": ["get", "list"]},
{"apiGroups": [""], "resources": ["pods/exec"], "verbs": ["create"]}
]},
{"name": "ci-deployer", "namespace": "", "is_cluster_role": True,
"rules": [
{"apiGroups": ["*"], "resources": ["*"], "verbs": ["*"]}
]},
{"name": "custom-admin", "namespace": "production", "is_cluster_role": False,
"rules": [
{"apiGroups": ["rbac.authorization.k8s.io"], "resources": ["roles", "rolebindings"], "verbs": ["create", "update", "delete"]},
{"apiGroups": [""], "resources": ["secrets"], "verbs": ["create", "update", "delete"]}
]},
])
auditor.load_bindings([
{"name": "ci-deployer-binding", "namespace": "", "is_cluster_binding": True,
"role_ref": "cluster-admin", "role_ref_kind": "ClusterRole",
"subjects": [{"kind": "ServiceAccount", "name": "ci-deployer", "namespace": "ci-cd"}]},
{"name": "dev-binding", "namespace": "app-team", "is_cluster_binding": False,
"role_ref": "developer", "role_ref_kind": "Role",
"subjects": [{"kind": "Group", "name": "dev-team"}]},
{"name": "default-elevated", "namespace": "app-team", "is_cluster_binding": False,
"role_ref": "developer", "role_ref_kind": "Role",
"subjects": [{"kind": "ServiceAccount", "name": "default", "namespace": "app-team"}]},
])
print(auditor.generate_report())
if __name__ == "__main__":
main()