# Network Segmentation Published articles for Network Segmentation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AWS Security Reference Architecture: A deep dive into PCI DSS compliance DevFeed: [AWS Security Reference Architecture: A deep dive into PCI DSS compliance]() Original publisher: [Read original article]() Author: Avik Mukherjee Published: 2026-09-14T17:46:56Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services](), [Security](), [Architecture & Design](), [Network Segmentation](), [Encryption](), [Logging](), [Access Control](), [Cloud]() Tags: [access-control](), [amazon-web-services](), [announcements](), [architecture](), [compliance](), [encryption](), [foundational-100](), [logging](), [network-segmentation](), [pci-dss](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview AWS announces the AWS Security Reference Architecture (AWS SRA) PCI DSS Deep Dive, a guide that extends the core AWS SRA with prescriptive architecture-level guidance for organizations handling cardholder data on AWS. It explains how AWS SRA patterns address PCI DSS concerns including account scoping, network segmentation, encryption, logging, and access control. ### Source excerpt Amazon Web Services (AWS) is excited to announce the publication of the AWS Security Reference Architecture (AWS SRA) Payment Card Industry (PCI) Data Security Standard (DSS) Deep Dive. This new guide extends the core AWS SRA to provide prescriptive, architecture-level guidance for organizations that store, process, or transmit cardholder data on AWS. Organizations subject to [...] ## The Unexpected Winner of Cisco IT's Wi-Fi 7 Upgrade? Security. DevFeed: [The Unexpected Winner of Cisco IT's Wi-Fi 7 Upgrade? Security.]() Original publisher: [Read original article]() Author: Chris Tomazic Published: 2026-09-11T12:30:05Z Content type: article Language: en Sources: [Cisco Blogs]() Topics: [Security](), [Network](), [Zero Trust]() Tags: [agenticops](), [ai-in-it-operations](), [cisco-it](), [cisco-on-cisco](), [cisco-secure-networking](), [enterprise-networking](), [network](), [network-security](), [network-segmentation](), [security](), [wi-fi-7](), [zero-trust]() ### AI overview Cisco IT's Wi-Fi 7 upgrade delivered expected improvements in connectivity, availability, and performance, but its most significant result was stronger security. The article argues that networking and security should be designed and operated as one system, highlighting zero trust access and Cisco Secure Networking as practical outcomes of that approach. ### Source excerpt Cisco IT's Wi-Fi 7 upgrade delivered more than faster connectivity -- it transformed enterprise security. Discover how Zero Trust Access, AI agents, and secure-by-design infrastructure are redefining what a modern network can do. ## Zero trust architecture for platform engineers: Securing modern developer platforms DevFeed: [Zero trust architecture for platform engineers: Securing modern developer platforms]() Original publisher: [Read original article]() Author: Ajay Chankramath Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Zero Trust](), [Security](), [Architecture & Design](), [Platform Engineering](), [Authentication](), [Authorization](), [Cloud](), [Kubernetes](), [Network Segmentation](), [SPIFFE](), [SPIRE]() Tags: [architecture](), [authentication](), [authorization](), [cloud](), [cloud-native](), [developer](), [identity](), [kubernetes](), [network-segmentation](), [platform](), [platform-engineering](), [policy](), [security](), [spiffe](), [spire](), [zero-trust]() ### AI overview This article explains how zero-trust architecture secures cloud-native developer platforms. It describes continuous authentication and authorization, cryptographic service identity through SPIFFE/SPIRE, network segmentation, policy-as-code enforcement, and runtime verification for Kubernetes-based, multi-tenant environments. ### Source excerpt Secure your cloud-native platform with Zero Trust Architecture. Explore ZTA principles, service identity (SPIFFE/SPIRE), and policy-as-code for automated, developer-friendly security ## Isovalent Networking for Virtualization: Enterprise-Grade Network Segmentation and Multi-Tenancy for VMs in Kubernetes DevFeed: [Isovalent Networking for Virtualization: Enterprise-Grade Network Segmentation and Multi-Tenancy for VMs in Kubernetes]() Original publisher: [Read original article]() Author: Marcos Hernandez Published: 2026-06-02T12:59:28Z Content type: release Language: en Sources: [Isovalent - The latest articles covering eBPF-based Networking, Observability, and Security]() Topics: [virtualization](), [Network Segmentation](), [Multi-tenancy](), [Kubernetes]() Tags: [cilium](), [ebpf](), [hubble](), [isovalent](), [kubernetes](), [kubernetes-networking](), [load-balancer](), [mesh-networking](), [migrations](), [multi-tenancy](), [network-segmentation](), [policy](), [product](), [runtime-security](), [tetragon](), [virtualization](), [website]() ### AI overview Isovalent announced the general availability of Isovalent Networking for Virtualization, a product that provides network segmentation, multi-tenancy, and policy enforcement for virtual machine workloads running in Kubernetes. It also streamlines migrations to KubeVirt. ### Source excerpt We're formally announcing the General Availability of Isovalent Networking for Virtualization (INV), a purpose-built product that brings full network segmentation, multi-tenancy, and policy enforcement to virtual machine workloads running in Kubernetes, in addition to streamlining migrations to KubeVirt. ## PCI DSS Compliance: What Digital Businesses Need to Know DevFeed: [PCI DSS Compliance: What Digital Businesses Need to Know]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Security](), [Social engineering](), [Network Segmentation](), [TLS (Transport Layer Security)](), [vulnerability management](), [SIEM, Security](), [Software as a service](), [tokenization]() Tags: [compliance](), [digital-products](), [firewalls](), [mfa](), [network-segmentation](), [pci-dss](), [saas](), [scope](), [security](), [siem](), [tls](), [tokenization](), [vulnerability-management]() ### AI overview This guide explains how PCI DSS applies to digital businesses that accept card payments, including SaaS companies and sellers of digital products. It outlines the standard's 12 requirements and discusses controls for networks, account data, vulnerabilities, access, monitoring, and information security. It also covers card-not-present transactions, recurring billing, and tokenization. ### Source excerpt PCI DSS compliance explained for digital businesses. Understand the 12 requirements, compliance levels, and how to reduce your scope when selling digital products online. ## Kubernetes for Agentic AI: Best Practices for Security and Observability DevFeed: [Kubernetes for Agentic AI: Best Practices for Security and Observability]() Original publisher: [Read original article]() Author: info@goteleport.com (Boris Kurktchiev, Jack Pitts) Published: 2026-04-01T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Kubernetes](), [Security](), [observability](), [Containers](), [Availability](), [AI Platform]() Tags: [availability](), [container](), [kubernetes](), [kubernetes-security](), [least-privilege](), [monitoring](), [network-segmentation](), [observability](), [permissions](), [recommendations](), [security]() ### AI overview This article presents 18 Kubernetes best practices for securing and monitoring containerized agentic AI workloads. It emphasizes foundational controls such as least privilege, access control, network policies, image assurance, network segmentation, and continuous monitoring, while noting that many practices also apply to other containerized and serverless environments. ### Source excerpt Discover 18 Kubernetes security, observability, and availability best practices for container-based agentic workloads. ## Data Inventory DevFeed: [Data Inventory]() Original publisher: [Read original article]() Author: Ritesh Modi Published: 2025-02-19T14:24:14Z Content type: tutorial Language: en Sources: [Wise Engineering - Medium]() Topics: [data-governance](), [data-architecture](), [Security & Privacy](), [Databases](), [Provisioning](), [Terraform]() Tags: [backend](), [data](), [data-governance](), [databases](), [frontend](), [governance](), [least-privilege](), [network-segmentation](), [platform](), [provisioning](), [security](), [security-privacy](), [terraform]() ### AI overview Wise's Data Governance team describes Data Inventory, a catalog of data assets that records their locations and security or privacy controls. The article explains the system's constraints, design outcomes, and process for discovering operational databases and their metadata. ### Source excerpt The Data Governance team, part of Data Platform, develops and operates platform products through which autonomous teams can govern their data. The team's vision is to democratise data in a secure and compliant manner. Data Inventory was the team's first product. What is Data Inventory? A data inventory is an extensive catalog of the Wise's data assets. It helps us understand where the data is located and what kind of security / privacy controls are in place. This is also a requirement for ISO 27001:2022. What are the constraints? Any system has to work well with our controls and way-of-working. This led to following constraints: It shall be built in a way that satisfies our security controls such as network segmentation, least privilege access, secure secret management, etc. It shall be easy to integrate with other in-house platforms to provide cohesive experience. It shall be built to connect with heterogeneous and fragmented infrastructure. Many data systems are built through off-the-shelf or managed service offering but others are built & operated in-house. The system shall be integrated by default with technology provided by Data Platform. On another hand, it shall be extensible enough to integrate with data systems not maintained by Data Platform. How did we build our inventory? At high level, we split this into 4 main outcomes: 1. Register assets at correct granularity. 2. Identify the correct owner and make them accountable for the life cycle. 3. Extract the schema of the data asset. 4. Classify the asset with correct sensitivity. This is how design looks at high level: To achieve the above design and outcome, we follow the following steps: Step 0: Discover data systems network metadata Scanners need to be aware of the network metadata before doing scanning. For example: - What is the host or connection string? - What is the technology of the data system? - What is the name of the data system? Let us take an example of how we solve it in our operational datab ## Cleared for takeoff: Meeting TSA's new cybersecurity requirements DevFeed: [Cleared for takeoff: Meeting TSA's new cybersecurity requirements]() Original publisher: [Read original article]() Published: 2023-07-10T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Cybersecurity](), [chainguard images](), [Security & Privacy](), [Critical Infrastructure](), [Network Segmentation](), [Access Control](), [Vulnerabilities](), [Monitoring](), [threat detection](), [container images](), [Development]() Tags: [access-control](), [aviation-cybersecurity](), [chainguard](), [chainguard-images](), [compliance](), [container-images](), [critical-infrastructure](), [cve](), [cybersecurity](), [engineering](), [fedramp](), [image-cve](), [monitoring](), [network-segmentation](), [secure-software](), [software-development](), [threat-detection](), [tsa-cybersecurity](), [vulnerabilities](), [vulnerability-management]() ### AI overview The article explains how updated TSA cybersecurity requirements affect aviation organizations, focusing on network segmentation, access control, continuous monitoring, threat detection, and risk-based patch management. It presents Chainguard Images as a source-built, continuously updated suite of minimal hardened container images intended to reduce known vulnerabilities and support compliance efforts. ### Source excerpt TSA strengthens cybersecurity for airports & aircraft. Learn how Chainguard Images helps meet new software development requirements. ## Alternatives to a Corporate VPN DevFeed: [Alternatives to a Corporate VPN]() Original publisher: [Read original article]() Author: info@goteleport.com (Shivashish Yadav) Published: 2022-04-20T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Virtual Private Network](), [network security](), [remote access](), [Vulnerabilities](), [Network Segmentation](), [Zero Trust](), [Firewall]() Tags: [corporate](), [firewalls](), [network-segmentation](), [remote-access](), [security](), [security-vulnerabilities](), [vpn](), [zero-trust]() ### AI overview This article explains why corporate VPNs can create security and access-control risks, particularly for remote work and third-party connections. It discusses data-leak exposure, shared passwords, insufficient resource-level access controls, and the need for network segmentation, firewalls, least-privilege access, or a zero-trust model as alternatives or safeguards. ### Source excerpt VPNs were once the gold standard for network security, but they have limits. This post dives into perimeter-based security limits and offers modern VPN alternatives.