[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HMB1GD3MPVA60VMZKN80F6":3,"skill-same:01M6HMB1GD3MPVA60VMZKN80F6":121},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":6,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6HMB1GD3MPVA60VMZKN80F6","implementing-rbac-hardening-for-kubernetes",null,"Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"hardening","for","implementing","implementing rbac hardening for kubernetes","kubernetes","rbac","container-security","security-hardening","iam","service-accounts","least-privilege","Providers","identity","access","cm","Access Control","de","cluster","cybersecurity","security","2026-11-10 10:12:30",false,"---\nname: implementing-rbac-hardening-for-kubernetes\ndescription: Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubernetes\n- rbac\n- access-control\n- least-privilege\n- security-hardening\n- iam\n- oidc\n- service-accounts\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\ncategory: implementing-rbac-hardening-for-kubernetes\n---\n# Implementing RBAC Hardening for Kubernetes\n\n## Overview\n\nKubernetes RBAC regulates access to cluster resources based on roles assigned to users, groups, and service accounts. Default configurations often grant excessive permissions, and without active hardening, RBAC becomes a primary attack vector for privilege escalation, lateral movement, and data exfiltration. Hardening requires implementing least-privilege principles, eliminating unnecessary ClusterRole bindings, separating service accounts, integrating external identity providers, and continuous auditing.\n\n\n## When to Use\n\n- When deploying or configuring implementing rbac hardening for kubernetes capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Kubernetes cluster v1.24+ with RBAC enabled (default since v1.6)\n- kubectl access with cluster-admin for initial audit\n- External identity provider (OIDC) for user authentication\n- Audit logging enabled on the API server\n\n## Core Hardening Principles\n\n### 1. Eliminate cluster-admin Sprawl\n\nAudit and remove unnecessary cluster-admin bindings:\n\n```bash\n# List all cluster-admin bindings\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] |\n  select(.roleRef.name == \"cluster-admin\") |\n  \"\\(.metadata.name) -> \\(.subjects[]? | \"\\(.kind)\u002F\\(.name) (\\(.namespace \u002F\u002F \"cluster\"))\")\"\n'\n```\n\n### 2. Namespace-Scoped Roles Over ClusterRoles\n\nUse Role and RoleBinding instead of ClusterRole and ClusterRoleBinding:\n\n```yaml\n# Good: Namespace-scoped role\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  namespace: application\n  name: app-developer\nrules:\n  - apiGroups: [\"apps\"]\n    resources: [\"deployments\"]\n    verbs: [\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\"]\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"pods\u002Flog\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"\"]\n    resources: [\"configmaps\"]\n    verbs: [\"get\", \"list\"]\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  namespace: application\n  name: app-developer-binding\nsubjects:\n  - kind: Group\n    name: dev-team\n    apiGroup: rbac.authorization.k8s.io\nroleRef:\n  kind: Role\n  name: app-developer\n  apiGroup: rbac.authorization.k8s.io\n```\n\n### 3. Dedicated Service Accounts Per Workload\n\n```yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: payment-processor\n  namespace: payments\nautomountServiceAccountToken: false  # Disable auto-mount\n---\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: payment-processor\n  namespace: payments\nspec:\n  template:\n    spec:\n      serviceAccountName: payment-processor\n      automountServiceAccountToken: true  # Only mount when explicitly needed\n      containers:\n        - name: processor\n          image: payments\u002Fprocessor:v2.1@sha256:abc...\n```\n\n### 4. Restrict Dangerous Permissions\n\nBlock permissions that enable privilege escalation:\n\n```yaml\n# Dangerous verbs\u002Fresources to restrict:\n# - secrets: get, list, watch (exposes all secrets in namespace)\n# - pods\u002Fexec: create (enables command execution in pods)\n# - pods: create with privileged securityContext\n# - serviceaccounts\u002Ftoken: create (generates new tokens)\n# - clusterroles\u002Fclusterrolebindings: create, update (self-escalation)\n# - nodes\u002Fproxy: create (bypasses API server authorization)\n\n# Safe read-only role example\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: ClusterRole\nmetadata:\n  name: security-viewer\nrules:\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"services\", \"namespaces\", \"nodes\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"apps\"]\n    resources: [\"deployments\", \"daemonsets\", \"statefulsets\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"networking.k8s.io\"]\n    resources: [\"networkpolicies\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n```\n\n### 5. OIDC Integration for User Authentication\n\n```yaml\n# API server flags for OIDC integration\napiVersion: v1\nkind: Pod\nmetadata:\n  name: kube-apiserver\nspec:\n  containers:\n    - name: kube-apiserver\n      command:\n        - kube-apiserver\n        - --oidc-issuer-url=https:\u002F\u002Fidp.company.com\n        - --oidc-client-id=kubernetes\n        - --oidc-username-claim=email\n        - --oidc-groups-claim=groups\n        - --oidc-ca-file=\u002Fetc\u002Fkubernetes\u002Fpki\u002Foidc-ca.crt\n```\n\n## RBAC Audit Process\n\n### Step 1: Enumerate All Bindings\n\n```bash\n# All ClusterRoleBindings with subjects\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] | select(.subjects != null) |\n  .subjects[] as $s |\n  \"\\(.metadata.name) | \\(.roleRef.name) | \\($s.kind)\u002F\\($s.name)\"\n' | sort | column -t -s '|'\n\n# All RoleBindings across namespaces\nkubectl get rolebindings --all-namespaces -o json | jq -r '\n  .items[] | select(.subjects != null) |\n  .subjects[] as $s |\n  \"\\(.metadata.namespace) | \\(.metadata.name) | \\(.roleRef.name) | \\($s.kind)\u002F\\($s.name)\"\n' | sort | column -t -s '|'\n```\n\n### Step 2: Identify Overprivileged Service Accounts\n\n```bash\n# Find service accounts with cluster-admin or admin roles\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] |\n  select(.roleRef.name == \"cluster-admin\" or .roleRef.name == \"admin\") |\n  select(.subjects[]?.kind == \"ServiceAccount\") |\n  \"\\(.subjects[] | select(.kind == \"ServiceAccount\") | \"\\(.namespace)\u002F\\(.name)\")\"\n'\n```\n\n### Step 3: Check Default Service Account Usage\n\n```bash\n# Find pods using the default service account\nkubectl get pods --all-namespaces -o json | jq -r '\n  .items[] |\n  select(.spec.serviceAccountName == \"default\" or .spec.serviceAccountName == null) |\n  \"\\(.metadata.namespace)\u002F\\(.metadata.name)\"\n'\n```\n\n### Step 4: Verify Token Auto-Mount\n\n```bash\n# Find pods with auto-mounted service account tokens\nkubectl get pods --all-namespaces -o json | jq -r '\n  .items[] |\n  select(.spec.automountServiceAccountToken != false) |\n  \"\\(.metadata.namespace)\u002F\\(.metadata.name) sa=\\(.spec.serviceAccountName \u002F\u002F \"default\")\"\n'\n```\n\n## Tooling\n\n### rbac-lookup\n\n```bash\n# Install rbac-lookup\nkubectl krew install rbac-lookup\n\n# View RBAC for a specific user\nkubectl rbac-lookup developer@company.com\n\n# View all RBAC bindings wide format\nkubectl rbac-lookup --kind user -o wide\n```\n\n### rakkess (Review Access)\n\n```bash\n# Install rakkess\nkubectl krew install access-matrix\n\n# Show access matrix for current user\nkubectl access-matrix\n\n# Show access for a specific service account\nkubectl access-matrix --sa payments:payment-processor\n```\n\n## References\n\n- [Kubernetes RBAC Documentation](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Freference\u002Faccess-authn-authz\u002Frbac\u002F)\n- [CIS Kubernetes Benchmark - RBAC Controls](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Kubernetes Security Hardening Guide 2025](https:\u002F\u002Fsealos.io\u002Fblog\u002Fa-practical-guide-to-kubernetes-security-hardening-your-cluster-in-2025\u002F)\n- [OWASP Kubernetes Security Cheat Sheet](https:\u002F\u002Fcheatsheetseries.owasp.org\u002Fcheatsheets\u002FKubernetes_Security_Cheat_Sheet.html)\n","# Implementing RBAC Hardening for Kubernetes\n\n## Overview\n\nKubernetes RBAC regulates access to cluster resources based on roles assigned to users, groups, and service accounts. Default configurations often grant excessive permissions, and without active hardening, RBAC becomes a primary attack vector for privilege escalation, lateral movement, and data exfiltration. Hardening requires implementing least-privilege principles, eliminating unnecessary ClusterRole bindings, separating service accounts, integrating external identity providers, and continuous auditing.\n\n\n## When to Use\n\n- When deploying or configuring implementing rbac hardening for kubernetes capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Kubernetes cluster v1.24+ with RBAC enabled (default since v1.6)\n- kubectl access with cluster-admin for initial audit\n- External identity provider (OIDC) for user authentication\n- Audit logging enabled on the API server\n\n## Core Hardening Principles\n\n### 1. Eliminate cluster-admin Sprawl\n\nAudit and remove unnecessary cluster-admin bindings:\n\n```bash\n# List all cluster-admin bindings\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] |\n  select(.roleRef.name == \"cluster-admin\") |\n  \"\\(.metadata.name) -> \\(.subjects[]? | \"\\(.kind)\u002F\\(.name) (\\(.namespace \u002F\u002F \"cluster\"))\")\"\n'\n```\n\n### 2. Namespace-Scoped Roles Over ClusterRoles\n\nUse Role and RoleBinding instead of ClusterRole and ClusterRoleBinding:\n\n```yaml\n# Good: Namespace-scoped role\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  namespace: application\n  name: app-developer\nrules:\n  - apiGroups: [\"apps\"]\n    resources: [\"deployments\"]\n    verbs: [\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\"]\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"pods\u002Flog\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"\"]\n    resources: [\"configmaps\"]\n    verbs: [\"get\", \"list\"]\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  namespace: application\n  name: app-developer-binding\nsubjects:\n  - kind: Group\n    name: dev-team\n    apiGroup: rbac.authorization.k8s.io\nroleRef:\n  kind: Role\n  name: app-developer\n  apiGroup: rbac.authorization.k8s.io\n```\n\n### 3. Dedicated Service Accounts Per Workload\n\n```yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: payment-processor\n  namespace: payments\nautomountServiceAccountToken: false  # Disable auto-mount\n---\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: payment-processor\n  namespace: payments\nspec:\n  template:\n    spec:\n      serviceAccountName: payment-processor\n      automountServiceAccountToken: true  # Only mount when explicitly needed\n      containers:\n        - name: processor\n          image: payments\u002Fprocessor:v2.1@sha256:abc...\n```\n\n### 4. Restrict Dangerous Permissions\n\nBlock permissions that enable privilege escalation:\n\n```yaml\n# Dangerous verbs\u002Fresources to restrict:\n# - secrets: get, list, watch (exposes all secrets in namespace)\n# - pods\u002Fexec: create (enables command execution in pods)\n# - pods: create with privileged securityContext\n# - serviceaccounts\u002Ftoken: create (generates new tokens)\n# - clusterroles\u002Fclusterrolebindings: create, update (self-escalation)\n# - nodes\u002Fproxy: create (bypasses API server authorization)\n\n# Safe read-only role example\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: ClusterRole\nmetadata:\n  name: security-viewer\nrules:\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"services\", \"namespaces\", \"nodes\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"apps\"]\n    resources: [\"deployments\", \"daemonsets\", \"statefulsets\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"networking.k8s.io\"]\n    resources: [\"networkpolicies\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n```\n\n### 5. OIDC Integration for User Authentication\n\n```yaml\n# API server flags for OIDC integration\napiVersion: v1\nkind: Pod\nmetadata:\n  name: kube-apiserver\nspec:\n  containers:\n    - name: kube-apiserver\n      command:\n        - kube-apiserver\n        - --oidc-issuer-url=https:\u002F\u002Fidp.company.com\n        - --oidc-client-id=kubernetes\n        - --oidc-username-claim=email\n        - --oidc-groups-claim=groups\n        - --oidc-ca-file=\u002Fetc\u002Fkubernetes\u002Fpki\u002Foidc-ca.crt\n```\n\n## RBAC Audit Process\n\n### Step 1: Enumerate All Bindings\n\n```bash\n# All ClusterRoleBindings with subjects\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] | select(.subjects != null) |\n  .subjects[] as $s |\n  \"\\(.metadata.name) | \\(.roleRef.name) | \\($s.kind)\u002F\\($s.name)\"\n' | sort | column -t -s '|'\n\n# All RoleBindings across namespaces\nkubectl get rolebindings --all-namespaces -o json | jq -r '\n  .items[] | select(.subjects != null) |\n  .subjects[] as $s |\n  \"\\(.metadata.namespace) | \\(.metadata.name) | \\(.roleRef.name) | \\($s.kind)\u002F\\($s.name)\"\n' | sort | column -t -s '|'\n```\n\n### Step 2: Identify Overprivileged Service Accounts\n\n```bash\n# Find service accounts with cluster-admin or admin roles\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] |\n  select(.roleRef.name == \"cluster-admin\" or .roleRef.name == \"admin\") |\n  select(.subjects[]?.kind == \"ServiceAccount\") |\n  \"\\(.subjects[] | select(.kind == \"ServiceAccount\") | \"\\(.namespace)\u002F\\(.name)\")\"\n'\n```\n\n### Step 3: Check Default Service Account Usage\n\n```bash\n# Find pods using the default service account\nkubectl get pods --all-namespaces -o json | jq -r '\n  .items[] |\n  select(.spec.serviceAccountName == \"default\" or .spec.serviceAccountName == null) |\n  \"\\(.metadata.namespace)\u002F\\(.metadata.name)\"\n'\n```\n\n### Step 4: Verify Token Auto-Mount\n\n```bash\n# Find pods with auto-mounted service account tokens\nkubectl get pods --all-namespaces -o json | jq -r '\n  .items[] |\n  select(.spec.automountServiceAccountToken != false) |\n  \"\\(.metadata.namespace)\u002F\\(.metadata.name) sa=\\(.spec.serviceAccountName \u002F\u002F \"default\")\"\n'\n```\n\n## Tooling\n\n### rbac-lookup\n\n```bash\n# Install rbac-lookup\nkubectl krew install rbac-lookup\n\n# View RBAC for a specific user\nkubectl rbac-lookup developer@company.com\n\n# View all RBAC bindings wide format\nkubectl rbac-lookup --kind user -o wide\n```\n\n### rakkess (Review Access)\n\n```bash\n# Install rakkess\nkubectl krew install access-matrix\n\n# Show access matrix for current user\nkubectl access-matrix\n\n# Show access for a specific service account\nkubectl access-matrix --sa payments:payment-processor\n```\n\n## References\n\n- [Kubernetes RBAC Documentation](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Freference\u002Faccess-authn-authz\u002Frbac\u002F)\n- [CIS Kubernetes Benchmark - RBAC Controls](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Kubernetes Security Hardening Guide 2025](https:\u002F\u002Fsealos.io\u002Fblog\u002Fa-practical-guide-to-kubernetes-security-hardening-your-cluster-in-2025\u002F)\n- [OWASP Kubernetes Security Cheat Sheet](https:\u002F\u002Fcheatsheetseries.owasp.org\u002Fcheatsheets\u002FKubernetes_Security_Cheat_Sheet.html)\n",{"name":5,"tags":49,"author":52,"domain":42,"license":15,"version":53,"category":5,"nist_csf":54,"subdomain":30,"description":7,"mitre_attack":59},[28,29,50,34,31,32,51,33],"access-control","oidc","mahipal","1.0",[55,56,57,58],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[60,61,62,63],"T1610","T1611","T1609","T1525","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fimplementing-rbac-hardening-for-kubernetes",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill implementing-rbac-hardening-for-kubernetes",{"tool":78,"command":79},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill implementing-rbac-hardening-for-kubernetes",{"tool":81,"command":82},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill implementing-rbac-hardening-for-kubernetes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002FSKILL.md",true,[86,92,97,103,107,111,117],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Ftemplate.md","ASSET","资产文件",741,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002Fassets\u002Ftemplate.md",{"path":93,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002FLICENSE",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fapi-reference.md","REFERENCE","参考文档",6262,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002Freferences\u002Fapi-reference.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fstandards.md",766,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002Freferences\u002Fstandards.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fworkflows.md",708,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002Freferences\u002Fworkflows.md",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fagent.py","SCRIPT","脚本",9923,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002Fscripts\u002Fagent.py",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fprocess.py",7020,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-rbac-hardening-for-kubernetes\u002Fscripts\u002Fprocess.py",[122,150,176,198,214,233],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":131,"publishedAt":44},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[132,133,134,135,25,136,42,137,138,139,140,141,142,143,144,145,146,147,148,149],"integrity","backup","recovery","validating backup integrity for recovery","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":44},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[157,158,159,160,161,42,162,163,164,165,166,167,168,169,170,171,172,173,174,175],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","with","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":44},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[43,183,147,42,184,185,186,143,144,187,188,189,190,191,192,193,194,195,196,197],"triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":44},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[43,205,206,183,147,161,42,207,185,140,208,209,143,144,210,188,171,211,212,213],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":44},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[43,221,222,223,224,225,42,226,227,228,185,229,143,230,231,232,191,38,147,40],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":239,"publishedAt":44},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[240,241,242,243,42,244,245,246,247,248,249,230,250,251,38,252,40,253,254,255],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]