[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF7HKFMZ7EY82AT7Z89C89":3,"skill-same:01M6AF7HKFMZ7EY82AT7Z89C89":120},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6AF7HKFMZ7EY82AT7Z89C89","implementing-kubernetes-network-policy-with-calico",null,"Installs Calico as the cluster CNI and writes standard Kubernetes NetworkPolicy under it, covering default-deny baselines, policy ordering and precedence, service-account-based selectors, and verifying that policy is genuinely being enforced. Use when adopting Calico as the enforcement CNI, establishing a default-deny baseline, or debugging why a NetworkPolicy is not taking effect under Calico. Keywords: Calico CNI, NetworkPolicy, default deny, policy order, Felix, service account selector. Do not use for Calico-only CRDs such as GlobalNetworkPolicy or DNS egress - use implementing-container-network-policies-with-calico; for CNI-agnostic policy use implementing-network-policies-for-kubernetes.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\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],"network","implementing kubernetes network policy with calico","calico","kubernetes","policy","pr","debugging","dns","container-security","ZeRO","cybersecurity","service-account","zero-trust","network-segmentation","network-policy","cni","baseline","segmentation","security","2026-11-10 10:12:30",false,"---\nname: implementing-kubernetes-network-policy-with-calico\ndescription: >-\n  Installs Calico as the cluster CNI and writes standard Kubernetes NetworkPolicy under it,\n  covering default-deny baselines, policy ordering and precedence, service-account-based\n  selectors, and verifying that policy is genuinely being enforced. Use when adopting Calico\n  as the enforcement CNI, establishing a default-deny baseline, or debugging why a\n  NetworkPolicy is not taking effect under Calico. Keywords: Calico CNI, NetworkPolicy,\n  default deny, policy order, Felix, service account selector. Do not use for Calico-only CRDs\n  such as GlobalNetworkPolicy or DNS egress - use\n  implementing-container-network-policies-with-calico; for CNI-agnostic policy use\n  implementing-network-policies-for-kubernetes.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- calico\n- kubernetes\n- network-policy\n- network-segmentation\n- zero-trust\n- cni\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\n---\n\n# Implementing Kubernetes Network Policy with Calico\n\n## Overview\n\nCalico is an open-source CNI plugin that provides fine-grained network policy enforcement for Kubernetes clusters. It implements the full Kubernetes NetworkPolicy API and extends it with Calico-specific GlobalNetworkPolicy, supporting policy ordering, deny rules, and service-account-based selectors.\n\n\n## When to Use\n\n- When deploying or configuring implementing kubernetes network policy with calico 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+)\n- Calico CNI installed (v3.26+)\n- `kubectl` and `calicoctl` CLI tools\n- Cluster admin RBAC permissions\n\n## Installing Calico\n\n### Operator-based Installation (Recommended)\n\n```bash\n# Install the Tigera operator\nkubectl create -f https:\u002F\u002Fraw.githubusercontent.com\u002Fprojectcalico\u002Fcalico\u002Fv3.27.0\u002Fmanifests\u002Ftigera-operator.yaml\n\n# Install Calico custom resources\nkubectl create -f https:\u002F\u002Fraw.githubusercontent.com\u002Fprojectcalico\u002Fcalico\u002Fv3.27.0\u002Fmanifests\u002Fcustom-resources.yaml\n\n# Verify installation\nkubectl get pods -n calico-system\nwatch kubectl get pods -n calico-system\n\n# Install calicoctl\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Fprojectcalico\u002Fcalico\u002Fv3.27.0\u002Fmanifests\u002Fcalicoctl.yaml\n```\n\n### Verify Calico is Running\n\n```bash\n# Check Calico pods\nkubectl get pods -n calico-system\n\n# Check Calico node status\nkubectl exec -n calico-system calicoctl -- calicoctl node status\n\n# Check IP pools\nkubectl exec -n calico-system calicoctl -- calicoctl get ippool -o wide\n```\n\n## Kubernetes NetworkPolicy\n\n### Default Deny All Traffic\n\n```yaml\n# deny-all-ingress.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: default-deny-ingress\n  namespace: production\nspec:\n  podSelector: {}\n  policyTypes:\n    - Ingress\n\n---\n# deny-all-egress.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: default-deny-egress\n  namespace: production\nspec:\n  podSelector: {}\n  policyTypes:\n    - Egress\n```\n\n### Allow Specific Pod-to-Pod Communication\n\n```yaml\n# allow-frontend-to-backend.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-frontend-to-backend\n  namespace: production\nspec:\n  podSelector:\n    matchLabels:\n      app: backend\n  policyTypes:\n    - Ingress\n  ingress:\n    - from:\n        - podSelector:\n            matchLabels:\n              app: frontend\n      ports:\n        - protocol: TCP\n          port: 8080\n```\n\n### Allow DNS Egress\n\n```yaml\n# allow-dns-egress.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-dns-egress\n  namespace: production\nspec:\n  podSelector: {}\n  policyTypes:\n    - Egress\n  egress:\n    - to:\n        - namespaceSelector: {}\n      ports:\n        - protocol: UDP\n          port: 53\n        - protocol: TCP\n          port: 53\n```\n\n### Namespace Isolation\n\n```yaml\n# allow-same-namespace.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-same-namespace\n  namespace: production\nspec:\n  podSelector: {}\n  policyTypes:\n    - Ingress\n  ingress:\n    - from:\n        - podSelector: {}\n```\n\n## Calico-Specific Policies\n\n### GlobalNetworkPolicy (Cluster-Wide)\n\n```yaml\n# global-deny-external.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: GlobalNetworkPolicy\nmetadata:\n  name: deny-external-ingress\nspec:\n  order: 100\n  selector: \"projectcalico.org\u002Fnamespace != 'ingress-nginx'\"\n  types:\n    - Ingress\n  ingress:\n    - action: Deny\n      source:\n        nets:\n          - 0.0.0.0\u002F0\n      destination: {}\n```\n\n### Calico NetworkPolicy with Deny Rules\n\n```yaml\n# calico-deny-policy.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: NetworkPolicy\nmetadata:\n  name: deny-database-from-frontend\n  namespace: production\nspec:\n  order: 10\n  selector: app == 'database'\n  types:\n    - Ingress\n  ingress:\n    - action: Deny\n      source:\n        selector: app == 'frontend'\n    - action: Allow\n      source:\n        selector: app == 'backend'\n      destination:\n        ports:\n          - 5432\n```\n\n### Service Account Based Policy\n\n```yaml\n# sa-based-policy.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: NetworkPolicy\nmetadata:\n  name: allow-by-service-account\n  namespace: production\nspec:\n  selector: app == 'api'\n  ingress:\n    - action: Allow\n      source:\n        serviceAccounts:\n          names:\n            - frontend-sa\n            - monitoring-sa\n  egress:\n    - action: Allow\n      destination:\n        serviceAccounts:\n          names:\n            - database-sa\n```\n\n### Host Endpoint Protection\n\n```yaml\n# host-endpoint-policy.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: GlobalNetworkPolicy\nmetadata:\n  name: restrict-host-ssh\nspec:\n  order: 10\n  selector: \"has(kubernetes.io\u002Fhostname)\"\n  applyOnForward: false\n  types:\n    - Ingress\n  ingress:\n    - action: Allow\n      protocol: TCP\n      source:\n        nets:\n          - 10.0.0.0\u002F8\n      destination:\n        ports:\n          - 22\n    - action: Deny\n      protocol: TCP\n      destination:\n        ports:\n          - 22\n```\n\n## Calico Policy Tiers\n\n```yaml\n# security-tier.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: Tier\nmetadata:\n  name: security\nspec:\n  order: 100\n\n---\n# platform-tier.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: Tier\nmetadata:\n  name: platform\nspec:\n  order: 200\n```\n\n## Monitoring and Troubleshooting\n\n```bash\n# List all network policies\nkubectl get networkpolicy --all-namespaces\n\n# List Calico-specific policies\nkubectl exec -n calico-system calicoctl -- calicoctl get networkpolicy --all-namespaces -o wide\nkubectl exec -n calico-system calicoctl -- calicoctl get globalnetworkpolicy -o wide\n\n# Check policy evaluation for a specific endpoint\nkubectl exec -n calico-system calicoctl -- calicoctl get workloadendpoint -n production -o yaml\n\n# View Calico logs\nkubectl logs -n calico-system -l k8s-app=calico-node --tail=100\n\n# Test connectivity\nkubectl exec -n production frontend-pod -- wget -qO- --timeout=2 http:\u002F\u002Fbackend-svc:8080\u002Fhealth\n```\n\n## Best Practices\n\n1. **Start with default deny** - Apply deny-all policies to every namespace, then allow specific traffic\n2. **Use labels consistently** - Define a labeling standard for app, tier, environment\n3. **Order policies** - Use Calico policy ordering (`order` field) to control evaluation precedence\n4. **Allow DNS first** - Always create DNS egress rules before applying egress deny policies\n5. **Use GlobalNetworkPolicy** for cluster-wide security baselines\n6. **Test policies in staging** - Validate network connectivity after applying policies\n7. **Monitor denied traffic** - Enable Calico flow logs for visibility into blocked connections\n8. **Use tiers** - Organize policies into security, platform, and application tiers\n","# Implementing Kubernetes Network Policy with Calico\n\n## Overview\n\nCalico is an open-source CNI plugin that provides fine-grained network policy enforcement for Kubernetes clusters. It implements the full Kubernetes NetworkPolicy API and extends it with Calico-specific GlobalNetworkPolicy, supporting policy ordering, deny rules, and service-account-based selectors.\n\n\n## When to Use\n\n- When deploying or configuring implementing kubernetes network policy with calico 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+)\n- Calico CNI installed (v3.26+)\n- `kubectl` and `calicoctl` CLI tools\n- Cluster admin RBAC permissions\n\n## Installing Calico\n\n### Operator-based Installation (Recommended)\n\n```bash\n# Install the Tigera operator\nkubectl create -f https:\u002F\u002Fraw.githubusercontent.com\u002Fprojectcalico\u002Fcalico\u002Fv3.27.0\u002Fmanifests\u002Ftigera-operator.yaml\n\n# Install Calico custom resources\nkubectl create -f https:\u002F\u002Fraw.githubusercontent.com\u002Fprojectcalico\u002Fcalico\u002Fv3.27.0\u002Fmanifests\u002Fcustom-resources.yaml\n\n# Verify installation\nkubectl get pods -n calico-system\nwatch kubectl get pods -n calico-system\n\n# Install calicoctl\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Fprojectcalico\u002Fcalico\u002Fv3.27.0\u002Fmanifests\u002Fcalicoctl.yaml\n```\n\n### Verify Calico is Running\n\n```bash\n# Check Calico pods\nkubectl get pods -n calico-system\n\n# Check Calico node status\nkubectl exec -n calico-system calicoctl -- calicoctl node status\n\n# Check IP pools\nkubectl exec -n calico-system calicoctl -- calicoctl get ippool -o wide\n```\n\n## Kubernetes NetworkPolicy\n\n### Default Deny All Traffic\n\n```yaml\n# deny-all-ingress.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: default-deny-ingress\n  namespace: production\nspec:\n  podSelector: {}\n  policyTypes:\n    - Ingress\n\n---\n# deny-all-egress.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: default-deny-egress\n  namespace: production\nspec:\n  podSelector: {}\n  policyTypes:\n    - Egress\n```\n\n### Allow Specific Pod-to-Pod Communication\n\n```yaml\n# allow-frontend-to-backend.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-frontend-to-backend\n  namespace: production\nspec:\n  podSelector:\n    matchLabels:\n      app: backend\n  policyTypes:\n    - Ingress\n  ingress:\n    - from:\n        - podSelector:\n            matchLabels:\n              app: frontend\n      ports:\n        - protocol: TCP\n          port: 8080\n```\n\n### Allow DNS Egress\n\n```yaml\n# allow-dns-egress.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-dns-egress\n  namespace: production\nspec:\n  podSelector: {}\n  policyTypes:\n    - Egress\n  egress:\n    - to:\n        - namespaceSelector: {}\n      ports:\n        - protocol: UDP\n          port: 53\n        - protocol: TCP\n          port: 53\n```\n\n### Namespace Isolation\n\n```yaml\n# allow-same-namespace.yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-same-namespace\n  namespace: production\nspec:\n  podSelector: {}\n  policyTypes:\n    - Ingress\n  ingress:\n    - from:\n        - podSelector: {}\n```\n\n## Calico-Specific Policies\n\n### GlobalNetworkPolicy (Cluster-Wide)\n\n```yaml\n# global-deny-external.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: GlobalNetworkPolicy\nmetadata:\n  name: deny-external-ingress\nspec:\n  order: 100\n  selector: \"projectcalico.org\u002Fnamespace != 'ingress-nginx'\"\n  types:\n    - Ingress\n  ingress:\n    - action: Deny\n      source:\n        nets:\n          - 0.0.0.0\u002F0\n      destination: {}\n```\n\n### Calico NetworkPolicy with Deny Rules\n\n```yaml\n# calico-deny-policy.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: NetworkPolicy\nmetadata:\n  name: deny-database-from-frontend\n  namespace: production\nspec:\n  order: 10\n  selector: app == 'database'\n  types:\n    - Ingress\n  ingress:\n    - action: Deny\n      source:\n        selector: app == 'frontend'\n    - action: Allow\n      source:\n        selector: app == 'backend'\n      destination:\n        ports:\n          - 5432\n```\n\n### Service Account Based Policy\n\n```yaml\n# sa-based-policy.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: NetworkPolicy\nmetadata:\n  name: allow-by-service-account\n  namespace: production\nspec:\n  selector: app == 'api'\n  ingress:\n    - action: Allow\n      source:\n        serviceAccounts:\n          names:\n            - frontend-sa\n            - monitoring-sa\n  egress:\n    - action: Allow\n      destination:\n        serviceAccounts:\n          names:\n            - database-sa\n```\n\n### Host Endpoint Protection\n\n```yaml\n# host-endpoint-policy.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: GlobalNetworkPolicy\nmetadata:\n  name: restrict-host-ssh\nspec:\n  order: 10\n  selector: \"has(kubernetes.io\u002Fhostname)\"\n  applyOnForward: false\n  types:\n    - Ingress\n  ingress:\n    - action: Allow\n      protocol: TCP\n      source:\n        nets:\n          - 10.0.0.0\u002F8\n      destination:\n        ports:\n          - 22\n    - action: Deny\n      protocol: TCP\n      destination:\n        ports:\n          - 22\n```\n\n## Calico Policy Tiers\n\n```yaml\n# security-tier.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: Tier\nmetadata:\n  name: security\nspec:\n  order: 100\n\n---\n# platform-tier.yaml\napiVersion: projectcalico.org\u002Fv3\nkind: Tier\nmetadata:\n  name: platform\nspec:\n  order: 200\n```\n\n## Monitoring and Troubleshooting\n\n```bash\n# List all network policies\nkubectl get networkpolicy --all-namespaces\n\n# List Calico-specific policies\nkubectl exec -n calico-system calicoctl -- calicoctl get networkpolicy --all-namespaces -o wide\nkubectl exec -n calico-system calicoctl -- calicoctl get globalnetworkpolicy -o wide\n\n# Check policy evaluation for a specific endpoint\nkubectl exec -n calico-system calicoctl -- calicoctl get workloadendpoint -n production -o yaml\n\n# View Calico logs\nkubectl logs -n calico-system -l k8s-app=calico-node --tail=100\n\n# Test connectivity\nkubectl exec -n production frontend-pod -- wget -qO- --timeout=2 http:\u002F\u002Fbackend-svc:8080\u002Fhealth\n```\n\n## Best Practices\n\n1. **Start with default deny** - Apply deny-all policies to every namespace, then allow specific traffic\n2. **Use labels consistently** - Define a labeling standard for app, tier, environment\n3. **Order policies** - Use Calico policy ordering (`order` field) to control evaluation precedence\n4. **Allow DNS first** - Always create DNS egress rules before applying egress deny policies\n5. **Use GlobalNetworkPolicy** for cluster-wide security baselines\n6. **Test policies in staging** - Validate network connectivity after applying policies\n7. **Monitor denied traffic** - Enable Calico flow logs for visibility into blocked connections\n8. **Use tiers** - Organize policies into security, platform, and application tiers\n",{"name":5,"tags":48,"author":49,"domain":34,"license":15,"version":50,"nist_csf":51,"subdomain":32,"description":7,"mitre_attack":56},[26,27,38,37,36,39],"mahipal","1.0",[52,53,54,55],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[57,58,59,60],"T1610","T1611","T1609","T1525","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-kubernetes-network-policy-with-calico",4395,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-kubernetes-network-policy-with-calico",{"tool":77,"command":78},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-kubernetes-network-policy-with-calico",{"tool":80,"command":81},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-kubernetes-network-policy-with-calico","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\u002FSKILL.md",true,[85,91,96,102,106,110,116],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Ftemplate.md","ASSET","资产文件",1972,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\u002Fassets\u002Ftemplate.md",{"path":92,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\u002FLICENSE",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fapi-reference.md","REFERENCE","参考文档",1440,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\u002Freferences\u002Fapi-reference.md",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fstandards.md",2711,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\u002Freferences\u002Fstandards.md",{"path":107,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fworkflows.md",4627,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\u002Freferences\u002Fworkflows.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fagent.py","SCRIPT","脚本",7884,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\u002Fscripts\u002Fagent.py",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fprocess.py",7865,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-network-policy-with-calico\u002Fscripts\u002Fprocess.py",[121,148,170,198,224,251],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":130,"publishedAt":43},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[131,132,133,134,42,34,135,136,29,137,138,139,140,141,142,143,144,145,146,147],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":43},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[154],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},[156,144,157,158,42,28,34,29,159,33,160,161,162,163,164,165,166,167,168,169],"boot","TPM","validating tpm measured boot attestation","verification","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":180,"publishedAt":43},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[176,179],{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},[164,181,182,183,184,34,185,186,159,187,188,189,190,191,192,193,194,195,196,197],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"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":205,"publishedAt":43},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[204],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},[206,207,208,34,209,210,211,212,213,214,215,216,217,218,219,220,161,221,222,223],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":231,"publishedAt":43},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[230],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},[232,233,234,34,235,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":252,"name":253,"nameZh":6,"description":254,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":255,"categories":256,"keywords":258,"publishedAt":43},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[257],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},[42,259,34,260,261,262,263,264,265,266,267,193,268,194,269,270,271,272,273,274],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]