[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GYP43GRTSAR77AYCQV8H2P":3,"skill-same:01M6GYP43GRTSAR77AYCQV8H2P":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6GYP43GRTSAR77AYCQV8H2P","implementing-purdue-model-network-segmentation",null,"Implement network segmentation based on the Purdue Enterprise Reference Architecture (PERA) model to separate industrial control system networks into hierarchical security zones from Level 0 physical process through Level 5 enterprise, enforcing strict traffic control between OT and IT domains.","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-purdue-model-network-segmentation\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"implementing","network segmentation","network","model","implementing purdue model network segmentation","segmentation","networks","traffic","domains","control","system","cybersecurity","iec62443","scada","ics","ot-security","Enterprise","defense-in-depth","architecture","implement","2026-11-10 10:12:30",false,"---\nname: implementing-purdue-model-network-segmentation\ndescription: >\n  Implement network segmentation based on the Purdue Enterprise Reference\n  Architecture (PERA) model to separate industrial control system networks into\n  hierarchical security zones from Level 0 physical process through Level 5\n  enterprise, enforcing strict traffic control between OT and IT domains.\ndomain: cybersecurity\nsubdomain: ot-ics-security\ntags: [ot-security, ics, purdue-model, network-segmentation, iec62443, defense-in-depth, dmz, scada]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n\n# Implementing Purdue Model Network Segmentation\n\n## When to Use\n\n- When designing or retrofitting network architecture for an ICS\u002FSCADA environment\n- When implementing IEC 62443 zone and conduit requirements in a brownfield plant\n- When creating the IT\u002FOT DMZ (Level 3.5) to control data flow between enterprise and control networks\n- When remediating audit findings about flat OT networks or direct IT-to-OT connectivity\n- When segmenting a converged IT\u002FOT network after an acquisition or merger\n\n**Do not use** for micro-segmentation within a single Purdue level (see implementing-zone-conduit-model-for-ics), for cloud-native environments without traditional ICS networks, or for network segmentation in purely IT environments.\n\n## Prerequisites\n\n- Complete OT asset inventory with Purdue level classification for each device\n- Network architecture diagram showing current topology, VLANs, and firewall placements\n- Industrial firewalls capable of deep packet inspection for OT protocols (Palo Alto, Fortinet, Cisco)\n- Understanding of required data flows between Purdue levels (historian replication, remote access, patch distribution)\n- Change management approval from plant operations for network modifications\n\n## Workflow\n\n### Step 1: Map Current Architecture to Purdue Levels\n\nClassify all network assets and data flows according to the Purdue Model hierarchy.\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Purdue Model Network Segmentation Planner.\n\nMaps existing OT\u002FIT network assets to Purdue Model levels and generates\nsegmentation recommendations including firewall rules and VLAN assignments.\n\"\"\"\n\nimport json\nimport csv\nimport sys\nfrom collections import defaultdict\nfrom datetime import datetime\nfrom typing import Dict, List\n\n\nPURDUE_LEVELS = {\n    0: {\n        \"name\": \"Physical Process\",\n        \"description\": \"Sensors, actuators, field instruments\",\n        \"typical_devices\": [\"Sensors\", \"Actuators\", \"Drives\", \"Motor starters\"],\n        \"vlan_range\": \"100-109\",\n        \"allowed_protocols\": [\"HART\", \"Profibus\", \"Foundation Fieldbus\", \"IO-Link\"],\n    },\n    1: {\n        \"name\": \"Basic Control\",\n        \"description\": \"PLCs, RTUs, safety controllers\",\n        \"typical_devices\": [\"PLC\", \"RTU\", \"Safety Controller\", \"DCS Controller\"],\n        \"vlan_range\": \"110-119\",\n        \"allowed_protocols\": [\"EtherNet\u002FIP\", \"Profinet\", \"Modbus\u002FTCP\", \"S7comm\", \"OPC UA\"],\n    },\n    2: {\n        \"name\": \"Supervisory Control\",\n        \"description\": \"HMI, SCADA servers, engineering workstations\",\n        \"typical_devices\": [\"HMI\", \"SCADA Server\", \"Engineering Workstation\", \"Batch Server\"],\n        \"vlan_range\": \"120-129\",\n        \"allowed_protocols\": [\"OPC UA\", \"OPC DA\", \"Modbus\u002FTCP\", \"DNP3\", \"HTTPS\"],\n    },\n    3: {\n        \"name\": \"Site Operations\",\n        \"description\": \"Historian, MES, asset management\",\n        \"typical_devices\": [\"Historian\", \"MES Server\", \"Asset Management\", \"Alarm Server\"],\n        \"vlan_range\": \"130-139\",\n        \"allowed_protocols\": [\"OPC UA\", \"SQL\", \"HTTPS\", \"MQTT\"],\n    },\n    3.5: {\n        \"name\": \"IT\u002FOT DMZ\",\n        \"description\": \"Demilitarized zone between IT and OT\",\n        \"typical_devices\": [\"Jump Server\", \"Historian Mirror\", \"Patch Server\", \"AV Update Server\", \"Remote Access Gateway\"],\n        \"vlan_range\": \"150-159\",\n        \"allowed_protocols\": [\"HTTPS\", \"RDP (to jump server only)\", \"SSH\", \"SQL (read replica)\"],\n    },\n    4: {\n        \"name\": \"Enterprise IT\",\n        \"description\": \"Enterprise applications, email, ERP\",\n        \"typical_devices\": [\"ERP Server\", \"Email Server\", \"Business Applications\", \"Active Directory\"],\n        \"vlan_range\": \"200-249\",\n        \"allowed_protocols\": [\"HTTPS\", \"LDAPS\", \"SMTP\", \"SQL\"],\n    },\n    5: {\n        \"name\": \"Enterprise Network \u002F Internet\",\n        \"description\": \"External connections, cloud services, partner networks\",\n        \"typical_devices\": [\"Internet Gateway\", \"VPN Concentrator\", \"Cloud Services\"],\n        \"vlan_range\": \"250-254\",\n        \"allowed_protocols\": [\"HTTPS\", \"IPsec VPN\"],\n    },\n}\n\n\nclass PurdueSegmentationPlanner:\n    \"\"\"Plans Purdue Model network segmentation.\"\"\"\n\n    def __init__(self):\n        self.assets = []\n        self.data_flows = []\n        self.firewall_rules = []\n\n    def load_asset_inventory(self, filepath: str):\n        \"\"\"Load asset inventory from CSV.\"\"\"\n        with open(filepath, \"r\") as f:\n            self.assets = list(csv.DictReader(f))\n        print(f\"[*] Loaded {len(self.assets)} assets\")\n\n    def classify_assets(self):\n        \"\"\"Classify assets into Purdue levels based on type and function.\"\"\"\n        classification = defaultdict(list)\n        for asset in self.assets:\n            level = asset.get(\"purdue_level\", \"\")\n            try:\n                level = float(level)\n            except (ValueError, TypeError):\n                level = self._infer_purdue_level(asset)\n\n            classification[level].append(asset)\n            asset[\"assigned_level\"] = level\n\n        return classification\n\n    def _infer_purdue_level(self, asset: dict) -> float:\n        \"\"\"Infer Purdue level from device type if not explicitly assigned.\"\"\"\n        device_type = asset.get(\"type\", \"\").lower()\n        mapping = {\n            \"sensor\": 0, \"actuator\": 0, \"drive\": 0,\n            \"plc\": 1, \"rtu\": 1, \"safety\": 1, \"dcs\": 1,\n            \"hmi\": 2, \"scada\": 2, \"engineering\": 2,\n            \"historian\": 3, \"mes\": 3, \"alarm\": 3,\n            \"jump\": 3.5, \"patch\": 3.5, \"remote_access\": 3.5,\n            \"erp\": 4, \"email\": 4, \"directory\": 4,\n        }\n        for keyword, level in mapping.items():\n            if keyword in device_type:\n                return level\n        return -1\n\n    def generate_vlan_plan(self, classification: dict) -> list:\n        \"\"\"Generate VLAN assignment plan based on Purdue levels.\"\"\"\n        vlan_plan = []\n        for level, info in PURDUE_LEVELS.items():\n            assets_at_level = classification.get(level, [])\n            vlan_plan.append({\n                \"purdue_level\": level,\n                \"level_name\": info[\"name\"],\n                \"vlan_range\": info[\"vlan_range\"],\n                \"asset_count\": len(assets_at_level),\n                \"allowed_protocols\": info[\"allowed_protocols\"],\n            })\n        return vlan_plan\n\n    def generate_firewall_rules(self) -> list:\n        \"\"\"Generate inter-level firewall rules enforcing Purdue Model boundaries.\"\"\"\n        rules = [\n            {\n                \"rule_id\": 1,\n                \"name\": \"Block direct IT-to-Level1\",\n                \"action\": \"DENY\",\n                \"source_zone\": \"Level_4_Enterprise\",\n                \"dest_zone\": \"Level_1_Control\",\n                \"service\": \"ANY\",\n                \"log\": True,\n                \"description\": \"No direct access from enterprise IT to basic control PLCs\",\n            },\n            {\n                \"rule_id\": 2,\n                \"name\": \"Block direct IT-to-Level2\",\n                \"action\": \"DENY\",\n                \"source_zone\": \"Level_4_Enterprise\",\n                \"dest_zone\": \"Level_2_Supervisory\",\n                \"service\": \"ANY\",\n                \"log\": True,\n                \"description\": \"No direct access from enterprise IT to HMI\u002FSCADA\",\n            },\n            {\n                \"rule_id\": 3,\n                \"name\": \"Allow DMZ-to-Historian-Replica\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_3_Operations\",\n                \"dest_zone\": \"Level_35_DMZ\",\n                \"service\": \"SQL\u002F1433 (read replica push)\",\n                \"log\": True,\n                \"description\": \"Historian pushes data to DMZ replica for IT consumption\",\n            },\n            {\n                \"rule_id\": 4,\n                \"name\": \"Allow IT-to-DMZ-JumpServer\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_4_Enterprise\",\n                \"dest_zone\": \"Level_35_DMZ\",\n                \"service\": \"RDP\u002F3389, SSH\u002F22\",\n                \"log\": True,\n                \"description\": \"IT users access OT via jump server in DMZ only\",\n            },\n            {\n                \"rule_id\": 5,\n                \"name\": \"Allow DMZ-JumpServer-to-Level2\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_35_DMZ\",\n                \"dest_zone\": \"Level_2_Supervisory\",\n                \"service\": \"RDP\u002F3389 (from jump server IP only)\",\n                \"log\": True,\n                \"description\": \"Jump server provides controlled access to HMI\u002FSCADA\",\n            },\n            {\n                \"rule_id\": 6,\n                \"name\": \"Allow Level2-to-Level1\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_2_Supervisory\",\n                \"dest_zone\": \"Level_1_Control\",\n                \"service\": \"Modbus\u002F502, EtherNet-IP\u002F44818, S7comm\u002F102\",\n                \"log\": True,\n                \"description\": \"HMI\u002FSCADA communicates with PLCs using industrial protocols\",\n            },\n            {\n                \"rule_id\": 7,\n                \"name\": \"Block Level1-outbound-internet\",\n                \"action\": \"DENY\",\n                \"source_zone\": \"Level_1_Control\",\n                \"dest_zone\": \"Level_5_Internet\",\n                \"service\": \"ANY\",\n                \"log\": True,\n                \"description\": \"PLCs must never reach the internet directly\",\n            },\n            {\n                \"rule_id\": 8,\n                \"name\": \"Allow patch distribution DMZ-to-Level2\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_35_DMZ\",\n                \"dest_zone\": \"Level_2_Supervisory\",\n                \"service\": \"WSUS\u002F8530\",\n                \"log\": True,\n                \"description\": \"Patch server in DMZ distributes updates to supervisory systems\",\n            },\n            {\n                \"rule_id\": 9,\n                \"name\": \"Default deny all inter-zone\",\n                \"action\": \"DENY\",\n                \"source_zone\": \"ANY\",\n                \"dest_zone\": \"ANY\",\n                \"service\": \"ANY\",\n                \"log\": True,\n                \"description\": \"Default deny all traffic not explicitly permitted\",\n            },\n        ]\n        self.firewall_rules = rules\n        return rules\n\n    def print_segmentation_plan(self, classification: dict):\n        \"\"\"Print the complete segmentation plan.\"\"\"\n        print(f\"\\n{'='*70}\")\n        print(\"PURDUE MODEL NETWORK SEGMENTATION PLAN\")\n        print(f\"{'='*70}\")\n        print(f\"Generated: {datetime.now().isoformat()}\")\n\n        vlan_plan = self.generate_vlan_plan(classification)\n        print(f\"\\n--- VLAN ASSIGNMENT ---\")\n        for v in vlan_plan:\n            print(f\"\\n  {v['level_name']} (Purdue {v['purdue_level']})\")\n            print(f\"    VLAN Range: {v['vlan_range']}\")\n            print(f\"    Assets: {v['asset_count']}\")\n            print(f\"    Allowed Protocols: {', '.join(v['allowed_protocols'])}\")\n\n        print(f\"\\n--- INTER-ZONE FIREWALL RULES ---\")\n        rules = self.generate_firewall_rules()\n        for rule in rules:\n            action_symbol = \"+\" if rule[\"action\"] == \"ALLOW\" else \"X\"\n            print(f\"\\n  [{action_symbol}] Rule {rule['rule_id']}: {rule['name']}\")\n            print(f\"      {rule['source_zone']} -> {rule['dest_zone']}\")\n            print(f\"      Service: {rule['service']}\")\n            print(f\"      Reason: {rule['description']}\")\n\n\nif __name__ == \"__main__\":\n    planner = PurdueSegmentationPlanner()\n    if len(sys.argv) >= 2:\n        planner.load_asset_inventory(sys.argv[1])\n    classification = planner.classify_assets()\n    planner.print_segmentation_plan(classification)\n```\n\n### Step 2: Configure Industrial DMZ (Level 3.5)\n\nThe DMZ is the critical boundary between IT and OT. All data exchange must traverse it -- no direct connections are permitted.\n\n```yaml\n# Level 3.5 DMZ Architecture Configuration\n# All IT-OT data exchange flows through the DMZ\n\ndmz_architecture:\n  zone_name: \"IT_OT_DMZ\"\n  purdue_level: 3.5\n  vlan: 150\n\n  components:\n    historian_replica:\n      purpose: \"Read-only copy of OT historian data for IT\u002Fbusiness access\"\n      direction: \"OT pushes data TO DMZ (unidirectional)\"\n      ip: \"10.10.150.10\"\n      services:\n        - port: 1433\n          protocol: \"SQL\"\n          direction: \"inbound from Level 3 historian only\"\n        - port: 443\n          protocol: \"HTTPS\"\n          direction: \"outbound to Level 4 for IT consumers\"\n\n    jump_server:\n      purpose: \"Controlled remote access point for OT maintenance\"\n      ip: \"10.10.150.20\"\n      services:\n        - port: 3389\n          protocol: \"RDP\"\n          direction: \"inbound from Level 4 with MFA\"\n        - port: 3389\n          protocol: \"RDP\"\n          direction: \"outbound to Level 2 HMIs only\"\n      security_controls:\n        - \"Multi-factor authentication required\"\n        - \"Session recording enabled\"\n        - \"Maximum session duration: 4 hours\"\n        - \"Approval-based access workflow\"\n\n    patch_server:\n      purpose: \"Staging area for tested patches before OT deployment\"\n      ip: \"10.10.150.30\"\n      services:\n        - port: 8530\n          protocol: \"WSUS\"\n          direction: \"pulls from Level 4 WSUS, pushes to Level 2-3\"\n\n    antivirus_relay:\n      purpose: \"AV signature distribution to OT endpoints\"\n      ip: \"10.10.150.40\"\n      services:\n        - port: 443\n          protocol: \"HTTPS\"\n          direction: \"pulls definitions from Level 4, distributes to Level 2-3\"\n\n  firewall_rules:\n    north_firewall:  # Between DMZ and Level 4 Enterprise\n      - allow: \"Level 4 -> DMZ jump server:3389 (with MFA)\"\n      - allow: \"Level 4 -> DMZ historian replica:443 (read-only)\"\n      - allow: \"DMZ patch server -> Level 4 WSUS:8530 (pull only)\"\n      - deny: \"ALL other traffic\"\n\n    south_firewall:  # Between DMZ and Level 3 Operations\n      - allow: \"Level 3 historian -> DMZ replica:1433 (push direction)\"\n      - allow: \"DMZ jump server -> Level 2 HMI:3389 (session-limited)\"\n      - allow: \"DMZ patch server -> Level 2\u002F3:8530 (scheduled)\"\n      - deny: \"ALL other traffic\"\n\n    critical_rule: \"NO traffic passes through DMZ end-to-end. DMZ breaks all connections.\"\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Purdue Model (PERA) | Hierarchical reference architecture organizing industrial networks into levels 0-5 based on function and trust |\n| Level 3.5 DMZ | Demilitarized zone between IT (Level 4) and OT (Level 3), where all cross-boundary data exchange occurs |\n| Defense in Depth | Layered security approach requiring attackers to breach multiple boundaries to reach critical control systems |\n| Data Diode | Hardware-enforced unidirectional communication device ensuring data flows only from OT to IT, never reverse |\n| Zone | Logical grouping of assets sharing common security requirements as defined by IEC 62443 |\n| Conduit | Controlled communication path between zones with defined security policies |\n\n## Common Scenarios\n\n### Scenario: Flat OT Network Remediation\n\n**Context**: An audit reveals that enterprise IT systems can directly communicate with PLCs on the control network. There is no DMZ and no firewall between IT and OT.\n\n**Approach**:\n1. Perform full traffic analysis to identify all legitimate data flows crossing IT\u002FOT boundary\n2. Design DMZ architecture with historian replica, jump server, and patch staging\n3. Deploy industrial firewall between IT and DMZ (north firewall) and between DMZ and OT (south firewall)\n4. Migrate data flows one at a time: start with historian replication through DMZ\n5. Implement jump server for remote access, deprecating direct RDP to OT systems\n6. Block direct IT-to-OT traffic on the north firewall after all flows migrate through DMZ\n7. Validate with penetration test from IT network confirming no direct path to Level 1 controllers\n\n**Pitfalls**: Do not cut over all traffic simultaneously -- migrate flow by flow with rollback plans. Legacy OT systems may use protocols that cannot traverse firewalls doing DPI; test thoroughly in a lab first. Never deploy the DMZ during active production without an agreed maintenance window.\n\n## Output Format\n\n```\nPURDUE MODEL SEGMENTATION REPORT\n====================================\nAssessment Date: YYYY-MM-DD\nFacility: [Plant Name]\n\nCURRENT STATE:\n  Network Type: [Flat\u002FPartially segmented\u002FFully segmented]\n  IT-OT Boundary: [None\u002FFirewall\u002FDMZ with dual firewall]\n  Direct IT-to-PLC paths: [count]\n\nRECOMMENDED ARCHITECTURE:\n  Level 0-1: VLAN 110 (Control Network)\n  Level 2:   VLAN 120 (Supervisory Network)\n  Level 3:   VLAN 130 (Operations Network)\n  Level 3.5: VLAN 150 (IT\u002FOT DMZ)\n  Level 4-5: VLAN 200+ (Enterprise)\n\nDMZ COMPONENTS:\n  - Historian Replica Server\n  - Jump Server (MFA-enabled)\n  - Patch Staging Server\n  - AV Relay Server\n\nFIREWALL RULES: [count] rules generated\nMIGRATION STEPS: [count] phases planned\n```\n","# Implementing Purdue Model Network Segmentation\n\n## When to Use\n\n- When designing or retrofitting network architecture for an ICS\u002FSCADA environment\n- When implementing IEC 62443 zone and conduit requirements in a brownfield plant\n- When creating the IT\u002FOT DMZ (Level 3.5) to control data flow between enterprise and control networks\n- When remediating audit findings about flat OT networks or direct IT-to-OT connectivity\n- When segmenting a converged IT\u002FOT network after an acquisition or merger\n\n**Do not use** for micro-segmentation within a single Purdue level (see implementing-zone-conduit-model-for-ics), for cloud-native environments without traditional ICS networks, or for network segmentation in purely IT environments.\n\n## Prerequisites\n\n- Complete OT asset inventory with Purdue level classification for each device\n- Network architecture diagram showing current topology, VLANs, and firewall placements\n- Industrial firewalls capable of deep packet inspection for OT protocols (Palo Alto, Fortinet, Cisco)\n- Understanding of required data flows between Purdue levels (historian replication, remote access, patch distribution)\n- Change management approval from plant operations for network modifications\n\n## Workflow\n\n### Step 1: Map Current Architecture to Purdue Levels\n\nClassify all network assets and data flows according to the Purdue Model hierarchy.\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Purdue Model Network Segmentation Planner.\n\nMaps existing OT\u002FIT network assets to Purdue Model levels and generates\nsegmentation recommendations including firewall rules and VLAN assignments.\n\"\"\"\n\nimport json\nimport csv\nimport sys\nfrom collections import defaultdict\nfrom datetime import datetime\nfrom typing import Dict, List\n\n\nPURDUE_LEVELS = {\n    0: {\n        \"name\": \"Physical Process\",\n        \"description\": \"Sensors, actuators, field instruments\",\n        \"typical_devices\": [\"Sensors\", \"Actuators\", \"Drives\", \"Motor starters\"],\n        \"vlan_range\": \"100-109\",\n        \"allowed_protocols\": [\"HART\", \"Profibus\", \"Foundation Fieldbus\", \"IO-Link\"],\n    },\n    1: {\n        \"name\": \"Basic Control\",\n        \"description\": \"PLCs, RTUs, safety controllers\",\n        \"typical_devices\": [\"PLC\", \"RTU\", \"Safety Controller\", \"DCS Controller\"],\n        \"vlan_range\": \"110-119\",\n        \"allowed_protocols\": [\"EtherNet\u002FIP\", \"Profinet\", \"Modbus\u002FTCP\", \"S7comm\", \"OPC UA\"],\n    },\n    2: {\n        \"name\": \"Supervisory Control\",\n        \"description\": \"HMI, SCADA servers, engineering workstations\",\n        \"typical_devices\": [\"HMI\", \"SCADA Server\", \"Engineering Workstation\", \"Batch Server\"],\n        \"vlan_range\": \"120-129\",\n        \"allowed_protocols\": [\"OPC UA\", \"OPC DA\", \"Modbus\u002FTCP\", \"DNP3\", \"HTTPS\"],\n    },\n    3: {\n        \"name\": \"Site Operations\",\n        \"description\": \"Historian, MES, asset management\",\n        \"typical_devices\": [\"Historian\", \"MES Server\", \"Asset Management\", \"Alarm Server\"],\n        \"vlan_range\": \"130-139\",\n        \"allowed_protocols\": [\"OPC UA\", \"SQL\", \"HTTPS\", \"MQTT\"],\n    },\n    3.5: {\n        \"name\": \"IT\u002FOT DMZ\",\n        \"description\": \"Demilitarized zone between IT and OT\",\n        \"typical_devices\": [\"Jump Server\", \"Historian Mirror\", \"Patch Server\", \"AV Update Server\", \"Remote Access Gateway\"],\n        \"vlan_range\": \"150-159\",\n        \"allowed_protocols\": [\"HTTPS\", \"RDP (to jump server only)\", \"SSH\", \"SQL (read replica)\"],\n    },\n    4: {\n        \"name\": \"Enterprise IT\",\n        \"description\": \"Enterprise applications, email, ERP\",\n        \"typical_devices\": [\"ERP Server\", \"Email Server\", \"Business Applications\", \"Active Directory\"],\n        \"vlan_range\": \"200-249\",\n        \"allowed_protocols\": [\"HTTPS\", \"LDAPS\", \"SMTP\", \"SQL\"],\n    },\n    5: {\n        \"name\": \"Enterprise Network \u002F Internet\",\n        \"description\": \"External connections, cloud services, partner networks\",\n        \"typical_devices\": [\"Internet Gateway\", \"VPN Concentrator\", \"Cloud Services\"],\n        \"vlan_range\": \"250-254\",\n        \"allowed_protocols\": [\"HTTPS\", \"IPsec VPN\"],\n    },\n}\n\n\nclass PurdueSegmentationPlanner:\n    \"\"\"Plans Purdue Model network segmentation.\"\"\"\n\n    def __init__(self):\n        self.assets = []\n        self.data_flows = []\n        self.firewall_rules = []\n\n    def load_asset_inventory(self, filepath: str):\n        \"\"\"Load asset inventory from CSV.\"\"\"\n        with open(filepath, \"r\") as f:\n            self.assets = list(csv.DictReader(f))\n        print(f\"[*] Loaded {len(self.assets)} assets\")\n\n    def classify_assets(self):\n        \"\"\"Classify assets into Purdue levels based on type and function.\"\"\"\n        classification = defaultdict(list)\n        for asset in self.assets:\n            level = asset.get(\"purdue_level\", \"\")\n            try:\n                level = float(level)\n            except (ValueError, TypeError):\n                level = self._infer_purdue_level(asset)\n\n            classification[level].append(asset)\n            asset[\"assigned_level\"] = level\n\n        return classification\n\n    def _infer_purdue_level(self, asset: dict) -> float:\n        \"\"\"Infer Purdue level from device type if not explicitly assigned.\"\"\"\n        device_type = asset.get(\"type\", \"\").lower()\n        mapping = {\n            \"sensor\": 0, \"actuator\": 0, \"drive\": 0,\n            \"plc\": 1, \"rtu\": 1, \"safety\": 1, \"dcs\": 1,\n            \"hmi\": 2, \"scada\": 2, \"engineering\": 2,\n            \"historian\": 3, \"mes\": 3, \"alarm\": 3,\n            \"jump\": 3.5, \"patch\": 3.5, \"remote_access\": 3.5,\n            \"erp\": 4, \"email\": 4, \"directory\": 4,\n        }\n        for keyword, level in mapping.items():\n            if keyword in device_type:\n                return level\n        return -1\n\n    def generate_vlan_plan(self, classification: dict) -> list:\n        \"\"\"Generate VLAN assignment plan based on Purdue levels.\"\"\"\n        vlan_plan = []\n        for level, info in PURDUE_LEVELS.items():\n            assets_at_level = classification.get(level, [])\n            vlan_plan.append({\n                \"purdue_level\": level,\n                \"level_name\": info[\"name\"],\n                \"vlan_range\": info[\"vlan_range\"],\n                \"asset_count\": len(assets_at_level),\n                \"allowed_protocols\": info[\"allowed_protocols\"],\n            })\n        return vlan_plan\n\n    def generate_firewall_rules(self) -> list:\n        \"\"\"Generate inter-level firewall rules enforcing Purdue Model boundaries.\"\"\"\n        rules = [\n            {\n                \"rule_id\": 1,\n                \"name\": \"Block direct IT-to-Level1\",\n                \"action\": \"DENY\",\n                \"source_zone\": \"Level_4_Enterprise\",\n                \"dest_zone\": \"Level_1_Control\",\n                \"service\": \"ANY\",\n                \"log\": True,\n                \"description\": \"No direct access from enterprise IT to basic control PLCs\",\n            },\n            {\n                \"rule_id\": 2,\n                \"name\": \"Block direct IT-to-Level2\",\n                \"action\": \"DENY\",\n                \"source_zone\": \"Level_4_Enterprise\",\n                \"dest_zone\": \"Level_2_Supervisory\",\n                \"service\": \"ANY\",\n                \"log\": True,\n                \"description\": \"No direct access from enterprise IT to HMI\u002FSCADA\",\n            },\n            {\n                \"rule_id\": 3,\n                \"name\": \"Allow DMZ-to-Historian-Replica\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_3_Operations\",\n                \"dest_zone\": \"Level_35_DMZ\",\n                \"service\": \"SQL\u002F1433 (read replica push)\",\n                \"log\": True,\n                \"description\": \"Historian pushes data to DMZ replica for IT consumption\",\n            },\n            {\n                \"rule_id\": 4,\n                \"name\": \"Allow IT-to-DMZ-JumpServer\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_4_Enterprise\",\n                \"dest_zone\": \"Level_35_DMZ\",\n                \"service\": \"RDP\u002F3389, SSH\u002F22\",\n                \"log\": True,\n                \"description\": \"IT users access OT via jump server in DMZ only\",\n            },\n            {\n                \"rule_id\": 5,\n                \"name\": \"Allow DMZ-JumpServer-to-Level2\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_35_DMZ\",\n                \"dest_zone\": \"Level_2_Supervisory\",\n                \"service\": \"RDP\u002F3389 (from jump server IP only)\",\n                \"log\": True,\n                \"description\": \"Jump server provides controlled access to HMI\u002FSCADA\",\n            },\n            {\n                \"rule_id\": 6,\n                \"name\": \"Allow Level2-to-Level1\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_2_Supervisory\",\n                \"dest_zone\": \"Level_1_Control\",\n                \"service\": \"Modbus\u002F502, EtherNet-IP\u002F44818, S7comm\u002F102\",\n                \"log\": True,\n                \"description\": \"HMI\u002FSCADA communicates with PLCs using industrial protocols\",\n            },\n            {\n                \"rule_id\": 7,\n                \"name\": \"Block Level1-outbound-internet\",\n                \"action\": \"DENY\",\n                \"source_zone\": \"Level_1_Control\",\n                \"dest_zone\": \"Level_5_Internet\",\n                \"service\": \"ANY\",\n                \"log\": True,\n                \"description\": \"PLCs must never reach the internet directly\",\n            },\n            {\n                \"rule_id\": 8,\n                \"name\": \"Allow patch distribution DMZ-to-Level2\",\n                \"action\": \"ALLOW\",\n                \"source_zone\": \"Level_35_DMZ\",\n                \"dest_zone\": \"Level_2_Supervisory\",\n                \"service\": \"WSUS\u002F8530\",\n                \"log\": True,\n                \"description\": \"Patch server in DMZ distributes updates to supervisory systems\",\n            },\n            {\n                \"rule_id\": 9,\n                \"name\": \"Default deny all inter-zone\",\n                \"action\": \"DENY\",\n                \"source_zone\": \"ANY\",\n                \"dest_zone\": \"ANY\",\n                \"service\": \"ANY\",\n                \"log\": True,\n                \"description\": \"Default deny all traffic not explicitly permitted\",\n            },\n        ]\n        self.firewall_rules = rules\n        return rules\n\n    def print_segmentation_plan(self, classification: dict):\n        \"\"\"Print the complete segmentation plan.\"\"\"\n        print(f\"\\n{'='*70}\")\n        print(\"PURDUE MODEL NETWORK SEGMENTATION PLAN\")\n        print(f\"{'='*70}\")\n        print(f\"Generated: {datetime.now().isoformat()}\")\n\n        vlan_plan = self.generate_vlan_plan(classification)\n        print(f\"\\n--- VLAN ASSIGNMENT ---\")\n        for v in vlan_plan:\n            print(f\"\\n  {v['level_name']} (Purdue {v['purdue_level']})\")\n            print(f\"    VLAN Range: {v['vlan_range']}\")\n            print(f\"    Assets: {v['asset_count']}\")\n            print(f\"    Allowed Protocols: {', '.join(v['allowed_protocols'])}\")\n\n        print(f\"\\n--- INTER-ZONE FIREWALL RULES ---\")\n        rules = self.generate_firewall_rules()\n        for rule in rules:\n            action_symbol = \"+\" if rule[\"action\"] == \"ALLOW\" else \"X\"\n            print(f\"\\n  [{action_symbol}] Rule {rule['rule_id']}: {rule['name']}\")\n            print(f\"      {rule['source_zone']} -> {rule['dest_zone']}\")\n            print(f\"      Service: {rule['service']}\")\n            print(f\"      Reason: {rule['description']}\")\n\n\nif __name__ == \"__main__\":\n    planner = PurdueSegmentationPlanner()\n    if len(sys.argv) >= 2:\n        planner.load_asset_inventory(sys.argv[1])\n    classification = planner.classify_assets()\n    planner.print_segmentation_plan(classification)\n```\n\n### Step 2: Configure Industrial DMZ (Level 3.5)\n\nThe DMZ is the critical boundary between IT and OT. All data exchange must traverse it -- no direct connections are permitted.\n\n```yaml\n# Level 3.5 DMZ Architecture Configuration\n# All IT-OT data exchange flows through the DMZ\n\ndmz_architecture:\n  zone_name: \"IT_OT_DMZ\"\n  purdue_level: 3.5\n  vlan: 150\n\n  components:\n    historian_replica:\n      purpose: \"Read-only copy of OT historian data for IT\u002Fbusiness access\"\n      direction: \"OT pushes data TO DMZ (unidirectional)\"\n      ip: \"10.10.150.10\"\n      services:\n        - port: 1433\n          protocol: \"SQL\"\n          direction: \"inbound from Level 3 historian only\"\n        - port: 443\n          protocol: \"HTTPS\"\n          direction: \"outbound to Level 4 for IT consumers\"\n\n    jump_server:\n      purpose: \"Controlled remote access point for OT maintenance\"\n      ip: \"10.10.150.20\"\n      services:\n        - port: 3389\n          protocol: \"RDP\"\n          direction: \"inbound from Level 4 with MFA\"\n        - port: 3389\n          protocol: \"RDP\"\n          direction: \"outbound to Level 2 HMIs only\"\n      security_controls:\n        - \"Multi-factor authentication required\"\n        - \"Session recording enabled\"\n        - \"Maximum session duration: 4 hours\"\n        - \"Approval-based access workflow\"\n\n    patch_server:\n      purpose: \"Staging area for tested patches before OT deployment\"\n      ip: \"10.10.150.30\"\n      services:\n        - port: 8530\n          protocol: \"WSUS\"\n          direction: \"pulls from Level 4 WSUS, pushes to Level 2-3\"\n\n    antivirus_relay:\n      purpose: \"AV signature distribution to OT endpoints\"\n      ip: \"10.10.150.40\"\n      services:\n        - port: 443\n          protocol: \"HTTPS\"\n          direction: \"pulls definitions from Level 4, distributes to Level 2-3\"\n\n  firewall_rules:\n    north_firewall:  # Between DMZ and Level 4 Enterprise\n      - allow: \"Level 4 -> DMZ jump server:3389 (with MFA)\"\n      - allow: \"Level 4 -> DMZ historian replica:443 (read-only)\"\n      - allow: \"DMZ patch server -> Level 4 WSUS:8530 (pull only)\"\n      - deny: \"ALL other traffic\"\n\n    south_firewall:  # Between DMZ and Level 3 Operations\n      - allow: \"Level 3 historian -> DMZ replica:1433 (push direction)\"\n      - allow: \"DMZ jump server -> Level 2 HMI:3389 (session-limited)\"\n      - allow: \"DMZ patch server -> Level 2\u002F3:8530 (scheduled)\"\n      - deny: \"ALL other traffic\"\n\n    critical_rule: \"NO traffic passes through DMZ end-to-end. DMZ breaks all connections.\"\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Purdue Model (PERA) | Hierarchical reference architecture organizing industrial networks into levels 0-5 based on function and trust |\n| Level 3.5 DMZ | Demilitarized zone between IT (Level 4) and OT (Level 3), where all cross-boundary data exchange occurs |\n| Defense in Depth | Layered security approach requiring attackers to breach multiple boundaries to reach critical control systems |\n| Data Diode | Hardware-enforced unidirectional communication device ensuring data flows only from OT to IT, never reverse |\n| Zone | Logical grouping of assets sharing common security requirements as defined by IEC 62443 |\n| Conduit | Controlled communication path between zones with defined security policies |\n\n## Common Scenarios\n\n### Scenario: Flat OT Network Remediation\n\n**Context**: An audit reveals that enterprise IT systems can directly communicate with PLCs on the control network. There is no DMZ and no firewall between IT and OT.\n\n**Approach**:\n1. Perform full traffic analysis to identify all legitimate data flows crossing IT\u002FOT boundary\n2. Design DMZ architecture with historian replica, jump server, and patch staging\n3. Deploy industrial firewall between IT and DMZ (north firewall) and between DMZ and OT (south firewall)\n4. Migrate data flows one at a time: start with historian replication through DMZ\n5. Implement jump server for remote access, deprecating direct RDP to OT systems\n6. Block direct IT-to-OT traffic on the north firewall after all flows migrate through DMZ\n7. Validate with penetration test from IT network confirming no direct path to Level 1 controllers\n\n**Pitfalls**: Do not cut over all traffic simultaneously -- migrate flow by flow with rollback plans. Legacy OT systems may use protocols that cannot traverse firewalls doing DPI; test thoroughly in a lab first. Never deploy the DMZ during active production without an agreed maintenance window.\n\n## Output Format\n\n```\nPURDUE MODEL SEGMENTATION REPORT\n====================================\nAssessment Date: YYYY-MM-DD\nFacility: [Plant Name]\n\nCURRENT STATE:\n  Network Type: [Flat\u002FPartially segmented\u002FFully segmented]\n  IT-OT Boundary: [None\u002FFirewall\u002FDMZ with dual firewall]\n  Direct IT-to-PLC paths: [count]\n\nRECOMMENDED ARCHITECTURE:\n  Level 0-1: VLAN 110 (Control Network)\n  Level 2:   VLAN 120 (Supervisory Network)\n  Level 3:   VLAN 130 (Operations Network)\n  Level 3.5: VLAN 150 (IT\u002FOT DMZ)\n  Level 4-5: VLAN 200+ (Enterprise)\n\nDMZ COMPONENTS:\n  - Historian Replica Server\n  - Jump Server (MFA-enabled)\n  - Patch Staging Server\n  - AV Relay Server\n\nFIREWALL RULES: [count] rules generated\nMIGRATION STEPS: [count] phases planned\n```\n",{"name":5,"tags":43,"author":47,"domain":29,"license":14,"version":48,"subdomain":49,"description":50},[33,32,44,45,30,35,46,31],"purdue-model","network-segmentation","dmz","mahipal","1.0","ot-ics-security","Implement network segmentation based on the Purdue Enterprise Reference Architecture (PERA) model to separate industrial control system networks into hierarchical security zones from Level 0 physical process through Level 5 enterprise, enforcing strict traffic control between OT and IT domains.\n","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-purdue-model-network-segmentation",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add micsapp\u002Fmicstec-skills --skill implementing-purdue-model-network-segmentation",{"tool":64,"command":65},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill implementing-purdue-model-network-segmentation",{"tool":67,"command":68},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill implementing-purdue-model-network-segmentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-purdue-model-network-segmentation\u002FSKILL.md",true,[72,77,83],{"path":73,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-purdue-model-network-segmentation\u002FLICENSE",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi-reference.md","REFERENCE","参考文档",5646,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-purdue-model-network-segmentation\u002Freferences\u002Fapi-reference.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fagent.py","SCRIPT","脚本",7709,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-purdue-model-network-segmentation\u002Fscripts\u002Fagent.py",[90,126,155,176,196,221],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":107,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[97,102],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[36,108,109,110,111,112,113,114,20,115,116,117,118,119,120,121,122,123,124,125],"azure","azure apim architecture","component","authentication","gateway","topology","Optimization","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":140,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[132,133,136,139],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},{"categoryNo":134,"categoryName":135,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":137,"categoryName":138,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[141,142,143,144,108,145,146,147,148,149,150,151,115,116,122,152,153,123,154,18],"deployment","apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[161],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[163,164,165,166,108,111,115,116,167,168,169,170,171,172,173,123,174,175,18,125],"policy","authoring","apim policy authoring","security","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":184,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[182,183],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[185,166,186,115,170,187,108,141,188,189,190,191,116,192,123,193,194,195,124,125],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[203,204,205,143,206,207,208,209,115,210,211,212,213,214,215,216,217,218,219,220],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[223,228,229,230,231,232,233,168,234,235],"npm","js","calculate","node","math","user","compute","errors"]