--- name: implementing-network-segmentation-with-firewall-zones description: Designs and implements network segmentation using firewall security zones, VLANs, inter-zone ACLs, and workload-level microsegmentation to restrict east-west lateral movement and enforce least-privilege access. Use when architecting security zones, writing inter-zone firewall policies, or meeting PCI DSS/HIPAA/NIST 800-53/zero-trust segmentation requirements for dynamic or traditional network environments. domain: cybersecurity subdomain: network-security tags: - network-segmentation - firewall-zones - vlan - microsegmentation - lateral-movement - zero-trust - acl - east-west-traffic - pci-dss version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - PR.IR-01 - DE.CM-01 - ID.AM-03 - PR.DS-02 mitre_attack: - T1046 - T1040 - T1557 - T1071 - T1021 --- # Implementing Network Segmentation with Firewall Zones ## Overview Network segmentation divides a flat network into isolated security zones with firewall-enforced boundaries to contain breaches, restrict lateral movement, and enforce least-privilege access between workloads. Segmentation is a foundational control required by PCI DSS, HIPAA, NIST 800-53, and zero trust architectures. Modern segmentation combines traditional VLAN-based approaches with microsegmentation at the workload level for granular east-west traffic control. This skill covers designing zone architectures, configuring inter-zone firewall policies, implementing VLAN segmentation on switches, and deploying microsegmentation for dynamic environments. ## When to Use - When deploying or configuring implementing network segmentation with firewall zones 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 - Network topology documentation with asset inventory - Firewall supporting zone-based policies (Palo Alto, Fortinet, Cisco Firepower) - Managed switches with VLAN support (802.1Q trunking) - Traffic flow documentation or NetFlow data for baseline analysis - Compliance requirements (PCI DSS scope, HIPAA ePHI boundaries) ## Core Concepts ### Zone Architecture Tiers | Zone | Trust Level | Examples | Access Policy | |------|-------------|----------|---------------| | **Internet** | None | Public internet | Default deny inbound | | **DMZ** | Low | Web servers, mail relays, DNS | Limited inbound, restricted outbound | | **Guest** | Low | Guest WiFi, visitor network | Internet only, no internal access | | **Corporate** | Medium | Employee workstations, printers | Controlled access to internal resources | | **Server/Data Center** | High | Application servers, databases | Strict ACLs, limited admin access | | **PCI CDE** | Critical | Payment systems, card data | PCI DSS compliant isolation | | **Management** | Critical | Network devices, hypervisors, IPMI | Highly restricted, jump box only | | **OT/SCADA** | Critical | Industrial control systems | Air-gapped or strictly firewalled | ### Segmentation Approaches | Approach | Scope | Granularity | Use Case | |----------|-------|-------------|----------| | **VLAN Segmentation** | Layer 2 | Subnet-level | Department separation, guest isolation | | **Firewall Zones** | Layer 3-7 | Zone-to-zone | Inter-zone policy enforcement | | **ACLs on Routers** | Layer 3-4 | Subnet/port | Quick filtering at routing boundaries | | **Microsegmentation** | Layer 3-7 | Workload-level | Zero trust, container environments | | **SGT/TrustSec** | Layer 2-7 | Tag-based | Identity-based segmentation | ## Workflow ### Step 1: Map Traffic Flows and Define Zones Before implementing segmentation, capture baseline traffic: ```bash # Capture NetFlow data to understand existing traffic patterns nfdump -R /var/cache/nfdump/ -s srcip/bytes -n 50 # Identify east-west traffic between subnets nfdump -R /var/cache/nfdump/ -s record/bytes \ 'src net 10.0.0.0/8 and dst net 10.0.0.0/8' -n 100 # Map application dependencies # Document which servers need to communicate with which other servers ``` ### Step 2: Configure VLANs on Switches ``` ! Core switch VLAN configuration vlan 10 name Management vlan 20 name Corporate-Users vlan 30 name Servers vlan 40 name PCI-CDE vlan 50 name Guest vlan 60 name DMZ vlan 99 name Native-Unused ! Trunk port to firewall interface GigabitEthernet1/0/1 description Trunk-to-Firewall switchport trunk encapsulation dot1q switchport mode trunk switchport trunk allowed vlan 10,20,30,40,50,60 switchport trunk native vlan 99 switchport nonegotiate ! Access port for corporate users interface range GigabitEthernet1/0/2-24 switchport mode access switchport access vlan 20 spanning-tree portfast ! Access port for servers interface range GigabitEthernet1/0/25-36 switchport mode access switchport access vlan 30 ! Prevent VLAN hopping interface range GigabitEthernet1/0/37-48 switchport mode access switchport access vlan 99 shutdown ``` ### Step 3: Configure Firewall Zone Policies **Palo Alto zone-based policy:** ``` # Define zones on firewall sub-interfaces set network interface ethernet ethernet1/1 layer3 units ethernet1/1.10 tag 10 ip 10.0.10.1/24 set network interface ethernet ethernet1/1 layer3 units ethernet1/1.20 tag 20 ip 10.0.20.1/24 set network interface ethernet ethernet1/1 layer3 units ethernet1/1.30 tag 30 ip 10.0.30.1/24 set network interface ethernet ethernet1/1 layer3 units ethernet1/1.40 tag 40 ip 10.0.40.1/24 set zone Management network layer3 ethernet1/1.10 set zone Corporate network layer3 ethernet1/1.20 set zone Servers network layer3 ethernet1/1.30 set zone PCI-CDE network layer3 ethernet1/1.40 # Inter-zone policies (deny by default, explicitly allow) # Corporate -> Servers (only specific apps) set rulebase security rules Corp-to-Servers from Corporate to Servers set rulebase security rules Corp-to-Servers application [ web-browsing ssl dns smtp ] set rulebase security rules Corp-to-Servers action allow set rulebase security rules Corp-to-Servers profile-setting group Standard-Profiles # Corporate -> PCI (DENY) set rulebase security rules Corp-to-PCI from Corporate to PCI-CDE set rulebase security rules Corp-to-PCI action deny log-end yes # Servers -> PCI (only payment processing) set rulebase security rules Servers-to-PCI from Servers to PCI-CDE set rulebase security rules Servers-to-PCI source [ 10.0.30.10 ] set rulebase security rules Servers-to-PCI destination [ 10.0.40.10 ] set rulebase security rules Servers-to-PCI application [ ssl ] set rulebase security rules Servers-to-PCI service service-https set rulebase security rules Servers-to-PCI action allow # Management -> All (admin access via jump box) set rulebase security rules Mgmt-Admin from Management to [ Servers PCI-CDE ] set rulebase security rules Mgmt-Admin source [ 10.0.10.50 ] set rulebase security rules Mgmt-Admin application [ ssh rdp ] set rulebase security rules Mgmt-Admin source-user [ admin-group ] set rulebase security rules Mgmt-Admin action allow # Intra-zone deny (prevent lateral movement within zone) set rulebase security rules Deny-Intrazone from Corporate to Corporate set rulebase security rules Deny-Intrazone action deny log-end yes # Default deny all set rulebase security rules Deny-All from any to any set rulebase security rules Deny-All action deny log-end yes ``` ### Step 4: Implement Inter-VLAN Routing ACLs For additional layer 3 filtering on the router/L3 switch: ``` ! ACL: Corporate can only reach specific server ports ip access-list extended CORP-TO-SERVERS permit tcp 10.0.20.0 0.0.0.255 10.0.30.0 0.0.0.255 eq 80 permit tcp 10.0.20.0 0.0.0.255 10.0.30.0 0.0.0.255 eq 443 permit tcp 10.0.20.0 0.0.0.255 10.0.30.0 0.0.0.255 eq 25 permit udp 10.0.20.0 0.0.0.255 10.0.30.10 0.0.0.0 eq 53 deny ip 10.0.20.0 0.0.0.255 10.0.30.0 0.0.0.255 log ! ACL: PCI CDE isolation ip access-list extended PCI-ISOLATION permit tcp host 10.0.30.10 host 10.0.40.10 eq 443 permit tcp 10.0.10.50 0.0.0.0 10.0.40.0 0.0.0.255 eq 22 deny ip any 10.0.40.0 0.0.0.255 log ! Apply ACLs to VLAN interfaces interface Vlan20 ip address 10.0.20.1 255.255.255.0 ip access-group CORP-TO-SERVERS out interface Vlan40 ip address 10.0.40.1 255.255.255.0 ip access-group PCI-ISOLATION in ``` ### Step 5: Validate Segmentation ```python #!/usr/bin/env python3 """Network segmentation validation - tests connectivity between zones.""" import subprocess import sys import json from datetime import datetime class SegmentationValidator: """Test network segmentation controls between zones.""" def __init__(self): self.results = [] def test_connectivity(self, src_desc: str, dst_ip: str, port: int, protocol: str = "tcp", expected: str = "blocked"): """Test if connectivity exists between source and destination.""" try: if protocol == "tcp": cmd = ["nc", "-z", "-w", "3", dst_ip, str(port)] elif protocol == "udp": cmd = ["nc", "-z", "-u", "-w", "3", dst_ip, str(port)] elif protocol == "icmp": cmd = ["ping", "-c", "1", "-W", "3", dst_ip] else: return result = subprocess.run(cmd, capture_output=True, timeout=5) actual = "open" if result.returncode == 0 else "blocked" except subprocess.TimeoutExpired: actual = "blocked" except FileNotFoundError: actual = "error" status = "PASS" if actual == expected else "FAIL" self.results.append({ "source": src_desc, "destination": f"{dst_ip}:{port}/{protocol}", "expected": expected, "actual": actual, "status": status, }) symbol = "[+]" if status == "PASS" else "[!]" print(f" {symbol} {src_desc} -> {dst_ip}:{port}/{protocol} " f"| Expected: {expected} | Actual: {actual} | {status}") def run_validation(self): """Run segmentation validation tests.""" print(f"\n{'='*70}") print("NETWORK SEGMENTATION VALIDATION") print(f"{'='*70}") print(f"Date: {datetime.now().isoformat()}\n") # Tests that SHOULD be blocked print("[*] Testing controls that should BLOCK traffic:") self.test_connectivity("Corporate", "10.0.40.10", 443, "tcp", "blocked") self.test_connectivity("Corporate", "10.0.40.10", 22, "tcp", "blocked") self.test_connectivity("Guest", "10.0.30.10", 80, "tcp", "blocked") self.test_connectivity("Guest", "10.0.20.1", 0, "icmp", "blocked") # Tests that SHOULD be allowed print("\n[*] Testing controls that should ALLOW traffic:") self.test_connectivity("Corporate", "10.0.30.10", 443, "tcp", "open") self.test_connectivity("Corporate", "10.0.30.10", 80, "tcp", "open") self.test_connectivity("Management", "10.0.30.10", 22, "tcp", "open") # Summary passed = sum(1 for r in self.results if r["status"] == "PASS") failed = sum(1 for r in self.results if r["status"] == "FAIL") print(f"\n{'='*70}") print(f"Results: {passed} PASSED, {failed} FAILED out of {len(self.results)} tests") if failed > 0: print(f"\n[!] FAILED TESTS:") for r in self.results: if r["status"] == "FAIL": print(f" - {r['source']} -> {r['destination']}: " f"expected {r['expected']}, got {r['actual']}") # Save report report = { "date": datetime.now().isoformat(), "total_tests": len(self.results), "passed": passed, "failed": failed, "results": self.results, } report_path = f"segmentation_test_{datetime.now().strftime('%Y%m%d')}.json" with open(report_path, 'w') as f: json.dump(report, f, indent=2) print(f"\nReport saved to: {report_path}") if __name__ == "__main__": validator = SegmentationValidator() validator.run_validation() ``` ## Best Practices - **Default Deny** - Start with deny-all inter-zone rules and explicitly allow required traffic - **Document Flows** - Map all legitimate traffic flows before implementing restrictions - **Segment by Sensitivity** - Group assets by data classification and compliance scope - **Intra-Zone Control** - Block lateral movement within zones, not just between zones - **Limit Management Access** - Restrict management plane to a dedicated zone with jump boxes - **Regular Validation** - Test segmentation controls quarterly with automated tools - **Monitor Denied Traffic** - Log and review denied inter-zone traffic for policy refinement - **PCI Scope Reduction** - Use segmentation to minimize PCI DSS Cardholder Data Environment scope ## References - [CISA Zero Trust Microsegmentation Guidance](https://www.cisa.gov/sites/default/files/2025-07/ZT-Microsegmentation-Guidance-Part-One_508c.pdf) - [NIST SP 800-125B - Secure Virtual Network Configuration](https://csrc.nist.gov/publications/detail/sp/800-125b/final) - [PCI DSS v4.0 - Network Segmentation](https://www.pcisecuritystandards.org/) - [Faddom Network Segmentation Best Practices 2025](https://faddom.com/10-network-segmentation-best-practices-to-know-in-2025/) --- Source attribution: mukul975 Original project: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-network-segmentation-with-firewall-zones/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: mukul975 Original project: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-network-segmentation-with-firewall-zones/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Operations Roles: DevOps / SRE, IT Operations, Security Engineer Specialties: Backend, DevOps Tools: Fortinet, Cisco Firepower, Palo Alto Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 6051aed18cbccc98d8fc8254eff848c780b96c894c7000a27e76cea347165635