AGENT SKILL

configuring-microsegmentation-for-zero-trust

Configures microsegmentation policies to enforce least-privilege workload-to-workload access using tools such as VMware NSX, Illumio, and Calico, preventing lateral movement in zero trust architectures. Use when designing or implementing network microsegmentation as part of a zero trust architecture aligned with NIST SP 800-207.

License 许可
Apache-2.0
最近更新
2026-08-25
Stars
★ 0
Forks
0

01 前言 Front Matter

name
configuring-microsegmentation-for-zero-trust
tags
[ "zero-trust", "microsegmentation", "network-access", "lateral-movement", "network-security" ]
author
mahipal
domain
cybersecurity
license
Apache-2.0
version
1.0
nist_csf
[ "PR.AA-01", "PR.AA-05", "PR.IR-01", "GV.PO-01" ]
subdomain
zero-trust-architecture
description
Configures microsegmentation policies to enforce least-privilege workload-to-workload access using tools such as VMware NSX, Illumio, and Calico, preventing lateral movement in zero trust architectures. Use when designing or implementing network microsegmentation as part of a zero trust architecture aligned with NIST SP 800-207.
mitre_attack
[ "T1021", "T1210", "T1570", "T1046", "T1018" ]

02 资源文件 7

03 SKILL.md 正文

Configuring Microsegmentation for Zero Trust

Prerequisites

  • Understanding of zero trust principles (NIST SP 800-207)
  • Knowledge of network segmentation concepts
  • Familiarity with firewall and SDN technologies
  • Experience with VMware NSX, Illumio, Guardicore, or Cisco ACI

Overview

Microsegmentation divides a network into granular security zones, enforcing least-privilege access between workloads at the application layer rather than relying on traditional VLAN-based segmentation. In a zero trust architecture, microsegmentation eliminates implicit trust between workloads within the same network segment, preventing lateral movement even after an attacker gains initial access.

This skill covers designing microsegmentation policies using workload identity, implementing host-based and network-based enforcement, and validating segmentation effectiveness with tools like Illumio Core and VMware NSX.

When to Use

  • When deploying or configuring configuring microsegmentation for zero trust 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

  • Familiarity with zero trust architecture concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Architecture

Microsegmentation Models

  1. Network-Based (VMware NSX, Cisco ACI): Distributed firewall rules enforced at the hypervisor or network fabric level
  2. Host-Based (Illumio, Guardicore): Agent-based enforcement at the OS level using iptables/WFP rules
  3. Container-Based (Calico, Cilium): Network policies enforced at the pod/container level in Kubernetes
  4. Application-Based (Zscaler Workload Segmentation): Identity-based segmentation based on software identity rather than IP addresses

Enforcement Points

Traditional Segmentation        Microsegmentation
┌─────────────────┐            ┌──────────────────────┐
│  VLAN 10        │            │  Workload A ←policy→ │
│  ┌───┐ ┌───┐   │            │  Workload B ←policy→ │
│  │ A │ │ B │   │            │  Workload C ←policy→ │
│  └───┘ └───┘   │            │  Workload D ←policy→ │
│  (trust each    │            │  (zero trust between  │
│   other)        │            │   every pair)         │
└─────────────────┘            └──────────────────────┘

Key Concepts

Application Dependency Mapping

Before creating segmentation policies, discover actual communication flows between workloads using traffic telemetry. Tools like Illumio, Guardicore, and AppDynamics provide application dependency maps showing which workloads communicate, over which ports, and how frequently.

Policy Modeling

Draft policies in monitor/visibility mode before enforcement. This allows validation that proposed rules will not break legitimate traffic while identifying unnecessary or risky communication paths.

Label-Based Policy

Modern microsegmentation uses labels (role, application, environment, location) instead of IP-based rules. Label-based policies are portable across environments and survive IP changes during migrations.

Ring-Fencing

Isolate critical applications (PCI cardholder data environment, SWIFT financial systems, healthcare PHI) with strict allow-list policies that deny all traffic not explicitly permitted.

Workflow

Phase 1: Discovery and Mapping

  1. Deploy Visibility Agents

    • Install lightweight agents on all workloads (servers, VMs, containers)
    • Configure agents to report real-time traffic telemetry to the management console
    • Allow 2-4 weeks of traffic collection to build a comprehensive flow map
  2. Build Application Dependency Map

    • Review auto-discovered communication flows in the management console
    • Identify application tiers: web servers, app servers, databases, middleware
    • Map legitimate communication paths and flag unexpected connections
    • Document data flows for compliance scope (PCI, HIPAA)
  3. Assign Labels

    • Create a labeling taxonomy: Role (web, app, db), Application (ERP, CRM), Environment (prod, dev, staging), Location (dc1, aws-east)
    • Apply labels to all workloads via the management console or API
    • Validate label accuracy against CMDB and application owner input

Phase 2: Policy Design

  1. Define Segmentation Zones

    • Environment isolation: Production cannot communicate with Development
    • Tier isolation: Database tier only accepts connections from application tier
    • Application ring-fencing: PCI applications isolated from non-PCI workloads
    • Administrative access: Jump servers are the only management path
  2. Create Allow-List Policies

    • For each application, define explicit allow rules for required communication
    • Use label-based rules rather than IP-based where possible
    • Include process-level restrictions where supported (e.g., only httpd on port 443)
    • Set default-deny for all unlisted communication
  3. Model Policies in Test Mode

    • Enable policies in visibility/test mode (do not enforce)
    • Monitor for would-be blocked legitimate traffic
    • Refine policies based on test results over 1-2 weeks
    • Get application owner sign-off before enforcement

Phase 3: Enforcement

  1. Enforce Incrementally

    • Start with the most isolated, lowest-risk application
    • Switch policy from test mode to enforce mode
    • Monitor for application issues in the first 24-48 hours
    • Proceed to next application after validation
  2. Validate Segmentation

    • Run penetration tests attempting lateral movement between segments
    • Verify that blocked traffic generates alerts in the management console
    • Test emergency override procedures (break-glass)
    • Document enforcement status for each application zone

Phase 4: Operational Maintenance

  1. Ongoing Policy Management
    • Integrate with CI/CD: auto-label new workloads from deployment pipelines
    • Review policy violations weekly and investigate anomalies
    • Update policies when applications change or new services deploy
    • Perform quarterly segmentation effectiveness reviews

Validation Checklist

  • [ ] Agents deployed on all in-scope workloads
  • [ ] Application dependency map reviewed and approved by app owners
  • [ ] Labels assigned and validated against CMDB
  • [ ] Policies modeled in test mode with no false positives for 2+ weeks
  • [ ] Policies enforced incrementally with monitoring
  • [ ] Default-deny active for all segmented zones
  • [ ] Lateral movement tests confirm blocked unauthorized traffic
  • [ ] Alerting configured for policy violations
  • [ ] Break-glass procedure documented and tested
  • [ ] Compliance auditor sign-off for regulated environments

References

  • NIST SP 800-207: Zero Trust Architecture
  • CISA Zero Trust Maturity Model v2.0 - Network Pillar
  • Illumio Core Administration Guide
  • VMware NSX Distributed Firewall Configuration Guide
  • Forrester Zero Trust eXtended (ZTX) Framework

04 同仓库更多 Skills

vikasvardhanv
vikasvardhanv/jerry_skills

syllabus

Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.

★ 0
vikasvardhanv
vikasvardhanv/jerry_skills

pulse

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.

★ 0
vikasvardhanv
vikasvardhanv/jerry_skills

patent

Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.

★ 0
vikasvardhanv
vikasvardhanv/jerry_skills

notebooklm

Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.

★ 0
vikasvardhanv
vikasvardhanv/jerry_skills

litreview

Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.

★ 0
vikasvardhanv
vikasvardhanv/jerry_skills

grants

NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.

★ 0