mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-08-31 21:50:50 +03:00
mukul975
cb8d79e068
- Add validated mitre_attack frontmatter to all 754 skills (286 distinct techniques), verified against MITRE ATT&CK v19.1 via the official mitreattack-python library: 0 revoked, deprecated, or invalid IDs - Curate precise per-skill technique IDs for forensics, malware-analysis, threat-intel, and red-team skills (e.g. DCSync -> T1003.006, Kerberoasting -> T1558.003, Pass-the-Ticket -> T1550.003) - Reconcile v19.1 tactic restructuring: Defense Evasion split into Stealth (TA0005) and Defense Impairment (TA0112); revoked T1562.* family and T1070.001/.002 remapped to active equivalents (T1685.*) - Normalize word-split tags across 35 skills (remove filename-derived stopword tags, add semantic cybersecurity tags) - Add api-reference.md for 3 skills that were missing it - Update README ATT&CK section with accurate v19.1 tactic distribution
67 lines
2.2 KiB
Markdown
67 lines
2.2 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
|
|
mitre_attack:
|
|
- T1610
|
|
- T1611
|
|
- T1609
|
|
- T1525
|
|
---
|
|
# 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.
|