| Zone | Trust Level | ตัวอย่าง Systems/Assets | Access Policy (Typical) |
| Internet / Untrusted | 0 (No Trust) | Internet, Public Cloud, Partner Networks (Unmanaged) | Deny All Inbound (Except Published Services via DMZ/Proxy), Allow Outbound (with Inspection) |
| DMZ / Perimeter / Public Services | Low | Web Servers, Email Gateways, VPN Gateways, DNS Public, Proxy, Load Balancers, API Gateways | Allow Specific Inbound (80/443/53/VPN) from Internet, Restrict Outbound (No Direct Internet), No Direct Access to Internal |
| Internal / Private / Trusted | Medium-High | User Workstations, Internal Servers (AD, File, Print), Management Systems | Allow Internal ↔ Internal (Segmented), Controlled Outbound (Proxy), No Direct Internet Inbound |
| Restricted / Secure / Data Center | High | Database Servers, Application Servers, PKI, HSM, Backup Systems, Core Infrastructure | Allow Only from Specific App Zones (App→DB), No Internet, No User Direct Access, Strict Change Control |
| Management / Out-of-Band | Highest | Network Devices (Switch, Router, Firewall Mgmt), Server iDRAC/iLO/iLOM, Hypervisor Mgmt, Security Tools (SIEM, Vuln Scanner) | Allow Only from Dedicated Mgmt Workstations (PAW/Jump Host), MFA Required, No Internet, Encrypted Protocols Only (SSH, HTTPS, SNMPv3) |
ตัวอย่าง Security Zones ในสถาปัตยกรรมจริง (Real-world Examples)
1. Enterprise On-Premises (Traditional)
Internet
│
[Edge Firewall / Internet Firewall]
│
┌── DMZ Zone ────────────────────────────────┐
│ Web Proxy, Email Gateway, VPN Gateway, │
│ Public DNS, Web App Firewall (WAF) │
└────────────────────────────────────────────┘
│ (Strict Inter-zone FW)
┌── Internal Zone ───────────────────────────┐
│ User VLANs (by Dept/Floor/Building), │
│ Internal Servers (AD, DHCP, DNS, File), │
│ Wireless Corporate (802.1X) │
└────────────────────────────────────────────┘
│ (Strict Inter-zone FW)
┌── Server/Application Zone ─────────────────┐
│ App Servers, API Gateways, Middleware, │
│ Internal Web Apps, Dev/Test (Separate) │
└────────────────────────────────────────────┘
│ (Strict Inter-zone FW)
┌── Data Zone ───────────────────────────────┐
│ Database Clusters, Data Warehouse, │
│ Storage (SAN/NAS), Backup Servers │
└────────────────────────────────────────────┘
│ (Strict Inter-zone FW)
┌── Management Zone ─────────────────────────┐
│ Network Mgmt (NMS), Server Mgmt (iDRAC), │
│ Security Mgmt (SIEM, AV Console, FW Mgmt),│
│ Privileged Access Workstations (PAW) │
└────────────────────────────────────────────┘
2. Cloud (Azure/AWS/GCP) - Landing Zone Pattern
Azure Example:
Management Group: Root
├─ Platform
│ ├─ Connectivity (Hub VNet: Firewall, VPN, ExpressRoute, Bastion)
│ ├─ Identity (Entra ID, AD DS)
│ ├─ Management (Monitor, Security Center, Policy, Automation)
│ └─ Operations (Log Analytics, Sentinel)
├─ Landing Zones (Subscription per Workload/Env)
│ ├─ Corp (Prod/Non-prod)
│ │ ├─ VNet: snet-web (NSG+ASG), snet-app, snet-db, snet-mgmt, snet-dmz
│ │ └─ NSG per Subnet + ASG for App Tiers
│ ├─ Online / E-commerce
│ ├─ Data & Analytics
│ └─ Dev/Test/Sandbox
└─ Decommissioned / Quarantine
3. Zero Trust / Modern (Identity-centric Zones)
- ไม่ใช่ Network Zone แบบคงที่ (Static) แต่อาจเป็น Dynamic Zones/Trust Levels ตาม Identity + Device Health + Context
- ใช้ Micro-segmentation (Illumio, Guardicore, NSX, Calico/Cilium, Cloud SG/NSG) ระดับ Workload/Pod/Process
- ZTNA (Zero Trust Network Access) แทน VPN: User+Device Verified → Access Specific App Only (No Network Access)
- SASE/SSE: Cloud-delivered Security (SWG, CASB, ZTNA, FWaaS) บน PoP ทั่วโลก
Firewall Security Zones (บน Firewall Appliance)
Firewall Vendors (Palo Alto, FortiGate, Check Point, Cisco FTD, Sophos) ใช้ Zone Concept ในการจัดการ Policy:
- สร้าง Zone:
Untrust, DMZ, Trust, Management, Guest, IoT, Server, Database
- Assign Interface (Physical/Subinterface/VLAN) ให้ Zone
- Policy Rules: Source Zone → Destination Zone → Source IP/User → Destination IP/Port → Application → Action
- Inter-zone Traffic: Default Deny (Implicit) → Explicit Allow Rules เท่านั้น
- Intra-zone Traffic: Default Allow (บน Switch) แต่แนะนำให้ Enable Intra-zone Firewalling (Host Firewall, Micro-seg)
Best Practices สำหรับ Network Security Zoning
- 🎯 Define Zones by Business Function & Risk ไม่ใช่แค่ Technical (VLAN/Subnet) — คิดว่า "Data/Asset นี้ Critical มากน้อยแค่ไหน? ใครต้องเข้าถึง?"
- 🛡 Default Deny / Implicit Deny ระหว่าง Zone ทุกคู่ — Allow เฉพาะที่ Documented & Approved
- 🔥 Firewall ทุกช่วง (Inter-zone Firewalling) — ไม่ใช่แค่ Perimeter ใช้ Internal Firewall / Virtual Firewall / Cloud Firewall / Host Firewall
- 🏷 Naming Convention ชัดเจน:
zone--- (เช่น zone-high-db-prod, zone-low-dmz-prod)
- 📝 Document Flows (Data Flow Diagrams): Source Zone, Dest Zone, Protocol, Port, App, Data Classification, Owner, Review Cycle
- 🔄 Regular Review & Recertification: Rules, Zones, Flows ทุก 6-12 เดือน ลบ Rule/Zone ที่ไม่ใช้
- 🤖 Automate with IaC: Terraform, Ansible, Vendor APIs (Panorama, FortiManager, Azure Policy, AWS Firewall Manager)
- 🔍 Monitor & Alert: Inter-zone Traffic Anomalies, Denied Traffic Spikes, New Flows, Policy Violations
- 🧪 Test Segmentation: Penetration Test (Lateral Movement), Breach and Attack Simulation (BAS), Red Team
เครื่องมือช่วยจัดการ Zones
- Network Visualization/Mapping: NetBrain, Forward Networks, Veriflow (Forward), Cisco Secure Network Analytics, Auvik
- Firewall Policy Management: Tufin, FireMon, AlgoSec, Skybox, Palo Alto Panorama, FortiManager, Check Point SmartConsole
- Micro-segmentation: Illumio, Guardicore (Akamai), VMware NSX, Cisco ACI, Calico Enterprise, Cilium, Azure NSG/ASG, AWS Security Groups
- Cloud Security Posture (CSPM): Wiz, Orca, Lacework, Prisma Cloud, Defender for Cloud, Security Command Center — ตรวจ Security Group/NSG Rules