mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-07-17 21:19:40 +03:00
mukul975
efca3ec611
Mapped every skill to NIST CSF 2.0 subcategory IDs (GV/ID/PR/DE/RS/RC functions) based on subdomain and content analysis. Restores 11 skills corrupted during prior rebase, re-enriching with ATLAS, D3FEND, NIST AI RMF, and CSF 2.0 fields. All 754 skills now carry structured mappings for all 5 security frameworks: - MITRE ATT&CK (in tags) - MITRE ATLAS v5.5 (atlas_techniques) - MITRE D3FEND v1.3 (d3fend_techniques) - NIST AI RMF 1.0 (nist_ai_rmf) - NIST CSF 2.0 (nist_csf)
61 lines
2.1 KiB
Markdown
61 lines
2.1 KiB
Markdown
---
|
|
name: implementing-container-network-policies-with-calico
|
|
description: Enforce Kubernetes network segmentation using Calico CNI network policies and global network policies to control
|
|
pod-to-pod traffic, restrict egress, and implement zero-trust microsegmentation.
|
|
domain: cybersecurity
|
|
subdomain: container-security
|
|
tags:
|
|
- container-security
|
|
- kubernetes
|
|
- calico
|
|
- network-policy
|
|
- microsegmentation
|
|
- cni
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- PR.PS-01
|
|
- PR.IR-01
|
|
- ID.AM-08
|
|
- DE.CM-01
|
|
---
|
|
# Implementing Container Network Policies with Calico
|
|
|
|
## Overview
|
|
|
|
Calico provides Kubernetes-native and extended network policy enforcement through its CNI plugin. This skill covers creating and auditing Calico NetworkPolicy and GlobalNetworkPolicy resources to implement pod-to-pod traffic control, namespace isolation, egress restrictions, and DNS-based policy rules using calicoctl and the Kubernetes API.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When deploying or configuring implementing container network policies with calico capabilities in your environment
|
|
- When establishing security controls aligned to compliance requirements
|
|
- When building or improving security architecture for this domain
|
|
- When conducting security assessments that require this implementation
|
|
|
|
## Prerequisites
|
|
|
|
- Kubernetes cluster with Calico CNI installed
|
|
- Python 3.9+ with `kubernetes` client library
|
|
- calicoctl CLI tool installed and configured
|
|
- kubectl access with RBAC permissions for network policy management
|
|
|
|
## Steps
|
|
|
|
### Step 1: Audit Existing Network Policies
|
|
Use calicoctl and kubectl to inventory current network policies and identify unprotected namespaces.
|
|
|
|
### Step 2: Implement Default-Deny Policies
|
|
Create default-deny ingress and egress policies per namespace as a zero-trust baseline.
|
|
|
|
### Step 3: Create Workload-Specific Allow Rules
|
|
Define granular allow rules for legitimate pod-to-pod and pod-to-service communication.
|
|
|
|
### Step 4: Validate Policy Enforcement
|
|
Test connectivity between pods to verify policies are correctly enforced.
|
|
|
|
## Expected Output
|
|
|
|
JSON audit report listing all network policies, unprotected namespaces, policy rule counts, and connectivity test results.
|