<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>Products &amp; Solutions | Blog</title>
        <link>https://www.zscaler.com/tw/blogs/feeds/product-insights</link>
        <description>Latest news and views from the leading voices in cloud security and secure digital transformation.</description>
        <lastBuildDate>Thu, 19 Nov 2026 07:14:44 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>RSS 2.0, JSON Feed 1.0, and Atom 1.0 generator for Node.js</generator>
        <language>zh-tw</language>
        <item>
            <title><![CDATA[What&#039;s New with ZDX: Feed AIOps Tools, Prioritize VIPs, and Monitor Modern Web Performance]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-zdx-feed-aiops-tools-prioritize-vips-and-monitor-modern-web</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-zdx-feed-aiops-tools-prioritize-vips-and-monitor-modern-web</guid>
            <pubDate>Tue, 17 Nov 2026 22:27:24 GMT</pubDate>
            <description><![CDATA[When C-suite video calls drop, NetOps relies on complex REST calls for data ingestion, and when SaaS CRM performance degrades without clear alerts, IT and Security teams need fast root-cause isolation across distributed environments.Because Zscaler Digital Experience (ZDX) is built natively into the Zscaler Zero Trust Exchange alongside Zscaler Internet Access (ZIA) and Zscaler Private Access (ZPA), organizations using ZDX already possessed comprehensive hop-by-hop visibility from devices, across networks, to applications without deploying siloed monitoring tools. Building on this integrated solution, we extended our capabilities to support emerging enterprise operating models and customer needs to enable bulk data pulls into large-scale AIOps platforms, dedicated executive tiering, and single page application analysis.The&nbsp;October 2026 ZDX release delivers targeted innovations including GraphQL API, ZDX VIP Users, and Real User Monitoring (RUM) for Single Page Applications (SPA). Together, these updates deliver additional operational value across the Zscaler Zero Trust Exchange, empower teams to automate cross-domain workflows, prioritize executive digital experience, and maintain visibility into modern cloud applications. Enterprise Visibility at Scale: ZDX GraphQL API for Bulk TelemetryUnlock High-Throughput Telemetry for Unified Data PlatformsTraditional REST APIs and sequential endpoint polling introduce operational overhead and rate-limiting bottlenecks when extracting fleet-wide data, creating latency across platforms like Snowflake, Databricks, Splunk, and ServiceNow.By eliminating the friction of sequential endpoint queries, high-throughput digital experience telemetry directly feeds predictive incident remediation and cross-functional analytics. The ZDX GraphQL API empowers organizations to overcome REST API limitations, allowing teams to request only the specific fields required in a single query payload, drastically reducing data transfer overhead, accelerating pipeline ingestion, and unlocking immediate business value from central AIOps initiatives.Use Case: Extract Specific ZDX Data at Scale for Reporting and ComplianceConsider an enterprise data engineering team supporting joint Security, ITOps, and NetOps workflows across a global workforce. To maintain a continuous compliance audit trail and satisfy cross-departmental reporting requirements, the team must consolidate a unified stream of user experience, device, network, and application telemetry into their central data lake, Splunk, and Datadog environments.To achieve this, the team schedules automated, daily bulk telemetry extractions via the ZDX GraphQL API. This structured, normalized dataset streams directly into their unified data platform, instantly populating compliance monitoring dashboards in Datadog and enabling deep historical security analysis within Splunk. Furthermore, this clean telemetry acts as a direct, high-quality data feed for internal AI agents, allowing compliance officers and business analysts to query the data lake using natural language and generate customized, audit-ready reports on demand."We’ve used ZDX’s GraphQL to consolidate device, network, and application telemetry into our centralized data lake, simplifying cross-department reporting and empowering our internal AI agents to generate customized, on-demand insights — replacing manual data pulls that used to take days."—&nbsp;Major Healthcare Organization and Leading Technology PlatformHow to Use: Slash Ingestion Overhead and Power Fleet-Scale AIOps AutomationBulk Data Extraction in a Single Query: Extract aggregated telemetry across devices, users, and applications in a single API call, supporting query windows up to 48 hours with a 14-day historical lookback.Optimized Payload Architecture: Select only the required fields to minimize data payload volume, lower processing overhead, and maximize API consumption efficiency across automated pipelines.How to EnableEntitlement SKU: Available for&nbsp;ZDX Advanced Plus customers.Deployment &amp; Endpoints: Accessible via the standalone ZDX endpoint (api.zdxcloud.net/graphql) and through Zscaler OneAPI (api.zsapi.net/zins/graphql).ResourcesZDX GraphQL API | Best Practices Guide: Getting StartedZDX GraphQL API | API &amp; Integration DocumentationZDX GraphQL API | API Rate LimitsZDX | Data Sheet Executive Service Assurance: VIP User Designation and PrioritizationDeliver White-Glove Support: Prioritize Mission-Critical Executive CohortsIn large global enterprises, delivering tailored, white-glove IT support to executive leadership and critical operational teams is an established best practice. When senior leaders or business-critical units encounter digital friction during major events, such as board meetings, investor calls, or quarterly closes, service desks require fast-track visibility to diagnose issues immediately.&nbsp;VIP Users provides heightened visibility into leadership experiences without having to sort through alerts from tens of thousands of other endpoints.Use Case: Protect Critical Executive Access Across Zero TrustDuring a quarterly financial review, a Chief Financial Officer experiences audio-video degradation while reviewing sensitive internal planning portals connected via ZPA.Because the CFO is configured within the ZDX VIP Users cohort, the incident automatically flags in the Service Desk’s dedicated VIP queue. An executive support engineer immediately pulls up ZDX CloudPath and determines that the disruption is caused by localized Wi-Fi channel contention and home router packet drop. Armed with definitive hop-by-hop diagnostics, the technician provides immediate guidance to resolve the local home network issue, all while showing healthy performance through the ZPA Private Service Edge, so IT can rule out the private access path.How to Use: Slash Triage Time and Protect Leadership ProductivityZDX VIP Users introduces dedicated cohort prioritization, enabling support teams to define and segment VIP user groups.Tailored Executive Cohort Management: Define and manage up to 5,000 priority users through automated directory synchronization or targeted list uploads.Accelerated Executive Triage: Easily apply a VIP filter across ZDX Incidents, User Overview, CloudPath, and administrative APIs to instantly isolate high-priority service events.How to EnableEntitlement SKU: Available for&nbsp;ZDX Advanced Plus customers.Deployment: Navigate to&nbsp;ZDX Admin &gt; VIP Management to configure cohorts via CSV upload or automated Identity Provider (IdP) directory group mapping.Prerequisites: Requires administrator roles with&nbsp;VIP Admin or&nbsp;VIP Viewer privileges. Automated directory sync requires an active SCIM/IdP integration (Okta or Microsoft Entra ID).ResourcesZDX VIP Users | Help ArticleZDX VIP Users | Release Note Modern Web Performance Visibility: Real User Monitoring (RUM) for Single-Page Applications (SPA)Align with Modern Web Frameworks: Capture Dynamic In-App User ExperiencesWhen your app team rolls out a new application or your organization adopts a new third-party SaaS platform, poor performance and sluggish in-app interactions can quickly trigger frustrating finger-pointing between your app team, third-party SaaS vendors, Zscaler admins, endpoint teams, and network administrators. Why spend hours on endless bridge calls trying to determine whose fault it is when ZDX Real User Monitoring (RUM) for SPAs gives you end-to-end visibility to instantly isolate root causes across dynamic in-app user interactions?Use Case: Isolate In-App Navigation Latency for Custom Private Applications Secured via ZPAA healthcare organization secures access to its SaaS applications through ZIA and custom internal applications through ZPA, including their Electronic Medical Records (EMR) portal. Medical staff members report that while their EMR launches quickly, clicking into patient charts and updating medical records during patient visits experiences delays that are preventing them from effectively reviewing and updating patient records.With ZDX RUM SPA Tracking active via the lightweight browser extension, network operations teams can inspect real user interaction timings across the custom application and either fix or disprove claims of network disruptions. The telemetry measures in-app route transitions, client-side DOM rendering times, and background API latency. The diagnostic waterfall reveals that the delay stems from an unoptimized third-party client-side analytics script executing in the browser, while ZPA processing times remain under 15 milliseconds.For a Service Desk team using ZDX Agent, they could have quickly identified this root cause via natural language bypassing unnecessary escalation to the Network team. In either case, the granular timing breakdown can be shared with the application development team via&nbsp;Snapshot Views, given the internal App team members aren’t active ZDX users. They can then optimize the script, which can then be validated using RUM.How to Use: Eliminate Browser Blindspots and Unmask Client-Side LatencyDynamic SPA Route Tracking: Capture soft navigations, route changes, and real-time user interactions across modern React, Angular, and Vue applications.Granular In-Browser Waterfall Analysis: Measure client-side component render times, asynchronous API calls, and third-party script execution directly from user sessions.How to EnableEntitlement SKU: Available for&nbsp;ZDX Advanced Plus customers.Deployment: Enable RUM SPA tracking in application monitoring settings under&nbsp;ZDX Configuration &gt; Applications.Prerequisites: Configured application monitoring definitions and the&nbsp;ZDX browser extension deployed to endpoints.ResourcesZDX RUM SPA | Release Note Scale and Focus Your Digital Experience StrategyThe October 2026 ZDX release reinforces the power of native digital experience monitoring across the Zscaler Zero Trust Exchange. By combining fleet-wide data extraction, dedicated executive prioritization, and granular frontend application tracking, IT, Security, and Service Desk teams can simultaneously scale their data operations and focus their operational resources.Whether you are consolidating data architectures into an enterprise datalake, refining white-glove executive support models, or optimizing mission-critical SaaS workflows, these capabilities empower you to isolate root causes faster and deliver consistent, high-performing digital experiences across your entire organization.Ready to Get Started?All features highlighted in this release are available for ZDX Advanced Plus customers. Don’t have ZDX or ZDX Advanced Plus?&nbsp;Schedule a personalized ZDX demo or explore more at&nbsp;zscaler.com/zdx.]]></description>
            <dc:creator>John Jones (Sr.Marketing Manager–Digital Experience Monitoring)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Go Dark or Go Unprotected? Why Your Workloads Need a Better Business Continuity Plan]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/go-dark-or-go-unprotected-why-your-workloads-need-better-business-continuity</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/go-dark-or-go-unprotected-why-your-workloads-need-better-business-continuity</guid>
            <pubDate>Mon, 16 Nov 2026 20:28:00 GMT</pubDate>
            <description><![CDATA[A global bank processing transactions, a large healthcare provider syncing patient systems, or a manufacturer running real-time plant operations can't tolerate unplanned downtime or unsecured fallback traffic. For these production workloads — secured by a cloud-native zero trust architecture — an outage isn't just an inconvenience. It can mean lost or unsecured connectivity for systems that were never designed to tolerate downtime.&nbsp;The Zscaler Zero Trust Exchange™ is the world’s largest security cloud, protecting 750+ billion transactions daily. With a globally distributed network of more than 200 public data centers across 185 countries, it seamlessly absorbs component, network, and regional failures to deliver secure, low-latency access to companies worldwide. Yet, no system is immune to unforeseen events — which is why you need a business continuity&nbsp;plan to keep workloads connected and secure through catastrophic failures.&nbsp; 3 Pillars of an Efficient Disaster RecoveryAn efficient disaster recovery plan should ensure the following:Stay connected: When the Zscaler Public Service Edge can’t be reached, workload traffic moves to the private service edge - a predefined backup cloud (Zscaler managed Business Continuity Cloud or customer managed data center).Stay inspected: The workload traffic is still inspected by Zscaler private service edge based on the policies defined in the Public Service Edge.&nbsp;Come back on its own: When the Zscaler Public Service Edge is healthy, workload traffic moves back from the private service edge automatically.&nbsp;&nbsp;&nbsp; Introducing Business Continuity Cloud for Workload CommunicationsBusiness Continuity Cloud — Zscaler's existing business continuity and disaster-recovery capability for users — is now available for workloads. It adds a private data plane and control plane that protects workloads traffic with uninterrupted security, even when the public cloud is unavailable or unreachable. Here's how it works.&nbsp; Managing the Data Plane Outage: Automated Failover&nbsp;Typically, when a workload tries to connect to the internet or a SaaS destination, traffic is sent to the Cloud Connector, which forwards it to the Zscaler Zero Trust Exchange (ZTE). Customers inspect this traffic and enforce advanced threat and data protection using Zscaler Internet Access (ZIA). If the Zscaler Public Service Edge goes down, egress traffic is either blocked entirely (fail-close) or allowed through without inspection (fail-open).With Business Continuity Cloud support for workloads, traffic instead fails over automatically to a dedicated, geographically separate standby cloud instance that enforces the same policies defined in the Zscaler Public Service Edge. Customers can use the Zscaler-managed Business Continuity Cloud (BCC) or deploy a Zscaler Virtual/Private Service Edge in their own data centers to handle the inspection.Figure: Traffic going through Zscaler managed BCC during data plane failureFigure: Traffic going through customer managed Data Center during data plane failure&nbsp; Managing the Control Plane Outage: DNS triggered failoverWhat do you do when the Zscaler admin portal itself is unreachable? You can't make changes, flip a switch, or respond — right when you need to most. For these situations, customers can pre-configure a DNS TXT record that Cloud Connector polls periodically, giving them an external "switch" to trigger failover.This also makes fire drills practical, not just emergencies — customers can validate failover on a defined subset of traffic on a regular cadence, without redirecting all production traffic, so continuity plans are proven before they're ever needed.Figure: DNS triggered business continuity during control plane failure&nbsp; BenefitsTogether, automated failover and DNS-triggered failover give workloads the same resilience that's long protected user traffic — without asking customers to choose between staying online and staying secure. Here's what that translates to in practice.Production continuity independent of security-layer availabilityUntil now, the health of your production workloads was tied to the health of a single cloud control point — if the Zscaler Public Service Edge went down, so did your options. With business continuity built in, that dependency breaks. Workload traffic keeps flowing to its internet and SaaS destinations through the Zscaler Business Continuity Cloud (BCC) or customer managed Data Center with Zscaler virtual/private service edge, fully inspected, regardless of what's happening upstream. Production uptime is no longer hostage to the availability of any one component in the chain.No forced trade-off between staying secure and staying onlineFail-open and fail-close have always asked customers to choose one: let traffic through unprotected, or cut it off entirely. Neither is a real continuity plan — just damage control. Automated failover to the Business Continuity Cloud or a customer-managed private service edge removes that choice altogether. The same policies enforced at the Zscaler Public Service Edge carry over to the backup path, so traffic stays both online and inspected, even during an outage.Low operational overheadResilience shouldn't require a second team to run it. Failover to the private service edge is automatic — no manual cutover, no scripts to trigger in the middle of an incident. Provisioning happens through existing licensing rather than a separate deployment project, and configuration lives in one place rather than being repeated across every gateway. Testing is self-service too: customers can run fire drills on a defined slice of traffic whenever they want proof the failover path works, without waiting on Zscaler or disrupting production to find out.Fits enterprises with strict uptime and compliance requirementsFor regulated industries and large enterprises, disaster recovery isn't optional — it's something auditors and boards expect documented and tested for every critical vendor in the stack. Business continuity for workloads gives these organizations exactly that: a defined failover path, a way to validate it on a schedule, and a control mechanism that works even if the admin portal itself is unreachable. It's DR that can actually be demonstrated, not just assumed.&nbsp; ConclusionOutages are no longer a question of if, but when — and for critical production workloads, "when" needs an answer that doesn't force a choice between staying online and staying secure. By extending Business Continuity Cloud from users to workloads, Zscaler closes that gap on both fronts: automated failover keeps traffic inspected and flowing when Zscaler Public Service Edge is unreachable, and DNS-triggered failover gives customers a way to act even when the admin portal itself is down. This isn't just a fallback — it's a business continuity plan enterprises can actually validate before they ever need to rely on it. Zero Trust and business continuity were never meant to be separate conversations, and now, for workloads, they aren't.&nbsp;&nbsp;To learn more about how Zscaler secures your workloads,&nbsp;click here.&nbsp;]]></description>
            <dc:creator>Salim Zia (Senior Product Marketing Manager)</dc:creator>
        </item>
        <item>
            <title><![CDATA[From App Access to Infrastructure Control: Extending Zero Trust to Privileged Systems]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/app-access-infrastructure-control-extending-zero-trust-privileged-systems</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/app-access-infrastructure-control-extending-zero-trust-privileged-systems</guid>
            <pubDate>Mon, 16 Nov 2026 18:55:43 GMT</pubDate>
            <description><![CDATA[Modern organizations have largely mastered private application access. By replacing legacy VPNs with Zscaler Private Access (ZPA), IT and security teams have proven the value of Zero Trust: identity-based access, zero network exposure, device posture enforcement, and direct-to-app connectivity for managed users.Securing routine application access is only one side of the coin. Operating core infrastructure, the production servers, databases, network devices, and OT/ICS environments that keep the business running, introduces an entirely different level of risk and operational complexity.When system administrators, outsourced MSPs, and third-party vendors need to patch a database or service an OT controller, standard access policies aren't enough. These sessions demand strict operational governance: time-bound approvals, credential shielding, granular session controls, and complete audit visibility.Historically, solving this meant bolting on legacy Secure Remote Access (SRA) tools, a patchwork of bastion hosts, jump servers, static shared credentials, and complex firewall rules that manage complexity rather than eliminate it.That is why we built Zscaler Privileged Remote Access (PRA): an add-on capability delivered natively on your existing Zscaler platform that extends zero trust from application access to full privileged session governance. Two Sides of the Same Zero Trust Coin: ZPA + PRAWithin the Zscaler Zero Trust Exchange, ZPA and PRA work together to deliver a unified, clientless access architecture tailored to different user roles and workloads:Zscaler Private Access (ZPA):&nbsp;Brokers identity-based connectivity to private business applications for employees and managed devices. Users reach specific apps without ever being placed on the network, eliminating the attack surface and stopping lateral movement.Zscaler Privileged Remote Access (PRA):&nbsp;Delivers governed, monitored, and recorded access for administrators, contractors, and third-party vendors operating critical systems over protocols like SSH, RDP, and VNC.By layering PRA onto your existing Zscaler architecture, you bridge the gap between connecting users to applications and governing who operates your production infrastructure, all with zero new servers to build or manage.&nbsp; The Privileged Challenge in Critical InfrastructureOperating sensitive systems with legacy remote access tools introduces three critical operational challenges that routine access tools were never designed to solve:Uncontrolled Standing Access: Admins, vendors, and MSPs frequently retain persistent, standing privileges across production servers and OT environments instead of strictly time-boxed authorization.Exposed Administrative Credentials: Shared domain credentials, root passwords, and private SSH keys are handed directly to internal and external users, creating severe vulnerability if an endpoint is compromised.No Proof of What Happened:&nbsp;Without tamper-proof session recording or centralized audit trails, teams cannot prove compliance or reconstruct administrative actions during incident response.Legacy SRA attempts to address this with agent-heavy software, dedicated bastion servers, and complex routing rules. This leaves organizations with exposed infrastructure, inbound listening ports, slow deployment cycles, and heavy operational maintenance. What Zscaler PRA EliminatesDelivered 100% from the cloud, Zscaler PRA eliminates the traditional infrastructure required to govern privileged sessions:Eliminates Third-Party VPNs:&nbsp;Vendors can service critical production systems via a secure browser portal for a time-boxed window, and touch nothing else.Eliminates Jump Servers &amp; Bastion Hosts: IT admins can patch production servers directly from the cloud with full session recording, and touch nothing else.Eliminates Shared Admin Passwords: Network engineers access core devices with automatic credential injection and read-only rights, and touch nothing else.Eliminates Standing Privileges: Contractors connect to core infrastructure only after explicit Just-In-Time (JIT) approval, with access that auto-expires. The 5-Step Privileged Session LifecycleRather than bolting on disjointed point products, Zscaler PRA operationalizes privileged access as a seamless, 5-stage lifecycle brokered directly through the Zero Trust Exchange:1. User Identity-Based AccessPrivileged workflows begin with strict, contextual identity verification. Whether the user is an internal employee, an external partner, or a third-party vendor connecting from an unmanaged machine, access is requested and authenticated through the PRA Console. Users never touch the underlying corporate network, access is scoped strictly to authorized tasks.2. Just-In-Time (JIT) Access &amp; ApprovalsStanding privileges represent an open invitation for lateral movement. PRA replaces permanent admin rights with dynamic, Just-In-Time authorization. Designated administrators review and grant time-bound access on demand. Once the designated maintenance or operational window closes, access automatically expires, eliminating dormant access paths entirely.3. Reduced Credential Exposure (Cloud Vault &amp; Injection)Privileged credentials should never be visible to the operator. When a session is initiated in the cloud, PRA retrieves domain credentials, private SSH keys, or administrative passwords securely from a central Credential Vault. Through automated credential injection, credentials are submitted directly into the target session (SSH, RDP, VNC) without the user ever seeing, copying, or storing them.4. Real-Time Session GovernanceWhile the session is active, comprehensive governance controls run inline to protect target infrastructure and corporate data:Clipboard Controls: Restrict copy/paste actions to prevent unauthorized data transfer.Sandboxed File Transfer with Anti-Virus Scanning: Inspect and neutralize incoming files before they ever hit the production system.Inline DLP: Block sensitive proprietary or regulated data from leaving the session.Session Proctoring &amp; Sharing: Enable real-time dual-custody collaboration, live session monitoring, or immediate termination if anomalous behavior occurs.5. Post-Session Analysis &amp; AI Risk ScoringGovernance doesn't end when the session closes. Every single keystroke, command, and interaction is captured via tamper-proof session recording. PRA then applies AI-powered risk scoring (e.g., flagging elevated risk sessions like 82/100 High Risk) to automatically prioritize review for compliance teams, security audits, and rapid incident response. Proven Results: Eaton Modernizes Privileged AccessGlobal power management company Eaton, operating across 216 manufacturing facilities with 94,000 employees, turned to Zscaler PRA to secure privileged vendor and administrative access across its global footprint.By deploying PRA on top of their cloud-native security foundation, Eaton achieved:$500K+ saved in vendor travel costs in the first year alone by enabling secure remote servicing450 secure remote privileged sessions completed across critical environmentsDay 1 secure access&nbsp;operationalized immediately across newly acquired facilities without infrastructure rollout delays Elevate Your Zero Trust ArchitectureYou have already secured application access and eliminated broad network exposure with Zero Trust. Now, extend that same architecture to protect the systems that run your business.Zscaler Privileged Remote Access gives your teams total governance over administrators, vendors, and MSPs, delivering ephemeral credentials, agentless access, in-session DLP, and full recording with zero hardware to deploy.See how PRA extends your zero trust foundation:&nbsp;Request a demo.]]></description>
            <dc:creator>Olivia Vort (Senior Product Marketing Manager, Zero Trust Browser)</dc:creator>
        </item>
        <item>
            <title><![CDATA[When Cloud Services Fail, Security Is Still On The Clock]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/when-cloud-services-fail-security-still-clock</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/when-cloud-services-fail-security-still-clock</guid>
            <pubDate>Mon, 16 Nov 2026 15:15:13 GMT</pubDate>
            <description><![CDATA[IntroductionRecent cloud service disruptions are a reminder that resilience is a critical part of security.&nbsp;When organizations lose access to cloud services like email, collaboration apps, calendaring, and cloud productivity services, the impact is immediate and visible. Business slows down, teams lose coordination, and critical decision-making gets harder. Security teams also depend on these services to share alerts and coordinate decisions during an investigation. Incidents do not pause just because the tools used to manage them are unavailable. Situation OverviewThe Microsoft 365 outage disrupted Outlook and Exchange Online, with additional impacts to Teams, SharePoint, and OneDrive. Microsoft attributed the incident to a technical issue involving a network change during a capacity upgrade and said there was no evidence of malicious activity.&nbsp;Security workflows were also affected. Microsoft&nbsp;reported disruptions to Defender for Office 365, access to Defender portal pages, and multiple Purview services. Affected capabilities included authorization, data loss prevention (DLP), information protection, role-based access control (RBAC), and data classification. How Cloud Outages Disrupt Security OperationsWhen email goes down, most incident response teams lose their primary coordination channel. When chat follows, analysts have no reliable escalation path. These are communications problems, and they slow response. But there is a second, less visible problem: when security consoles or management planes share the same cloud dependency, defenders can also lose the ability to monitor risk, push policy, or approve containment actions. One problem slows you down. The other can weaken your defensive posture directly. In a major outage, organizations may face both at once. Both problems require separate planning.&nbsp;Modern enterprises have built efficiency around a small set of integrated cloud services. That creates convenience and speed in normal conditions, but it can also create concentrated risk during an outage. A single provider disruption can affect not just employee productivity, but the communications backbone that security teams rely on to investigate alerts, coordinate response, notify executives, and manage customer impact.&nbsp;Disruptions can also originate within the enterprise through a cyberattack. Ransomware and other destructive attacks have shown that a single compromise can cascade across an entire enterprise when the network allows unrestricted lateral movement. Organizations that rely on flat networks or legacy perimeter-based architectures face the possibility that one compromised endpoint or privileged account can turn an isolated breach into a widespread business disruption. Resilience planning must account for both service outages and cyberattacks that can disrupt critical operations, including the tools security teams need to respond. Planning For Security ContinuityThat is why incident response planning cannot assume primary tools will always be available. Organizations need documented business continuity and disaster recovery plans that are tested regularly for immediate activation when required. That includes predefined backup channels, alternate contact methods, offline access to key escalation trees, and clear rules for when teams should move from primary to contingency workflows.This is also why security resilience cannot be treated as a narrow infrastructure or disaster recovery exercise. Business continuity plans need to account for how security teams will operate during degraded conditions, and security plans need to assume the loss of normal business tooling. If defenders cannot communicate, cannot reach key telemetry, or cannot execute urgent response steps, organizational risk rises immediately, even if the original incident was operational rather than adversarial.Security programs are often measured by how well they prevent, detect, and respond to threats. They should also be measured by how well they continue to operate when the environment around them becomes unstable. RecommendationsBusiness continuity plans must account for how security teams will operate under these conditions. Ultimately, resilience is not separate from security. It is a core part of it.Key actions leaders should consider:Document a business continuity and disaster recovery plan:&nbsp;Define a business continuity and disaster recovery plan including communication channels for incident coordination, executive updates, and crisis response if primary email or messaging platforms fail. Establish clear rules for when teams should move from primary to contingency workflows.Establish an architecturally independent business continuity capability for mission-critical security services (DR Cloud):&nbsp;High-availability SLAs are not a substitute for a dedicated disaster recovery environment. An architecturally independent business continuity cloud, fully isolated from your primary security infrastructure, should maintain security policies, inspection, and access controls during a large-scale outage. This should include automated failover so the transition happens without manual intervention or gaps in protection.Define decision ownership as part of the plan: Pre-assign roles for response leadership, internal communications, customer communications, and escalation management during major service disruptions. Specify who declares the fallback mode, manages executive updates, coordinates with IT and infrastructure teams, and how customer-facing communications will be approved and delivered.Make critical response information available offline: Ensure contact lists, escalation paths, playbooks, and core procedures can be accessed without dependence on cloud productivity tools.Test degraded-mode operations: Run tabletop exercises that assume loss of email, chat, and shared collaboration platforms, as well as temporary loss of access to core security consoles or management workflows. Test how teams reach key telemetry, push policy, or approve containment actions under these conditions. Also, test failover and recovery to verify that critical applications remain accessible and security controls continue to operate.&nbsp;Adopt a Zero Trust architecture to eliminate lateral movement: When a cyberattack succeeds, its ability to spread can compound the damage. Organizations that connect users to the network give attackers a path to move laterally from a single compromised endpoint to critical systems across the enterprise. Implement a Zero Trust architecture that connects users directly to authorized applications, without placing them on the network, to help contain the blast radius and reduce the risk of wider business disruption.Review concentration risk across providers: Identify where security operations rely too heavily on a single platform for communications, visibility, or administrative control. Account for shared cloud dependencies that could disrupt these functions at the same time. How Zscaler Builds Resilience Into SecurityZscaler built the Zero Trust Exchange with this kind of resilience in mind. The platform's architecture decouples control, data, and logging planes to help prevent a disruption in one from cascading to the others.&nbsp;Because the Zero Trust Exchange connects users directly to authorized applications and never to the network, it eliminates the lateral movement paths that allow ransomware and other attacks to spread across an enterprise. This helps contain the blast radius of a compromise and reduce the risk of enterprise-wide disruption .To maintain security during service outages,&nbsp;Zscaler Business Continuity Cloud provides a dedicated, architecturally independent cloud that is fully isolated from the primary Zero Trust Exchange. It is not a degraded fallback. During failover, it maintains the same zero trust policies, the same inspection engines, and the same threat prevention, with logs still streaming. For end users, the transition is automatic: no manual intervention or no re-authentication. For security teams, defensive posture is preserved through the disruption.This is the same principle that enterprises relied on in the data center era, when a separate disaster recovery site supported continued operations if the primary facility went down. In the cloud era, high-availability SLAs alone are not enough. An architecturally independent business continuity cloud remains essential to keeping security operational when primary services fail.To learn more about how this works in practice, see our&nbsp;blog or join one of our upcoming&nbsp;webinars.&nbsp;]]></description>
            <dc:creator>Deepen Desai (EVP, Chief Security Officer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Future-Proofing Enterprise Traffic: How to Govern and Inspect Post-Quantum Traffic Without Hardware Refreshes]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/future-proofing-enterprise-traffic-how-govern-and-inspect-post-quantum</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/future-proofing-enterprise-traffic-how-govern-and-inspect-post-quantum</guid>
            <pubDate>Thu, 12 Nov 2026 19:35:45 GMT</pubDate>
            <description><![CDATA[This is Part 1 of our three-part architectural series,&nbsp;Future-Proofing Enterprise Traffic, exploring how Zscaler Internet Access (ZIA) and the Zero Trust Exchange solve the three structural shifts breaking legacy network security: Post-Quantum Cryptography (PQC), Inline Cyber Threat Protection for Agentic AI, and SOC Provenance with Endpoint Context.Every inline security architecture relies on a simple contract: if an attack has to cross the network, your security stack should be able to terminate the connection, inspect the bytes, understand the context, and render a verdict before any damage is done.For fifteen years, legacy network security vendors tried to honor that contract by bolting features onto castle-and-moat firewalls or by lifting those same virtual firewall instances into the cloud and calling them SASE. As long as enterprise traffic mostly consisted of classical TLS 1.2/1.3 over TCP and compiled&nbsp;.exe binaries, that approach limped along.Over the last nine months, the wire moved faster than legacy appliances could follow. Looking across the&nbsp;500+ trillion daily signals and&nbsp;9+ billion daily blocked threats traversing the Zscaler Zero Trust Exchange, three structural shifts have broken the assumptions behind traditional network and endpoint security:Post-Quantum Cryptography (PQC)&nbsp;changed the physical geometry of TLS handshakes: With modern browsers, operating systems, and major content providers enabling hybrid post-quantum key exchange by default and the IETF finalizing RFC 10024 in August 2026, TLS 1.3&nbsp;ClientHello messages now routinely span multiple TCP segments—overwhelming fixed-hardware firewalls and legacy proxies.Inline Cyber Threat Protection now has to parse AI agents and persistent streaming protocols: Sanctioned AI tools hold open bidirectional WebSockets, browsers default to HTTP/3 over QUIC, attackers tunnel command-and-control (C2) inside gRPC, and autonomous AI agents execute instructions out of plain-text Markdown skill files (.md) and Model Context Protocol (MCP) servers.The SOC is&nbsp;starving for provenance, not just more alerts: When an attacker uses a living-off-the-land binary (LOLBin), a ClickFix PowerShell stager, or an offline USB drop, a network proxy that only sees packets can’t tell which process opened the connection — and an EDR that only sees the host can’t surgically enforce inline network policy across the global enterprise.To stop a modern breach, an inline architecture has to win at three consecutive choke points: terminating post-quantum TLS handshakes without failing open, decoding agentic AI and persistent streaming protocols inline, and correlating every network socket to the exact process and DLL executing on the endpoint. We recently shared a high-level summary of our&nbsp;Zenith Live 2026 innovations; across this three-part series, we are going under the hood of Zscaler Internet Access (ZIA) to walk through the architecture across each pillar. In Part 1, we examine the first choke point:&nbsp;Post-Quantum Cryptography (PQC).From Lattice Math to Production Plumbing: Why PQC Is Today’s Network CrisisIf you have followed the recent standardization work across the IETF, specifically within the&nbsp;TLS,&nbsp;LAMPS (Limited Additional Mechanisms for PKIX and SMIME), and&nbsp;PLANTS (PKI, Logs, And Tree Signatures) working groups, you have noticed an unmistakable shift in tone among cryptographers and systems engineers. Two years ago, PQC discussions were theoretical primers on lattice math. Today, the focus is squarely on production plumbing: standardizing hybrid post-quantum key exchange for TLS 1.3, updating X.509 certificates and PKI hierarchies for ML-DSA (FIPS 204) in LAMPS, advancing Merkle Tree Certificates in PLANTS to keep post-quantum certificate chains from bloating, and solving how larger post-quantum handshakes behave across real-world enterprise networks.Why does IETF protocol plumbing matter to a CISO or security architect? Because major web browsers (Chrome, Edge, Firefox), modern operating systems, and leading cloud and content providers have already enabled hybrid post-quantum key establishment (such as&nbsp;X25519MLKEM768) by default in TLS 1.3. That means client endpoints, cloud workloads, and major web origins are already negotiating TLS handshakes with post-quantum key exchange on your network today — without enterprise application teams changing a single line of code.Combine the IETF’s publication of&nbsp;RFC 10024 (Post-Quantum Traditional Hybrid Key Agreement Mechanisms for TLS 1.3) with compressed federal compliance timelines, and&nbsp;PQC is no longer a 2030 roadmap item.&nbsp;The Byte Math That Breaks Legacy Firewalls and Virtual SASELook at the byte math of a TLS 1.3 handshake to see why this creates an immediate crisis for legacy firewall appliances and virtual-machine SASE gateways:Classical Elliptic-Curve Exchange: In a classical&nbsp;X25519 exchange, both the client and server key shares are just&nbsp;32 bytes each.Hybrid Post-Quantum Exchange: In a hybrid&nbsp;X25519MLKEM768 exchange, the key shares are much larger and asymmetric: the client sends a&nbsp;1,216-byte key share in the&nbsp;ClientHello, while the server responds with a&nbsp;1,120-byte key share in the&nbsp;ServerHello—a&nbsp;38 increase in client key share size.Ethernet MTU Fragmentation: Once you include cipher suites, extensions, and SNI, the TLS&nbsp;ClientHello routinely exceeds the&nbsp;1,500-byte Ethernet MTU, forcing the message to split across multiple TCP segments before the handshake even completes.When a hardware firewall or virtualized appliance with fixed inspection buffers encounters a multi-packet&nbsp;ClientHello proposing hybrid post-quantum key exchange, it hits an architectural wall. If the appliance cannot reassemble and parse the multi-segment&nbsp;ClientHello, it must either&nbsp;fail closed (dropping the connection and breaking access to modern cloud apps) or&nbsp;fail open (passing the session through completely uninspected). Even if a legacy proxy manages to terminate the TLS session without supporting PQC key exchange groups, it forces the connection to negotiate a classical key exchange group (often incurring an extra&nbsp;HelloRetryRequest round-trip) — depriving the inspected session of post-quantum protection.Passing encrypted traffic uninspected in 2026 is catastrophic for enterprise security. In&nbsp;our latest research, overall phishing volume dropped 20% as attackers shifted from noisy mass spam to targeted precision, yet&nbsp;95.2% of phishing attempts and&nbsp;87% of all blocked malicious activity rode over encrypted TLS channels, driven by&nbsp;413,524 AI-generated site instances.At the same time,&nbsp;1 in 3 organizations inspect 0% of their encrypted traffic and&nbsp;70% have limited or no visibility into AI threats traversing their tunnels according to the&nbsp;ThreatLabz 2026 VPN Risk Report. If your gateway cannot terminate hybrid PQC handshakes at scale, you face an unfortunate choice: either every modern browser and workload upgrade quietly shrinks your inspection coverage, or you are exposing your data to Harvest Now, Decrypt Later (HNDL) risks posed by future quantum computers.How the Zscaler Zero Trust Exchange Solves ItBecause ZIA is a cloud-native, multi-tenant proxy distributed across 160+ points of presence—not a fixed-ASIC box in a wiring closet—we engineered&nbsp;PQC readiness directly into our elastic TLS state machine with zero CAPEX or hardware refreshes required:Cryptographic Discovery &amp; Inventory in Web Insights: You cannot manage a cryptographic migration—or pass a compliance audit—blind. ZIA populates&nbsp;six dedicated PQC logging fields in Web Insights on every transaction (streamable in real time to your SIEM via Nanolog Streaming Service) and visualizes them in the&nbsp;Post Quantum Cryptography Visibility interactive report. Security teams get a live, probe-free inventory of Classical vs. PQC transaction volume, client-proposed key exchange algorithms, negotiated client and server key exchange mechanisms, and signature schemes.Wire-Speed Hybrid ML-KEM TLS Inspection &amp; Per-Leg Negotiation: ZIA natively reassembles multi-packet ClientHello messages in memory and terminates, inspects, and re-encrypts TLS 1.3 sessions using the standardized RFC 10024 hybrid ML-KEM key exchange groups (X25519MLKEM768, SecP256r1MLKEM768, and SecP384r1MLKEM1024). Crucially, ZIA negotiates key exchange independently on the client-to-proxy and proxy-to-origin legs—delivering seamless cryptographic translation across every permutation (PQC client to PQC server, classical client to PQC server, and PQC client to classical server) so a legacy destination never strips quantum protection from the client leg, and you retain 100% full-payload inspection across malware, DLP, and IPS engines.&nbsp;Pioneering Single-Packet PQC Standards: While the Zero Trust Exchange natively handles multi-packet handshakes, many enterprises still have third-party path devices that fail closed whenever a ClientHello spans multiple TCP segments. To solve this across the broader internet ecosystem,&nbsp;Zscaler authored and registered two compact hybrid PQC TLS groups at the IANA registry—SecP256r1MLKEM512 and MLKEM512X25519, targeted for upcoming support in OpenSSL 4.2—that deliver quantum safety while keeping the ClientHello within a single MTU packet.&nbsp;Custom Crypto Profiles for Compliance &amp; Digital Sovereignty: ZIA’s Custom Crypto Profiles let administrators actively govern and enforce allowed post-quantum and hybrid key exchange mechanisms separately across source and destination traffic. This enables multinational organizations to satisfy strict federal timelines (such as CNSA 2.0 and OMB M-23-02) while simultaneously tuning regional policies for digital sovereignty mandates (such as Germany’s BSI, France’s ANSSI, or South Korea’s KpqC) when national requirements diverge from NIST guidance.&nbsp;Cryptographic Trust Governance (BYO Trust Store &amp; Cloud HSM): Quantum readiness requires governing certificate trust and private keys alongside key exchange. With Bring Your Own (BYO) Trust Store and Zscaler-managed Cloud HSM, administrators can maintain sovereign control over inspection keys, immediately revoke trust in compromised or untrusted root and intermediate Certificate Authorities (such as rapid mitigation against CA compromises like&nbsp;eMudhra), and prepare their PKI posture for post-quantum digital signatures (ML-DSA / FIPS 204) and Merkle Tree Certificates (MTC).&nbsp;Quantum-Resistant IPsec Traffic Forwarding (IKEv2 PPK): Securing the inner TLS session doesn't help if an adversary harvests the outer branch tunnel. To protect branch-to-cloud traffic forwarding against "Harvest Now, Decrypt Later" collection, ZIA supports IPsec with Post-Quantum Pre-Shared Keys (IKEv2 PPK, RFC 8784)—mixing a high-entropy post-quantum secret directly into the IKEv2 key derivation to quantum-harden the transport layer itself on commodity IPsec appliances without bloating handshake packets.&nbsp;What’s Next in the SeriesTerminating the post-quantum TLS handshake is only the first choke point. Once the session is decrypted, what happens when the payload inside isn’t a standard HTTP request or a compiled&nbsp;.exe binary — but an autonomous AI agent executing instructions from a plain-text&nbsp;.md file, or an attacker tunneling C2 over QUIC and gRPC?In&nbsp;Part 2, we dive into&nbsp;Inline Cyber Threat Protection for Agentic AI, persistent streaming protocols, and 200 MB patient-zero loaders. Want to benchmark your PQC inspection posture today? Reach out to your Zscaler account team to run a&nbsp;Cyber Threat Protection Posture Assessment.]]></description>
            <dc:creator>Satish Madiraju (Sr. Director, Product Management)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Deception Is a Zero Trust Sensor, Not a Science Project]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/deception-zero-trust-sensor-not-science-project</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/deception-zero-trust-sensor-not-science-project</guid>
            <pubDate>Thu, 12 Nov 2026 07:52:55 GMT</pubDate>
            <description><![CDATA[How DoW defenders can turn adversary movement into high-confidence detection with Zscaler DeceptionThe most useful network deception does not try to make an environment look clever. It makes an intruder reveal intent. That distinction matters for Department of War (DoW) organizations operating hybrid enterprise, mission, tactical edge, and partner connected networks. Alerts are plentiful; high-confidence evidence that an actor is enumerating, harvesting credentials, or moving laterally is not. A well-designed deception program improves that signal-to-noise ratio by placing believable but non-production assets, credentials, and paths where an adversary would naturally look but where a legitimate user should have no reason to operate. The policy alignment: assume breach, then make movement visibleCISA's Zero Trust Maturity Model describes a target environment in which security decisions draw on identity, device, network, application workload, and data signals, with continuous monitoring and centralized visibility across them. The&nbsp;DoD Zero Trust Strategy likewise drives toward an enterprise that can limit implicit trust and monitor activity across its architecture. Neither document should be read as a product prescription or as a blanket authorization to deploy decoys. Together, however, they support a practical operating principle: defenders must be able to detect and respond when an actor attempts to use access in an unintended way.CISA’s September 2026 publication,&nbsp;Using Cyber Decoys to Strengthen Detection and Response,&nbsp;provides complementary guidance for using cyber decoys to improve detection and response. It reinforces the operational discipline described in this blog post: make decoys believable but isolated, integrate the resulting signals into response workflows, and use the evidence to improve defensive decisions, not merely to generate alerts. The guide also uses the MITRE Engage and ATT&amp;CK frameworks to plan decoy operations, which gives DoW teams a common planning language.Deception is powerful in that model because a correctly placed decoy has an unusually clean analytic property. Interaction with it is rarely normal business activity. An attempted use of a decoy share, honey credential, fake service account, or decoy endpoint can be correlated with identity, endpoint, network, DNS, and security operations data to answer four urgent questions:Who touched it?From what device and network path?What did they try to do next?What containment action is appropriate now?That is the bridge from alerting to adversary engagement: force the attacker to choose between stopping and exposing their tradecraft. Where Zscaler Deception fitsZscaler Deception is designed to distribute realistic decoys and lures across endpoints and networks, detect interaction with them, and provide investigation context for the security team. The important conversation is not “where can we put a fake server?” It is “which attacker path do we need to make observable?”&nbsp; Delivered as part of the FedRAMP Authorized Zscaler Zero Trust Exchange, it is built to detect compromised users, expose lateral movement, and disrupt human-operated ransomware.For a DoW environment, that starts with mission-informed hypotheses. A few examples of this are: a compromised workstation enumerates shares, privileged accounts, management protocols, or remote administration paths; stolen credentials are tested against access paths that should never be used by the assigned user or device; an actor pivots toward an identity, data repository, enclave boundary, operational technology segment, or mission application; a partner-connected or tactical workflow creates an unexpected route to sensitive services.The decoy and the response playbook should be designed around the hypothesis, not around a generic catalog of traps. A decoy that resembles a real administrator jump path but is isolated from production can expose credential misuse. A lure placed near a data access workflow can expose discovery or staging behavior. A decoy service in a segmented enclave can reveal lateral movement without granting access to a real mission system. Design for the operator, not the demoThe fastest way to discredit deception is to create noise or operational ambiguity. The first deployment should therefore be narrow, measurable, and integrated with the people who must act on the alert.Select one mission-relevant attack path. Choose a user to resource, endpoint to server, or administrator path with an accountable owner. Do not start with the broadest network.Map normal behavior. Establish who legitimately administers the environment, which scanners and automated tools will touch it, and which change windows could create false positives.Place isolated, believable decoys. Decoys must not contain real sensitive data, provide a route into production, or disrupt mission operations. Their naming, protocol exposure, and location should be credible enough to attract relevant tradecraft.Integrate the detection. Route events to the SOC and correlate them with endpoint, identity, DNS, network, and relevant cloud telemetry. Define the severity, owner, escalation path, and time to containment objective before turning it on.Exercise the response. Purple team the scenario: simulate interaction, confirm the alert contains the necessary context, and test whether the team can isolate a device, revoke a session, rotate a credential, or block a path within the desired window.Measure and expand. Track time to detection, time to triage, time to containment, false positive rate, coverage of priority attack paths, and lessons that improve the underlying controls.&nbsp; The operational guardrails matterDeception in government environments must be governed like any other security capability. The authorization boundary, system owner, cyber operations center, incident response authority, privacy/civil liberties considerations, records requirements, classified environment constraints, and rules of engagement must be validated before deployment. In particular, teams should not assume that a commercial cloud capability, deception sensor, or automation workflow is approved for every DoW enclave or classification level.Decoys must also be genuinely inert. They should collect only the telemetry necessary for detection and investigation; they should never serve as a pivot point, store live operational data, or create an unmanaged exposure. The SOC needs an approved response matrix that distinguishes harmless reconnaissance from evidence requiring isolation or credential actions. Those decisions remain with the authorized government owners.The strategic value is not the decoy itself. It is the evidence it creates. Evidence that strengthens continuous verification, improves incident response, and exposes whether the architecture can actually limit an adversary after initial access.Zero Trust architecture shrinks the attack surface and limits where an intruder can go. Deception adds proof: if an actor gains a foothold, every attempt to move becomes visible. That is a meaningful advantage. Make the wrong move easy to detect and make the right defensive response routine.]]></description>
            <dc:creator>Andrew AJ Forysiak (Field CISO DOD)</dc:creator>
        </item>
        <item>
            <title><![CDATA[SAP November 2026 Patch Day: Four CVSS 10.0 Flaws, and Why Exposure Matters More Than Patch Speed]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/sap-november-2026-patch-day-four-cvss-10-0-flaws-and-why-exposure-matters</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/sap-november-2026-patch-day-four-cvss-10-0-flaws-and-why-exposure-matters</guid>
            <pubDate>Wed, 11 Nov 2026 17:07:44 GMT</pubDate>
            <description><![CDATA[On November 10, 2026, SAP&nbsp;fixed four critical vulnerabilities, all rated CVSS 10.0 and all exploitable without a login. They sit in the ICM, the Web Dispatcher, the SAP Gateway and the SAML2 service provider, the components closest to the network. None had been reported as exploited at publication.I wouldn't expect that to hold for long. In August, attackers started going after a critical SAP Commerce Cloud flaw&nbsp;three days after the fix shipped, before anyone had published an exploit for it. RISE with SAP customers have an extra wrinkle, because SAP's maintenance schedule determines when these fixes reach their landscape. Until they do, the thing you can actually manage is how exposed those systems are, and that's what the rest of this post covers. What SAP fixed in November 2026All four critical findings hit the parts of SAP that face the network: the HTTP stack, the reverse proxy in front of it, the gateway that application servers use to talk to each other, and single sign-on.ComponentCVEWhat goes wrongWorkaroundICM (NetWeaver AS ABAP)CVE-2026-76964Malformed WebSocket frames corrupt heap memory before login; possible code executionReach ICM only through a patched Web Dispatcher, and keep ICM ports unreachableSAP Web DispatcherCVE-2026-89126Same root cause in the reverse proxy, including embedded and HANA XS dispatchersDisable WebSocket support, which breaks ABAP Push Channels and some Fiori featuresSAP GatewayCVE-2026-89103With no explicit secinfo/reginfo rules, the gateway trusts the attacker as one of its own app serversNone in the noteSAML2 service provider (AS ABAP)CVE-2026-120017Some configurations skip the signature check on incoming assertions, so anyone can log in as any userNone; patch onlyOf the four, the gateway flaw says the most about where SAP risk comes from. The gateway decides trust based on network position, so traffic that looks like it came from inside the landscape gets treated as a peer. Zero trust architectures are built to get rid of exactly that assumption, and it's the thread running through everything below. How fast do attackers exploit SAP vulnerabilities?Critical SAP flaws are now getting weaponized within days of a patch, and occasionally before one exists. The table below covers the last eighteen months.WhenFlawPatch to exploitationAug 2026Commerce Cloud RCE (CVE-2026-58231, CVSS 10.0)3 days; attempts hit honeypots Aug 14 with no public PoCApr 2026SAP CAP and MTA npm packages (Mini Shai-Hulud)Not a vulnerability: four packages trojaned through a hijacked release pipeline, live for 2 to 4 hoursSep 2025S/4HANA ABAP code injection (CVE-2025-42957, CVSS 9.9)About 24 days; patched Aug 11, exploitation confirmed Sep 4Mar to Apr 2025NetWeaver Visual Composer (CVE-2025-31324, CVSS 10.0)Negative; exploited in the wild before SAP's Apr 24 emergency patchThe broader industry data points the same way. Mandiant's&nbsp;M-Trends 2026 puts the average time to exploit at an estimated minus 7 days, which means exploitation routinely starts before a fix ships.AI is shortening what's left of that timeline. In June, Anthropic showed a model&nbsp;turning freshly published patches into working exploits within an hour, at roughly $2,000 per Windows privilege-escalation exploit. A month earlier, Google's threat intelligence group reported the&nbsp;first zero-day it believes attackers built with AI help, which had been prepared for a mass exploitation campaign.Two caveats are worth stating plainly.&nbsp;VulnCheck's data shows exploitation in 2026 is fast but holding steady rather than accelerating, and nobody has documented an AI-built exploit against SAP yet. What has changed is the cost of reading an SAP patch and working backward to an exploit. That cost keeps falling, and patch windows were already too slow before it started. RISE with SAP: who patches, and what you still controlSAP's&nbsp;Roles and Responsibilities documents for RISE are the contract-level reference for who does what, and they split patching more finely than most customers assume. Kernel patches and Basis security notes are standard SAP services, so fixes like this month's ICM and Web Dispatcher notes land on SAP's maintenance schedule rather than yours. Application-level security notes are a packaged service bought separately, and testing implemented notes stays with the customer either way.The same document makes exposure largely your decision. SAP will provide an external IP and configure a web application firewall for internet-facing scenarios when you ask for them. Whether the Web Dispatcher should face the internet at all is yours to decide, along with which users, partners and networks can reach the gateway and the SAML endpoint, and how application identity and authorization are configured.For a RISE customer, then, the most useful question this week is what an attacker could reach while the fix is still in flight. Patch speed is largely out of your hands. What SAP teams should check this weekYou can answer all five of these with tools you already have. I'd get your SAP Basis and security teams in a room for an hour this week and work through them together, since each team usually holds half of the answer.Is any Web Dispatcher or ICM port reachable from the internet? Scan from outside your network, not from your asset inventory. If one is, it's exposed to CVE-2026-89126 or CVE-2026-76964 until patched.Can user networks reach the SAP Gateway on port 33xx? They shouldn't be able to. Following&nbsp;RedRays' guidance, confirm gw/acl_mode is 1 and that secinfo and reginfo have explicit rules rather than relying on the internal host keyword.Which identity providers does each system trust for SAML? Review the list in transaction SAML2, remove anything stale, and audit privileged SAML logons from unexpected sources.If you're on RISE, when is SAP applying the November notes to your landscape? Ask your SAP contact for a date, and plan your exposure around that date rather than Patch Day.Can your SAP systems call out to the internet freely? Web shells and credential theft both need an outbound path. The&nbsp;npm attack on SAP's developer packages sent stolen secrets straight to GitHub.&nbsp; Making those answers stick with zero trustThe checklist gets you through this week, but December's Patch Day will raise the same questions, and so will the one after that. A zero trust architecture keeps the answers to checks 1, 2 and 5 from drifting as your landscape changes. You still need SAP's fixes, since nothing in the architecture repairs a heap overflow or a skipped signature check, but it narrows who can reach the system while you wait for them.For user and partner access,&nbsp;Zscaler Private Access for RISE with SAP runs App Connectors inside the RISE private cloud. SAP manages them, and they only make outbound connections, so the Web Dispatcher and gateway are never published to the internet and a scanner looking for exposed SAP has nothing to find. Access is granted per user and per application. A contractor who needs Fiori never gets a network route to port 33xx, and neither does a compromised laptop sitting on the corporate network.ZPA also appears by name in SAP's own RISE&nbsp;Roles and Responsibilities as an optional service. SAP installs and configures the ZPA connector inside your landscape and allowlists it in the load balancer, and your team owns the access policy, the connection to your identity provider and the client rollout. Security and SAP Basis teams each keep the part they already run.Inbound access is half the picture. Most of the attacks in the table above also needed a way back out, whether that was a web shell calling home or stolen credentials heading to an attacker's GitHub repository.&nbsp;Zscaler Zero Trust Cloud inspects that egress traffic before it reaches the internet. Today, RISE customers can ask SAP to route their landscape's internet-bound traffic through their own Zscaler inspection, and some already do. That arrangement depends on SAP agreeing to it and isn't guaranteed to stay on the menu, so if outbound inspection matters to you, raise it with SAP now and get it written into your setup.Zero Trust Cloud also covers the traffic between workloads. A RISE landscape rarely stands alone: integration servers, middleware, partner systems and the applications in your own cloud accounts all exchange data with it. Zero Trust Cloud connects those workloads to SAP by policy instead of by network route, so a compromised integration server doesn't come with a network path into the SAP landscape. Where to startIf you own the RISE migration itself, this month's patches matter to you for a different reason. In the RISE programs we work on, the biggest source of delay is often keeping a zero trust architecture intact through the move: getting security to sign off on how users, partners and workloads will connect to the new landscape. Flaws like these are why that sign-off is hard to get, because no security team wants to put a Web Dispatcher on the internet or open the gateway to a flat network. Designing that access in at the start takes it off the migration's critical path.Whether you're planning the move or already on RISE, start by mapping what in your SAP landscape is reachable today: from the internet, from user networks and from partners. Zscaler's SAP team can work through that map with your application, Basis and security teams and show what a zero trust design would look like for your landscape.&nbsp;Talk to us about securing RISE with SAP.]]></description>
            <dc:creator>Bryan Ashley (Zero Trust Networking, Principal Architect)</dc:creator>
        </item>
        <item>
            <title><![CDATA[50% of the Fortune 500 Replaced Their VPN with Zscaler. What’s Holding Back the Rest?]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/50-fortune-500-replaced-their-vpn-zscaler-what-s-holding-back-rest</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/50-fortune-500-replaced-their-vpn-zscaler-what-s-holding-back-rest</guid>
            <pubDate>Tue, 10 Nov 2026 18:13:28 GMT</pubDate>
            <description><![CDATA[50% of the Fortune 500 Replaced Their VPN with Zscaler. What’s Holding Back the Rest?Every internet exposed IP address and open port on your network is an invitation to attackers, and Frontier AI is empowering the attackers to move faster than the enterprises can respond.&nbsp; Traditional VPN architectures, burdened with discoverable IP addresses and open inbound entry points, are rapidly turning into security liabilities in today's sophisticated threat ecosystem.Frontier AI has accelerated the speed and scale of attacks, giving threat actors the ability to scan vulnerabilities, identify exploit paths, and move laterally faster than a security team can patch systems. According to&nbsp;Zscaler ThreatLabz 2026 VPN Risk Report, 79% of organizations say the greatest AI-driven risk is attackers weaponizing vulnerabilities faster, while 70% report limited or no visibility into AI-enabled threats traversing their VPN connections.&nbsp;Inside the Castle-and-Moat: Let’s Examine VPN's Gateway ModelTraditional VPN architecture relies on a gateway model characterized by the following:DMZ placement:&nbsp;VPN gateways are positioned in the DMZ with public, DNS-published IP addresses that must be discoverable to enable connection.Inbound connections:&nbsp;Remote users initiate inbound connections to the gateway, requiring perimeter firewalls to keep inbound ports open to these public IP addresses.Network placement after authentication:&nbsp;Upon successful authentication, the VPN gateway assigns a virtual IP address and provisions network routes, placing the user directly onto the internal network/subnet.This architecture inherently expands the attack surface because the gateway must accept unsolicited inbound traffic from the public internet, making it easily discoverable to attackers. Consequently, a single unpatched gateway can expose the largely flat internal network, providing a primary entry path exploited in major VPN-gateway CVEs and enterprise breaches.&nbsp;&nbsp;Image 1: VPN architecture with gateways in the DMZ The rules of the game have changed, and legacy solutions were never built to play it.&nbsp;That's why 50% of the Fortune 500 didn't wait to adopt Zscaler. They eliminated exposed networks entirely by moving to&nbsp;Zscaler Private Access, and closed the front door that attackers had been targeting for years.&nbsp;Hiding applications to eliminate internet exposure is one of four powerful Zero Trust capabilities that Zscaler Private Access customers use to stop AI-powered attacks:&nbsp;Hide, Segment, Shield, and Deceive.Image 2: ZPA hides, segments, shields, and deceives threats in the AI Era&nbsp; So What’s Holding Back Other Enterprises Globally from Adopting Zscaler Zero Trust?What holds organizations back isn't technical limitations, but inertia—specifically, the fear of the unknown. Enterprise teams often worry about complex network re-architecting, whether legacy applications will work seamlessly in a Zero Trust model, and the operational risks if critical workflows break during the transition.50% of the Fortune 500 have already done it, so other enterprises can too. Zscaler recently added several capabilities in the Zero Trust Exchange platform to make this transformation as simple and painless as possible.Zscaler simplifies your Zero Trust transformation: Lift and shift effortlessly and adopt Zero Trust at your own paceJust like half of the Fortune 500, organizations can immediately transition to Zscaler Zero Trust for rapid risk reduction. For teams preferring a flexible pace, Zscaler ZPA offers enhanced features that guarantee 100% application compatibility throughout your gradual rollout.By executing a true lift-and-shift migration, you can onboard ZPA with near-zero operational disruption while maintaining full routing control and continuous application access.Phase 1 - Replace the VPN Gateway with "VPN for Legacy Apps"Enterprises can fully retire their VPN gateway and replace it with Zscaler's VPN for Legacy Apps, without rewriting access policies. Most importantly, the routing policies remain CIDR-based and security policy carries over unchanged. This is unique to ZPA for the following reasons.&nbsp;Specialized Network Connector: A virtual instance deployed in the data center replaces the VPN gateway, establishing an outbound-only tunnel to the Zero Trust Exchange so no inbound ports are ever opened and the internal network stays hidden from the internet.&nbsp;Bi-directional Support: For server-initiated traffic and real (non-NATed) IP binding, VPN for legacy apps keeps legacy protocols like VoIP, SCCM, and active FTP working seamlessly. These are precisely the traffic patterns that often force enterprises to maintain a full-tunnel VPN.The result is a like-for-like operational swap with a zero-trust architecture underneath, setting up the enterprise to selectively migrate crown-jewel apps onto full ZPA when they’re ready.Image 3: VPN for legacy apps replaces VPN gateways To deliver a lift-and-shift migration, Zscaler recently introduced&nbsp;key innovations, including user group-based access controls, wildcard FQDN support, static user IP assignments, micro-tenancy, and BGP route summarization.Phase 2 - Selectively Onboard Applications onto ZPAMigration isn't like a light switch. The Network Connector and App Connector work concurrently, allowing applications to be migrated incrementally:Move your crown-jewels to ZPA: Apps first move to standard ZPA App Connectors, where each application is defined as a discrete ZPA Application Segment with its own “per-app” policy. This enables true least-privilege and user-to-app access instead of network-level reachability.Server-initiated / server-to-client traffic stays on VPN for Legacy Apps: Standard ZPA App Connectors only support inside-out, user-initiated connections (user → app). Protocols requiring the server to initiate contact back to the client like VoIP signaling (SIP/H.323), SCCM pushes, and Active FTP's server-initiated data channels need the Network Connector's bi-directional tunneling and real IP binding. These stay on "VPN for Legacy Apps" by design, not as a temporary workaround.Both connector types can coexist on the same network segment, pointing at the same Zero Trust Exchange, so enterprises can migrate application-by-application instead of a single high stakes swap. Migration becomes incremental work instead of an obstacle blocking organizations from retiring legacy VPN gateways.Image 4: Transformation to ZPA to protect all applications Phase 3 - ZPA Takes Over and Automates Policy Creation Including App Segmentation PoliciesThe final phase eliminates manual overhead entirely by automating the process with&nbsp;Autonomous User-to-App Segmentation. Application discovery, segmentation, and policy creation operate seamlessly in the background without requiring human intervention.ZPA stands apart from other Zero Trust solutions because it automatically breaks down broad wildcard segments (such as *.company.com) into granular, least-privilege policies for individual applications (e.g., crm.company.com and confluence.company.com).&nbsp;Eliminating the need for tedious manual application mapping, ZPA delivers the following key capabilities:Discovery:&nbsp;Passively analyzing wildcard segment traffic (FQDNs, ports, and protocols), the AI engine identifies unmanaged applications. It can also integrate data from ServiceNow CMDB, Qualys, or Tenable to enhance initial discovery.Clustering:&nbsp;Using co-occurrence modeling, the system aggregates frequently co-accessed applications into unified logical segments. Meanwhile, domain-similarity heuristics isolate dev, staging, and production environments.Prioritization:&nbsp;Adaptive App Ranking evaluates clusters using domain structures, IP dependencies, and traffic volume, highlighting policies with the biggest blast radius.Policy generation:&nbsp;By mapping discovered application traffic to identity groups and real user access paths, the engine formulates targeted least-privilege policies (e.g., granting the Finance team access to only 5 designated apps) instead of broad subnet permissions. Each policy comes with a calculated attack-surface reduction metric and can be deployed with a single click.Continuous refinement:&nbsp;After deployment, the App Segmentation Insights dashboard proactively highlights new, idle, or overly broad segments.Image 5: Autonomous User-to-App segmentation eliminates lateral threat movement With Hide and Segment already in place,&nbsp;ZPA gives customers two additional defenses purpose-built for today's frontier AI-driven threats:Shield - Protect apps that must stay reachable.&nbsp;Autonomous Application Shield, built into the App Connector, scans which apps are actually running vulnerable software, blocks access and applies virtual patches inline.Deceive - Place realistic, high-fidelity&nbsp;Deception decoys and planted lure credentials directly along the paths an attacker would explore.&nbsp; &nbsp;A Simplified Path to Zero TrustTogether, this phased approach transforms your security landscape smoothly, turning your VPN to Zero Trust transition into a low-friction, continuous journey with zero workflow disruption.To help your IT team achieve a seamless migration and maintain a strong security posture, we strongly emphasize these three strategic phases as recommended best practices.Swap your VPN gateway with Zscaler’s "VPN for Legacy Apps" with no re-architecture while instantly eliminating the internet-facing attack surfaceMove your crown-jewel applications to ZPA at your own pace, coexisting with legacy VPN, so server-initiated applications (VoIP, SCCM) operate with zero downtime.&nbsp;Enable Autonomous User-to-App Segmentation to continuously discover, classify, and generate application policies on its own, turning coarse wildcard access into least-privilege, per-app zero trust without weeks of manual policy configuration.&nbsp;The result is a seamless transformation that happens entirely at your preferred pace without operational disruption - users remain fully productive, applications remain operational, and your attack surface continually shrinks.To start your transformation, refer to the&nbsp;Zscaler best practices for migrating from VPN to ZPA and take advantage of our latest innovations listed in&nbsp;What’s new in Zscaler SSE.&nbsp;]]></description>
            <dc:creator>Joby Menon (SVP, Product Management | Zscaler)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Strengthening Operational Resilience and Security for APRA CPS 230 and CPS 234]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/apra-cps-230-cps-234-operational-resilience-security</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/apra-cps-230-cps-234-operational-resilience-security</guid>
            <pubDate>Fri, 06 Nov 2026 17:01:29 GMT</pubDate>
            <description><![CDATA[For Australian financial institutions, meeting APRA expectations now means proving resilience in a world of cloud services, third-party dependencies and persistent cyber threats, as well as satisfying compliance requirements. Prudential Standards CPS 230 and CPS 234 raise the bar for both operational continuity and information security, pushing organisations to modernise how they protect critical services, data and users.The timelines make the point. CPS 234 has been in force since July 2019. CPS 230 has applied since 1 July 2025, and the transition period for pre-existing service provider arrangements ended on 1 July 2026. Both standards are now fully in effect, and for most institutions the question has moved from how the framework is designed to whether the evidence holds up.What we are hearing from financial institutions is that the regulatory burden goes well beyond adding more controls. The challenge is proving resilience across a much more complex operating environment. With growing dependence on cloud services, third parties and distributed users, many teams are finding that traditional approaches make it harder to meet rising regulatory expectations efficiently. Understanding the MandatesWhile CPS 230 and CPS 234 address different areas, together they reinforce a common expectation: financial institutions must be able to protect critical assets and continue operating during disruption.CPS 230: Operational Risk ManagementFocuses on resilience, business continuity and third-party risk. Institutions must identify critical operations, define disruption tolerances and maintain service continuity during severe events. APRA names the operations it expects to be treated as critical at a minimum: payments, deposit-taking, custody, settlements and clearing for banks; claims processing for insurers; investment management and fund administration for superannuation trustees. Each needs Board-approved tolerance levels, a credible business continuity plan tested against severe but plausible scenarios, and a register of material service providers. A material operational risk incident must be notified to APRA within 72 hours, and a disruption to a critical operation outside tolerance within 24 hours.CPS 234: Information SecurityFocuses on safeguarding information assets through effective security controls, testing, governance and incident response. The Board is ultimately responsible for information security, controls must be proportionate to the sensitivity and criticality of each asset, and their effectiveness must be tested systematically. Material incidents must be notified to APRA within 72 hours, and material control weaknesses that cannot be remediated promptly within 10 business days. An incident reported under CPS 234 does not need to be reported again under CPS 230. How Zscaler Helps Regulated Entities ComplyTo support these security and resilience mandates, the Zscaler Zero Trust Exchange™ provides a cloud-native architecture that eliminates implicit trust. Operating as a globally distributed service, it enforces strict, identity-based, least-privilege access and performs continuous inline inspection across the internet, SaaS and private applications.Because every connection is brokered and inspected, every policy decision is also logged: who accessed what, which threat was blocked, which configuration changed. That telemetry, exported to your SIEM or GRC platform, is the evidence base that both standards, and your auditors, ask for.Governance, risk appetite and regulatory reporting remain the responsibility of the regulated entity. Zscaler provides the architectural enforcement and technical controls that support APRA-regulated entities in meeting their obligations.How Zscaler Supports CPS 230Improve resilience without relying on legacy infrastructureBy removing dependence on centralised VPNs and traditional perimeter controls, Zscaler helps reduce single points of failure and supports more resilient access to critical applications. In a hub-and-spoke design, one failed concentrator or one compromised branch can become a disruption to payments or claims processing. Connecting users directly to the applications they are authorised to use removes that path.Maintain access during disruptionCapabilities such as Business Continuity Cloud, part of Zscaler Resilience, help organisations preserve secure user access during major outages or disruptive events. It provides a customer-specific backup instance, isolated from the primary cloud, that maintains equivalent security policy during failover rather than bypassing controls to restore connectivity. Private Service Edge offers a local on-ramp, and disaster recovery mode lets Zscaler Client Connector fall back to pre-defined emergency policies. Our Resilience Audit helps teams rehearse failover against their own recovery time objectives, which supports the testing CPS 230 requires, including scenarios where a material service provider fails.Improve visibility across third-party servicesWith Zscaler Digital Experience (ZDX), teams can monitor the digital experience across users, SaaS platforms and service providers, helping support oversight of critical external dependencies. When a disruption occurs, ZDX shows whether it originated in your own environment, with an ISP or with a SaaS provider. That is the kind of evidence CPS 230 expects when you monitor material service providers against agreed service levels.Support local enforcement and data handling requirementsZscaler's presence in Australia helps organisations align security enforcement more closely with local operational and data handling expectations. CPS 230 requires entities to assess the risks of geographic location and to notify APRA before entering a material offshoring arrangement, so knowing where traffic is processed and where logs are held is part of the assessment.Support your due diligence on Zscaler itselfCPS 230 treats providers of risk management and core technology services as material unless the entity can justify otherwise, so a security platform that supports critical operations is likely to appear on your register. We built the CPS 230 guide on that assumption. To support your assessment, Zscaler provides independent assurance, including IRAP assessment at the PROTECTED level, SOC 2 Type II and ISO/IEC 27001, through the Zscaler Compliance Center; live availability and performance data on the Zscaler Trust Portal; contractual SLAs; and open standards such as SAML, SCIM, IPsec and GRE that support an orderly exit if one is ever needed.How Zscaler Supports CPS 234Reduce attack surface and limit lateral movementZscaler connects users directly to approved applications rather than placing them on the corporate network, helping reduce exposure and contain compromise. With Zscaler Private Access (ZPA), private applications are not reachable from the internet, so there is nothing for an attacker to scan, and a compromised account reaches only the applications that user was entitled to.Inspect traffic and stop threats inlineInline inspection and advanced threat protection help identify malicious activity before it reaches users or sensitive environments. Zscaler Internet Access (ZIA) inspects internet and SaaS traffic, including encrypted traffic, with cloud firewall, intrusion prevention, DNS security and sandboxing applied in a single pass.Protect sensitive data wherever it movesDLP and CASB capabilities help organisations discover, classify and protect sensitive information across web, SaaS and private application traffic. Exact data match, file fingerprinting and optical character recognition let you apply controls proportionate to the sensitivity of each information asset, which is what CPS 234 asks of control design.Strengthen control consistency in hybrid environmentsZscaler applies policy more consistently across branch offices, remote users, cloud workloads and third-party access models. One policy, enforced everywhere and logged on every transaction, also gives you continuous evidence of control effectiveness, far more than a point-in-time sample, which supports the systematic testing CPS 234 requires. The Next Test: Extending the Same Principles to AIWhat we are seeing is Boards shifting the question from "are we secure?" to "can we keep delivering critical operations when something we depend on fails?" APRA's April 2026 letter on artificial intelligence raises that bar again. AI agents, AI built into supplier platforms and staff using unapproved AI tools bring new identities, new data flows and new fourth-party dependencies. APRA has said it expects enforceable preventative controls and continuous assurance, and that policy direction and after-the-fact detection on their own fall short.The Zero Trust principles that underpin CPS 230 and CPS 234 now have to extend to AI: verify every identity, human or machine, and inspect every flow. Institutions that treat these standards as the foundation for governing AI will be best placed to adopt it with confidence. Those that treat them as a finished compliance exercise will be revisiting the same gaps under a new heading. What Remains With the Regulated EntityZscaler provides technical controls, telemetry and architecture. Risk appetite, the designation of critical operations, tolerance levels, Board approvals, materiality decisions and notifications to APRA stay with the institution. Nothing Zscaler provides replaces your own legal, regulatory or prudential assessment. Simplify Your Compliance JourneyNavigating APRA's requirements is a continuous journey, and it calls for a unified approach to security and resilience that serves both standards at once. The Zscaler Zero Trust Exchange gives financial institutions a technical foundation that supports both CPS 230 and CPS 234 while allowing them to adopt cloud services with confidence.To support that work, we have developed a control mapping guide for each standard, and a third for APRA's AI expectations. They work through the requirements one by one, separating what the entity owns from how Zscaler capabilities align, and are written to support control design and evidence discussions with your risk, audit and security teams.Download the CPS 230 Control Mapping Guide&nbsp;Download the CPS 234 Control Mapping GuideDownload the APRA AI Supervisory Expectations Mapping GuideTo discuss how these map to your own critical operations and tolerance levels, contact your Zscaler team.]]></description>
            <dc:creator>Thomas Ferguson (Senior Sales Engineer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[How to Secure GenAI Usage in the Enterprise]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/secure-generative-ai-usage-in-enterprise</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/secure-generative-ai-usage-in-enterprise</guid>
            <pubDate>Thu, 05 Nov 2026 22:17:57 GMT</pubDate>
            <description><![CDATA[Securing GenAI usage matters because generative AI is now part of daily work, and every prompt can carry sensitive data. Employees use GenAI to write code and summarize documents in seconds, while CISOs work to keep source code, customer records, and intellectual property from leaving the organization through those same prompts.The Zscaler ThreatLabz 2026 AI Security Report found that enterprise AI and machine learning (ML) transactions rose 91% year over year in 2025, reaching 989.3 billion across the Zscaler Zero Trust Exchange™ platform. Data volume followed: 18,033 TB of corporate data flowed to AI and ML applications, a 93% increase.ChatGPT alone generated over 410 million data loss prevention (DLP) policy violations as users tried to share sensitive intellectual property and source code.According to the same report, enterprises blocked 39% of AI and ML transactions in 2025. Blocked transactions often indirectly encourage employees to use unsanctioned tools. Unrestricted access, which allows open use of any AI app without data controls, puts intellectual property and customer trust at risk.To safely adopt AI with confidence, organizations should adopt a secure-by-design zero trust architecture. From blocked to enabled: How zero trust secures GenAI usageZero trust secures GenAI usage by continuously verifying the user, device, application, and content of every AI session. Unlike static controls, which make one decision per destination, continuous controls evaluate each prompt and upload in real time and can change their decision the moment risk changes.A static control, such as an IP block list or URL filter, makes one decision based on the destination and applies it to every session. If the AI domain is approved, all traffic passes, whether the prompt asks for a recipe or contains source code.A continuous control keeps checking throughout the session. It evaluates the identity of the user, the health of the device, the specific application, and the content of each prompt and upload. It can change its decision the moment any of those factors change.This difference matters because GenAI risk lives in the payload. Static tools verify the address but ignore the content of the prompt, the uploaded file, and the model’s response, so sensitive data in transit goes unchecked. Their lists also need manual updates, and new AI apps can be deployed faster than any list can grow. Continuous controls apply policy to every request in real time.Zero trust changes what security teams inspect. Instead of trusting a destination, it evaluates every request on its own merits, using live context about who is asking, from which device, and what the content contains. The Zscaler Zero Trust Exchange applies this model inline, between users and AI apps, so policy decisions happen before data leaves the organization.Three core zero trust capabilities make that verification practical:Continuous asset discovery: It all starts with full visibility. Automated discovery enables the identification of shadow AI tools, custom-built models, and third-party SaaS integrations with embedded AI features.Granular access control: Identity is what drives every decision. Policies grant access to internal or high-risk LLMs to authorized personnel only. Rules adapt to role, device posture, and risk level.Browser isolation: Browser isolation streams external LLM sessions to the user as safe pixels. Employees get read-only interaction with the model. Administrators can restrict pasting, uploading, and downloading inside the session.&nbsp;“Zero trust mandates continuous verification of identity and trustworthiness of users, devices, and networks, regardless of their location or whether they are inside or outside the network perimeter.”– Ankit Gupta, Sr. Product Marketing Manager, Zscaler&nbsp; Comparing GenAI security approachesSecurity DimensionThe “Block Everything” ApproachLegacy Bolt-on SecurityUnified Zero Trust SASE with ZscalerBusiness EnablementHalts productivity and drives employees toward unsanctioned toolsPermits limited use and degrades the user experienceProvides secure browser isolation for unsanctioned GenAI appsDLP SophisticationOffers none because queries are simply blockedApplies static filters that miss prompt contextAnalyzes prompt content in real time with user and app contextSSL InspectionLeaves allowed AI traffic uninspectedAdds latency and leaves blind spots in encrypted streamsInspects SSL in a single-pass architecture at petabyte scaleCompliance ReadinessAchieves compliance only by restricting employee productivityLacks a unified dashboard for reporting and auditsProvides built-in compliance mapping for frameworks such as the EU AI Act and NIST AI RMF&nbsp; How to prevent data leakage in GenAI workflowsThe most critical step in preventing data leakage in GenAI workflows is keeping proprietary data out of public LLMs. Source code, customer records, and API keys submitted in a single prompt can leave enterprise control permanently, and some public models may use submitted content for training. Prevention must happen before the data leaves the network.Enable inline SSL inspection and real-time DLPNearly all GenAI traffic is encrypted, so inspection starts with decrypting it. Inline SSL inspection opens each session at scale, and the content then passes through data loss prevention (DLP) engines in the same pass.Context-aware DLP reads the prompt itself. It weighs the user, the destination app, and the data type, then decides whether to allow, redact, or block. This intercepts file uploads and copy-paste events as they happen. For example, a developer can ask an LLM to explain a public algorithm, but a prompt containing an internal API key is stopped.Enforce Cloud Browser Isolation for safe researchBrowser isolation lets employees use GenAI tools safely. The AI session runs in a secure cloud container, away from the employee’s device, which receives only a live image of the page, much like a video stream.&nbsp;“Cloud Browser Isolation renders web content in the cloud, and streams threat-free web page content to users, preventing web-based threats from reaching and infecting employee devices…By isolating web content in the cloud, CBI provides enhanced protection against web-based threats, simplifies security management, and supports remote work.”– Niraj Gopal, Head of Product Management, Federal and Sovereign Clouds, Zscaler&nbsp;Employees can still read, research, and learn from the model. CBI blocks clipboard transfers and enterprise file uploads, so productivity continues while sensitive data remains protected. Security concerns for custom-built LLMs and autonomous agentsEnterprises that build their own AI apps or deploy multiagent systems through the Model Context Protocol (MCP) face three prevalent risks:Prompt injection: Attackers trick models into following hidden instructions.Data poisoning and model tampering: Attackers corrupt training data or alter the model itself.Unauthorized agent actions: Autonomous agents may run tools or call APIs without authorization.These weaknesses are easy to exploit. In red team testing for the ThreatLabz 2026 AI Security Report, Zscaler found critical vulnerabilities in 100% of the AI systems tested, with a median time to first critical failure of 16 minutes.Regulatory expectationsUnder the EU AI Act, providers of general-purpose AI models must maintain technical documentation covering the model’s training and testing process and the data used for training, testing, and validation. According to the European Commission’s guidelines, an organization that fine-tunes a model becomes the provider of a general-purpose AI model only when the modification uses more than one-third of the original training compute.The EU AI Act also sets separate risk management and documentation duties for high-risk AI systems. Teams should record datasets, security controls, and risk assessments from the start.Containing a compromised agentMicrosegmentation backed by zero trust principles gives each agent, model, and data store its own boundary. Strict API controls limit which tools and endpoints an agent can call. If an attacker hijacks one agent, the compromise stays inside that segment, and lateral movement across the corporate network stops. The path forward: Innovate with confidenceSecuring generative AI works best when security controls act as an invisible guardrail. Employees maintain productivity, and the organization keeps its data secure.The Zscaler Zero Trust Exchange secures generative AI usage, gives security teams full inline visibility into AI traffic, and applies real-time DLP to every prompt. Zscaler Zero Trust Browser contains risky sessions. Microsegmentation and API control protect custom models and agents. Built-in compliance mapping helps organizations align with regulatory frameworks like the EU AI Act and NIST AI RMF.With zero trust in place, every new AI model or agent enters an environment that already verifies identity and inspects content. Access stays limited to what each user or agent needs, and teams can scale AI initiatives without waiting for security reviews to catch up.With Zscaler, organizations can say yes to generative AI with confidence. Request a custom product demo to learn more.]]></description>
            <dc:creator>Julia Benson (Senior Web Content Writer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[When AI and Multicloud Broke the Financial Services Compliance Playbook]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/when-ai-and-multicloud-broke-financial-services-compliance-playbook</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/when-ai-and-multicloud-broke-financial-services-compliance-playbook</guid>
            <pubDate>Wed, 04 Nov 2026 23:00:00 GMT</pubDate>
            <description><![CDATA[Two forces are rewriting financial services compliance - and regulators are no longer waiting. The 2026 IBM Cost of a Data Breach Report found AI-driven attacks surged 56% year over year, with financial services bearing the highest breach cost of any sector at $6.29 million per incident.1 Shadow AI alone adds $670,000.2 Meanwhile, cloud concentration risk turned theoretical when a 15-hour AWS outage in late 2025 simultaneously disrupted Coinbase, Robinhood, and parts of Lloyds Banking Group3 - prompting the EU to designate 19 critical ICT third-party providers under DORA for direct supervisory oversight.4&nbsp;The regulatory response in 2026 has been sweeping: the U.S. Treasury published the Financial Services AI Risk Management Framework mapping 46 AI risks to technical controls,5 the Federal Reserve replaced SR 11-7 with SR 26-2 to carve out generative AI entirely,6 and FINRA became the first U.S. regulator to require firms to capture agentic AI output as supervised communications.7 AI and multicloud didn't just change the technology stack - they forced an overhaul of the compliance standards themselves. The legacy architecture problemMany financial institutions still run legacy infrastructure that makes compliance far more painful than it needs to be. Flat networks and VPN-centric models put sensitive data within reach of too many systems. Virtual firewalls replicate the complexity of physical appliances in every cloud, creating inconsistent controls and audit preparation processes that are manual, error-prone, and expensive.The result: compliance teams spend weeks pulling evidence for a single audit cycle, security architects maintain separate rule sets across environments, and a single misconfigured firewall can put an entire assessment at risk.When the architecture itself creates friction, no amount of process improvement will fix it. Why zero trust changes the equationA zero trust architecture flips the model. Instead of building walls around a network perimeter and trusting everything inside, zero trust assumes no implicit trust - every connection between users, devices, workloads, and applications is verified and governed by policy.For financial services compliance, this has three practical implications:Segmentation becomes a built-in control, not a bolt-on project.&nbsp;Frameworks like DORA, SWIFT, and PCI DSS all require network segmentation - isolating critical systems from the general IT environment. With zero trust, microsegmentation is the architecture. Workloads communicate only when an explicit policy permits it, enforced consistently across AWS, Azure, GCP, and on-premises environments. For PCI DSS, this kind of segmentation can reduce the scope of an entire assessment by isolating the cardholder data environment from the rest of the network.Evidence collection is a by-product, not a project.&nbsp;Zero trust platforms enforce policy continuously and log every flow and policy decision immutably. Those records can be exported directly to SIEM and GRC platforms, turning what used to be a manual evidence-gathering exercise into an automated output of day-to-day operations. For SOC 2 Type II examinations - where auditors test whether controls operated effectively over a sustained period - this kind of continuous evidence is exactly what's needed.AI workloads get the same governance as everything else.&nbsp;As banks adopt agentic AI, regulators are extending existing security obligations to cover AI deployments. A zero trust architecture applies the same least-privilege policies, egress controls, and traffic inspection to AI workloads that it does to core banking and payment systems. Data classification policies can govern which model endpoints a workload is permitted to call and prevent sensitive data from reaching unsanctioned models. Six frameworks, one architectural foundationOur new white paper,&nbsp;Audit-Ready by Design: How a Zero Trust Architecture Helps Financial Services Firms Simplify Compliance, maps the Zscaler Zero Trust Cloud's capabilities to six of the frameworks that matter most to financial services firms today:PCI DSS 4.0.1 -&nbsp;The payment card industry standard, now fully enforceable with its emphasis on continuous security and scope reduction through segmentation.SWIFT CSCF v2026 -&nbsp;The latest version of SWIFT's Customer Security Controls Framework, including the new scope expansion to customer client connectors.DORA -&nbsp;The EU's Digital Operational Resilience Act, now in active enforcement, covering ICT risk management, incident reporting, resilience testing, and third-party risk for more than 22,000 financial entities.SOC 2 -&nbsp;The AICPA's Trust Services Criteria, where continuous control evidence is central to a Type II examination.GDPR -&nbsp;The foundational data protection regulation, where microsegmentation and data loss prevention map to Article 32's security obligations.EU AI Act -&nbsp;The first comprehensive AI regulation, with cybersecurity requirements for high-risk systems that zero trust directly supports.For each framework, the paper provides a detailed control-by-control mapping that shows where the Zscaler Zero Trust Cloud delivers full coverage, where it provides partial support, and where responsibility sits entirely with the financial institution. It's an honest, transparent assessment - not a checkbox exercise. Built for the compliance reality financial firms face todayThe regulatory environment isn't going to simplify itself. Frameworks are overlapping, enforcement is accelerating, and the adoption of AI is introducing entirely new categories of risk that regulators are folding into existing obligations rather than waiting for new ones.The firms that will navigate this environment most effectively aren't the ones with the biggest compliance teams. They're the ones whose architecture makes compliance a natural outcome of how their systems operate - where audit readiness is built in, not bolted on.Download the&nbsp;white paper to see the full control-by-control mappings across all six frameworks and learn how a zero trust architecture can simplify your compliance posture.&nbsp;&nbsp;1&nbsp;IBM, Cost of a Data Breach Report 2026. Analysis:&nbsp;Varonis, "IBM's Cost of a Data Breach Report 2026," 2026.2&nbsp;IBM, Cost of a Data Breach Report 2025; Analysis:&nbsp;Clarista, "AI Data Governance for Financial Services: A 2026 Framework."3&nbsp;Cognetryx, "What Is Cloud Concentration Risk? A Guide for Financial Firms," 2026.4&nbsp;European Supervisory Authorities (EBA, EIOPA, ESMA), CTPP designation, Nov 18, 2025. See:&nbsp;HYPR, "Cybersecurity Regulations for Financial Services for 2026 and Beyond."5&nbsp;U.S. Dept. of the Treasury &amp; FSSCC, Financial Services AI Risk Management Framework, Feb 19, 2026. See:&nbsp;Clarista, "AI Data Governance for Financial Services: A 2026 Framework."6&nbsp;Federal Reserve SR 26-2, Apr 17, 2026; OCC Bulletin 2026-13. See:&nbsp;Superintelligence Compliance, "AI Regulation in Financial Services: SR 26-2 and Reg B."7&nbsp;FINRA, 2026 Annual Regulatory Oversight Report, Dec 9, 2025. See:&nbsp;AccuroAI, "Financial Services AI Security: The 2026 Playbook."&nbsp;]]></description>
            <dc:creator>Nikitha Omkar (Senior Product Marketing Manager)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Replace VDI with Zero Trust Browser: Even Thick-Client Apps Can Now Be Streamed]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/replace-vdi-zero-trust-browser-even-thick-client-apps-can-now-be-streamed</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/replace-vdi-zero-trust-browser-even-thick-client-apps-can-now-be-streamed</guid>
            <pubDate>Wed, 04 Nov 2026 19:52:23 GMT</pubDate>
            <description><![CDATA[Replace VDI with Zero Trust Browser: Even Thick-Client Apps Can Now Be StreamedEvery major shift in how enterprises deliver applications has created a corresponding gap in security and access. Client-server gave way to web apps. Web apps moved to SaaS. SaaS moved to the browser. At each step, the access model caught up, sometimes years later.One holdout remains: thick-client applications.SAP GUI, financial modeling tools, developer IDEs, database management utilities. These applications still require a full desktop runtime. They cannot run natively in a browser, and organizations cannot simply rewrite them. So the default answer, for the past two decades, has been VDI.VDI works. It also costs up to&nbsp;$1,800 per user annually. It requires dedicated infrastructure: brokers, gateways, golden images, GPU pools, persistent storage, and specialized EUC teams to keep all of it running. Worse, VDI environments are network-centric by design. Desktops sit on internal networks with broad lateral movement paths, and access typically rides a VPN or VDI gateway that exposes a public attack surface. Recent high-profile vulnerabilities in those gateways have underscored exactly how fragile this model is.While Zero Trust Network Access has transformed how enterprises securely connect users to applications—including thick-client applications accessed through the Zscaler Client Connector—delivering those same thick clients to unmanaged devices remains a challenge. BYOD users, third-party contractors, and offshore teams often cannot install an endpoint agent, and for these scenarios, organizations still default to VDI, introducing significant infrastructure costs, operational complexity, and the same lateral movement risk they have been working to eliminate everywhere else.We built Zero Trust Browser Application Isolation to address that. The Zscaler Zero Trust Browser now supports thick-client application delivery through a capability we call Application Isolation.The concept is straightforward: thick-client applications execute inside isolated, ephemeral cloud environments managed by Zscaler. The user sees the application rendered inside the Zero Trust Browser, launched from the same landing page where their web and private applications already live. Administrators define which applications are available, assign them to user groups through access policies, and apply data protection controls through the same browser-native DLP they already use for web sessions.This post covers the architecture, how it changes the access model for thick clients, where the security controls sit, and what it means for organizations still running VDI. Traditional VDI delivers a full desktop. The user connects to a virtual machine, and inside that VM, they open the applications they need. The desktop is the unit of delivery. Everything that comes with a desktop (the OS, the image, the licensing, the patching, the startup time) comes along for the ride.Zscaler takes a different approach. Rather than requiring a dedicated VDI client or customer-managed infrastructure, it delivers cloud-hosted environments directly through the Zero Trust Browser. Users can seamlessly launch their desktop sessions in a browser tab, with access to their thick-client applications.The user opens the Zero Trust Browser and sees their entitled desktop environments alongside their web and private applications. One workspace. One landing page. One set of access policies governing all of it. Every session with Application Isolation routes through the Zscaler Zero Trust Exchange. Internet and SaaS traffic flows through ZIA for full inline inspection. Private application traffic flows through ZPA. All connections are brokered and identity-verified, bound to the authenticated user, not to a network path.There is no direct outbound route that bypasses Zscaler. The architecture enforces this by design, not by policy.Last-mile data protection controls apply at the browser layer. Clipboard restrictions, file transfer controls, dynamic watermarking, and anti-screenshot protection all work the same way they do in web isolation sessions. Administrators configure them from the same console, using the same policy framework. If you already manage DLP policies in the Zero Trust Browser for web applications, the same policies extend to thick-client sessions without additional configuration.Session persistence is enabled by default. Users can disconnect and reconnect to a running session with unsaved work intact. In future releases, we will introduce configurable session persistence policies, including an ephemeral mode where the environment self-destructs on disconnect and leaves no residual state—ideal for high-risk contractor scenarios.In the demo below, the user launches a persistent, isolated thick-client workspace directly from the Zero Trust Browser landing page — one click into a new tab, no local agents, VDI clients, or complex setup required. From there, they connect to a corporate CRM database hosted behind Zscaler Private Access, opening DBeaver and querying live account data without ever touching a VPN. To show the flexibility of the environment, they then drop into the command line and install the Geany editor using standard sudo permissions — just as they would on a local machine. Throughout the session, mouse tracking stays fluid and keyboard input registers instantly, with no perceptible latency between the remote workspace and the user's browser. Three things have converged to make this urgent.First, VDI licensing economics are getting worse, not better. Major vendors have raised prices and changed licensing terms repeatedly over the past several years. For organizations running thousands of VDI seats primarily to deliver a handful of thick-client applications, the cost-per-app math has become increasingly difficult to justify.Second, contractor and BYOD access patterns have grown more complex. Offshore development teams, third-party service providers, and acquired employees all need access to internal thick-client applications. Installing endpoint agents on unmanaged devices is often impractical or prohibited. VDI has been the default fallback, but it introduces the same infrastructure burden and lateral movement risk for external users that it does for internal ones.Third, the Zero Trust Browser has matured to the point where extending it into application delivery is a natural next step. The browser already handles web isolation, data protection, posture verification, and identity-based access. Adding cloud-hosted thick-client rendering to that same architecture lets organizations consolidate another access silo onto a platform they already operate. Replace VDI with Zscaler Zero Trust Browser. Instead of maintaining slow, expensive, and complex virtual desktops to run a handful of desktop apps, you can now publish remaining thick-client workloads directly into Zscaler’s Zero Trust Browser. By consolidating your thick-client access alongside the web and SaaS applications you already deliver natively through the browser, you can completely replace VDI solutions. The applications keep running while the complex infrastructure goes away.Secure contractor and offshore access without agents. Third-party developers access SAP, database utilities, and development environments from personal laptops through the Zero Trust Browser. Enterprise data stays inside the cloud. Copy/paste and file downloads are governed by policy.Stand up developer workspaces. Engineers get persistent, pre-configured environments with their IDEs, terminals, and database tools. Source code never touches the local endpoint, and connectivity to internal repositories flows through ZPA.Enforce DLP on sensitive applications. Financial analysts run modeling tools inside watermarked, screenshot-protected sessions. The controls are browser-native, so the user's workflow stays the same.Accelerate M&amp;A onboarding. Acquired employees access core business applications through the browser on day one. No network integration, no Active Directory trust configuration, no months of infrastructure work before someone can be productive. Application Isolation extends the Zero Trust Browser from an access and security layer into an application workspace. For organizations that have already consolidated internet, SaaS, and private application access onto the Zscaler Zero Trust Exchange, thick-client delivery was one of the last remaining reasons to maintain a parallel VDI environment.That reason is going away.The direction is the same one that has guided the platform from the beginning: every layer doing the job it does best, every layer working together, and zero trust extending wherever work happens.To learn more about Application Isolation in the Zero Trust Browser,&nbsp;contact your sales representative.]]></description>
            <dc:creator>Joby Menon (SVP, Product Management | Zscaler)</dc:creator>
        </item>
        <item>
            <title><![CDATA[When Freezers Become Ovens: Why OT Needs Zero Trust Now]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/when-freezers-become-ovens-why-ot-needs-zero-trust-now</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/when-freezers-become-ovens-why-ot-needs-zero-trust-now</guid>
            <pubDate>Wed, 04 Nov 2026 01:29:08 GMT</pubDate>
            <description><![CDATA[On Monday, Nov 2nd, grocery chains across Europe&nbsp;experienced temperature spikes that destroyed tens of millions of dollars worth of perishable food across thousands of locations. This happened less than three weeks after similar attacks in France when refrigeration units across hundreds of&nbsp;supermarkets—Intermarché, Carrefour, E. Leclerc, and others—were remotely driven into "defrost" mode overnight. Temperatures climbed past 100°F. Freezers turned into ovens, destroying all the perishable food within. Threat actors targeted internet-connected refrigeration controllers, forcing systems into a continuous, 50°C (122°F) defrost cycle. Because a defrost is a legitimate operational state, the controllers suppressed standard automated alarms, keeping store personnel in the dark until morning. The result was massive food waste and supply chain chaos.Whether the target is a supermarket, a manufacturing plant, a warehouse, or a military installation, the lesson is clear: when cyberattacks reach operational technology (OT), the consequences become physical—spoiled inventory, food shortages, safety risks, and loss of public trust. The “Patch” Reality in OT SystemsThe primary driver behind these attacks is a critical vulnerability (CVE-2025-41450) uncovered by Claroty’s Team82 in their&nbsp;report. This authentication bypass in widely used Danfoss AK-SM 800A controllers allowed anyone reverse-engineering a simple date-based algorithm to bypass login screens. Compounding the issue, scanning platforms revealed&nbsp;thousands of these controllers exposed directly to the public internet. But as we highlighted in our earlier blog post —"The Fix Has Been Out for a Year. The Controller Is Still Exposed"—these devices remain largely unpatched and still exposed.Traditional IT security best practices recommend patching all systems regularly, but OT operators face unique hurdles:Downtime Risks: Taking operational systems offline risks production downtime, supply interruptions and product wastage.End-of-Life Assets: Many active controllers are legacy models that are no longer supported or patched.Resource Constraints:&nbsp;Many OT controllers may not have sufficient memory or CPU resources to accept the patch. Hardware upgrades are expensive.All of these ensure the ongoing availability of an enormous unpatched OT attack surface. It doesn’t take an attacker —or an AI agent— long to figure out a damaging exploit and cause chaos. Refrigeration systems today, water plants tomorrow, power grids the day after? Why This Keeps HappeningRefrigeration controllers, like most OT and industrial IoT devices, were never designed with the modern threat landscape in mind. They're deployed for decades, maintained by third-party technicians who need remote access, and frequently connected directly to the internet because segmenting them properly takes effort most operators don't have time for. Add flat, “trust-everything” networks, and one exposed controller becomes a bridge into an entire facility—or, as we're now seeing, a repeatable playbook an actor can run against hundreds of sites in parallel.Firewalls and VPNs don't solve this. They were built to protect perimeters, not to stop an attacker from walking laterally once it's inside. Adding another appliance or service doesn’t fix this when lateral movement is the feature, not the flaw. OT environments need an architecture that assumes compromise is possible and limits what any single device—or attacker—can reach. Zero Trust Changes the Operating ModelZero trust isn’t just a feature on a firewall. It’s a fundamentally different architectural approach. If your starting point is a flat network with implicit trust, you cannot get to zero trust by simply inserting firewalls everywhere. It’s like building a superhighway and adding toll gates every few miles—it’s expensive, complex and slows everyone down.Zero trust starts by not extending the same network everywhere. All communication is brokered through an exchange based on identity and context, with continuously-monitored adaptive access. No route extension. This eliminates unrestricted lateral movement between sites. For OT that means replacing broad network access with granular segmentation — both between and within sites. All communication in &amp; out should be restricted to what the OT systems need, and no more. A controller should communicate only with approved services—not with any device that happens to share a subnet.Another key principle of a zero trust architecture is eliminating the attack surface. All connections are inside-out — from the factory or supermarket out to the Internet — not the other way around. No exposed VPN ports. No attack surface for hackers to exploit.For OT, that means eliminating all exposure to the Internet or third-party networks. A refrigeration technician should be able to reach the authorized controller for a defined maintenance action—not gain routable access to the store, site, or plant network. Zscaler Zero Trust for IoT/OTZscaler protects OT environments in three ways.1. Eliminates the attack surfaceTraditional SD-WAN or VPN-based connectivity extends the corporate network to every location. Firewalls and VPNs —often required for third-party vendor access—leave open exposed ports that become a route inwards. That model makes every device, factory or supermarket an attractive target because compromise at one site becomes an open door into the entire organization.Zscaler’s Zero Trust architecture hides everything. It enables users, agents and IoT/OT systems to securely communicate with apps through the Zero Trust Exchange, without exposing controllers and firewalls to the Internet.&nbsp;Zscaler’s Zero Trust Branch securely connects fixed sites such as supermarkets or warehouses, while&nbsp;Zscaler Cellular connects field assets and mobile IoT/OT (ex. fleet vehicles, remote sensors, scanners etc.).&nbsp;Zscaler Privileged Remote Access also enables third parties to securely connect to IoT/OT systems through a browser without ever being on the OT network.2. Eliminates lateral threat movementUnpatched OT systems will continue to remain a reality for the foreseeable future. What if you could isolate each controller, PLC or HMI into a “network-of-one” and limit the blast radius in the event of a compromise?Zscaler Zero Trust Device Segmentation, a key capability within Zero Trust Branch, does just that. Every device is isolated into a /32 micronetwork segment — without the need for agents or certificates on the OT system, removing a huge barrier for granular microsegmentation within OT environments. Each supermarket and controller becomes an island. All communication within the site is restricted — even within the same VLAN. This limits the ability of attackers to reach controllers by moving laterally, and in the event they do gain access to one, it ensures they cannot compromise the entire supermarket or warehouse.3. Ensures effective visibility &amp; controlPlant operators often lack a full inventory and understanding of their OT systems. Traditional approaches from the IT world, like scanners and agents, do not work on OT systems. Many OT devices are far too brittle or outdated. As a result, plants and supermarkets remain vulnerable. Field and mobile OT assets compound this problem.Zscaler’s&nbsp;Zero Trust Branch enables agentless discovery &amp; classification for headless devices, including IoT and OT assets. This helps security teams identify their OT estate, and take appropriate steps to secure it. Full visibility into east-west as well as north-south communication ensures an accurate understanding of communication patterns and cyber exposure.&nbsp;Zscaler Cellular extends this visibility by adding location and usage information enabling effective governance of the entire IoT/OT footprint. Design For Containment, Not Just PreventionPatching known vulnerabilities remains essential. But the ground reality in OT environments mandates a different architectural approach.The refrigeration incidents underscore a more durable principle: OT resilience depends on containing inevitable failures and compromises. Zero trust provides that containment by making each connection explicit, each device constrained, and each site less capable of becoming a launch point for a broader attack.Learn more about Zscaler IoT/OT solutions&nbsp;here and contact us for a demo.]]></description>
            <dc:creator>Ameet Naik (Senior Director, Product Marketing)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Defending Federal Internal Applications in the Age of Frontier AI: Lessons from PHP2Shell]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/defending-federal-internal-applications-age-frontier-ai-lessons-php2shell</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/defending-federal-internal-applications-age-frontier-ai-lessons-php2shell</guid>
            <pubDate>Tue, 03 Nov 2026 01:13:31 GMT</pubDate>
            <description><![CDATA[On October 21, 2026, two critical memory safety flaws in PHP, tracked as&nbsp;CVE-2026-109618 and&nbsp;CVE-2026-109619 and collectively known as&nbsp;PHP2Shell (CVSS v4.0: 9.2 for each) were disclosed after sitting dormant in core PHP code since at least 2012 (affected versions span PHP 5.4 through 8.5). These vulnerabilities allow an unauthenticated attacker to execute shell commands directly on a vulnerable server. News of the flaws leaked online on October 20, two days before the planned release. PHP responded that evening with an advance warning and moved the fix up a day. Before the fix arrived, government portals and organizations worldwide took services offline as a precaution, many following national cybersecurity guidance.For Federal Chief Information Officers (CIOs) and Chief Information Security Officers (CISOs), PHP2Shell is a critical inflection point. Signs of the memory problem behind one flaw surfaced in 2024, during follow-up work on PHP’s first external security audit in years. A fix stalled for months. PHP’s small security team weighed competing approaches with hard trade-offs, and no concrete path to exploitation had been found. In 2026, independent researchers using frontier AI models found that path, built working exploits, and reported them through coordinated disclosure.Traditional federal vulnerability management and Authority to Operate (ATO) patching workflows were designed for human timelines. PHP2Shell shows how little time that leaves: exploitation attempts were observed before the patches shipped, CISA added both CVEs to its Known Exploited Vulnerabilities (KEV) catalog five days after the fix, and civilian agencies were given three days to remediate and required to perform forensic triage to check whether systems had already been compromised under CISA Binding Operational Directive (BOD) 26-04. Why Internal Federal Environments Are Uniquely ExposedA common misconception is that web application vulnerabilities only threaten public-facing citizen portals. In reality, internal agency networks harbor vast quantities of hidden PHP instances that cannot be patched overnight.Exposure VectorFederal Environment ChallengeOperational ImpactEnd-of-Life (EoL) &amp; Legacy SystemsPHP released fixed versions only for currently supported branches (PHP 8.2–8.5). For legacy applications on end-of-life branches (such as PHP 7.4, 8.0, and 8.1), PHP published the code fix, and older branches back to PHP 5.4 received no fix from PHP but are also affected, so agencies depend on distribution or vendor backports or on rebuilding from source themselves.Agencies running mission-critical legacy workloads cannot simply apply an update without breaking core dependencies or requiring extensive regression testing.Embedded Appliances ("Black Boxes")Virtual appliances, VoIP/PBX systems, storage controllers, and branch firewalls often bundle PHP under the hood to serve browser-based admin consoles. Vendor advisories and trackers, such as the CISA Known Exploited Vulnerabilities Catalog, already list network, storage, and security products among those affected or under investigation.Updating underlying components independently is often impossible or requires waiting for the vendor to ship a fix.Broad Network AccessTraditional VPNs and flat internal networks grant authenticated employees, contractors, and support personnel broad network-level reachability.A single phished credential or compromised contractor laptop allows an adversary to scan internal IP spaces and compromise unpatched management interfaces.&nbsp; Practical Guidance: A Four-Step Zero Trust Framework for Federal AgenciesPatching underlying code remains mandatory to permanently remediate CVEs. However, when patches cannot be tested and deployed everywhere in time, or at all for embedded and end-of-life systems, agencies need architectural controls that reduce exposure and limit the blast radius while remediation is completed. These controls are compensating, not a substitute for patching: PHP's maintainers state that updating is the only complete fix.Federal leaders can operationalize a four-step, vendor-agnostic Zero Trust strategy:&nbsp;Hide, Segment, Shield, and Deceive to reduce risk during emergency remediation windows.&nbsp;Strategic PillarPractical Guidance for Federal AgenciesMission &amp; Security Benefit1. HIDE: Eliminate the Public Attack SurfaceRemove internal applications, database portals, staging environments, and admin consoles from public IP space, and replace VPN-based access to them. Place applications behind identity-aware proxies using outbound-only connections so there are no inbound open ports.External scanners and automated exploit tooling sweeping the internet cannot attack what they cannot see, reducing the need for emergency shutdowns.2. SEGMENT: Enforce User-to-Application AccessReplace network-level access with strict, identity-centric microsegmentation based on actual access patterns. Connect authorized users and contractors only to the specific applications required for their duties rather than placing them on the agency network.Sharply limits lateral movement. If an adversary compromises a contractor account, they have no network path to probe neighboring servers or appliance consoles. Applications the account is entitled to reach remain reachable, so this control should be paired with Shield.3. SHIELD: Deploy Inline Virtual PatchingImplement continuous runtime inspection and inline application protection at the access layer. Map which internal applications are actively running vulnerable software versions and apply targeted virtual patches inline only where needed.Blocks known exploit payloads once protections cover them from compromised insider accounts or allowed connections while limiting false positives on unrelated systems.4. DECEIVE: Trap Automated ReconnaissanceDeploy high-fidelity decoy environments—such as synthetic admin portals, decoy database interfaces, and planted lure credentials—along common internal exploration paths.Turns the attacker's reconnaissance against them, whether human- or tool-driven. Because legitimate personnel have no reason to touch decoys, any interaction provides an immediate, high-confidence alert to isolate the compromised session. Deception detects intrusions; it does not prevent exploitation of a vulnerable application.&nbsp; Key Takeaways for Federal Executive LeadershipAs frontier AI accelerates the discovery of long-dormant vulnerabilities in foundational open-source software, the window between public disclosure and mass weaponization has shrunk dramatically. With PHP2Shell, at least one exploitation attempt appeared four days before public disclosure, by means still unknown. After word of the flaws leaked, more attempts followed before patches were even shipped, and exploitation was widespread within hours of the fix. Federal agencies cannot rely solely on emergency patching sprints to protect sensitive data and mission continuity.The current cycle of waiting for a KEV listing and launching an emergency patching sprint was built for a world where critical, actively exploited flaws in core software arrived occasionally, driven by human actors. As AI helps researchers and adversaries find these flaws faster, short-deadline KEV additions will arrive more often, and each one pulls the same operations teams into the same fire drill. That approach does not scale, and for embedded appliances and end-of-life systems, a deadline often cannot be met by patching at all. Agencies need a standing architecture that reduces exposure before the next disclosure rather than after it. That is the role of the Hide, Segment, Shield, and Deceive framework.By removing private applications from public visibility, enforcing strict least-privilege user-to-application segmentation, applying targeted inline virtual patches, and deploying active deception, CISOs and CIOs can buy their operations teams the time needed to test and deploy permanent patches methodically, while meeting federal remediation deadlines and reducing risk for embedded and end-of-life systems that depend on vendor fixes, isolation, or removal.]]></description>
            <dc:creator>Jose Arvelo Negron (Manager, Sales Engineer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Water Sector Under Attack:  Defending our Drinking Water]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/water-sector-under-attack-defending-our-drinking-water</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/water-sector-under-attack-defending-our-drinking-water</guid>
            <pubDate>Fri, 30 Oct 2026 19:00:33 GMT</pubDate>
            <description><![CDATA[On July 20, 2026, CISA issued an alert that malicious actors were actively targeting Water and Wastewater systems. The alert coincided with media reports that active attacks against water treatment utilities had been detected and responded to in several U.S. states. Fortunately, the attacks were stymied before any people were harmed. The news is unsettling and requires urgent and sustained effort to ensure cybersecurity defenses for the water sector are rock-solid.As we go about our daily lives, we take basic things for granted. We turn on the tap, we fill up a glass of water and we drink it with barely a second thought. We know it's safe to drink because people in the water and wastewater industry are doing the hard work for us. We don't need to know about pH or chlorine levels or backflow prevention, we only need to know how to work a faucet. Similarly, when we engage with water utilities to help them harden their cyber defenses we need to bring solutions that fit the needs of water operators instead of asking them to conform to standard IT expectations. Their widespread use of OT and IoT requires an approach that can meet them where they are.At Zscaler, we're focused on delivering cybersecurity solutions for water and wastewater operators that can be rapidly and effectively deployed regardless of network topology or current level of capability. Defending against malicious actors requires a modern approach to cybersecurity based on Zero Trust security principles. This is especially true as threat actors increasingly use AI to automate reconnaissance, scale attacks, and exploit vulnerabilities faster than legacy defenses can respond. Our Zero Trust approach is informed by the scale of what Zscaler sees globally across enterprise, public sector, and critical infrastructure environments. With visibility into a vast volume of cyber activity around the world, Zscaler is able to identify emerging threats, attacker behaviors, and new techniques early, and apply those insights to better protect essential services. Because our solutions are cloud-delivered and designed to work alongside existing infrastructure, water utilities can strengthen their security posture without costly rip-and-replace projects or the burden of managing additional hardware.Zscaler is working with the water sector to make an immediate impact by helping water operators to:Reduce the External Attack Surface Zscaler's Zero Trust Branch (ZTB) solution greatly reduces the attack surface of the organization, which immediately limits exposure to external attacks. ZTB puts the water utility's internet presence into stealth mode and leverages connectivity to the Zscaler Zero Trust Exchange to secure the entity's communications.Provide Secure Internet Access Zscaler Internet Access (ZIA) is a cloud-native gateway that acts as a secure, policy-driven intermediary between users and the internet. It replaces legacy hardware like firewalls and VPNs with a globally distributed proxy network, inspecting all traffic inline to prevent threats, malware, and data loss. For water utilities, this means fewer boxes to buy, rack, and maintain, and a faster path to stronger security.Enable Microsegmentation ZTB enables microsegmentation of the entity's internal network without requiring massive network changes or firewall sprawl that would introduce complexity. This is especially valuable for resource-constrained water utilities because our approach does not require agents to be installed on the many OT and IoT devices already in use.Provide Secure Privileged Remote Access The Zero Trust Exchange allows water utilities to ensure trustworthy and secure communications and internet connectivity. Importantly, ZTB facilitates secure Privileged Remote Access to internal systems, ensuring that water utilities can continue to work with water industry partners in support of their infrastructure without opening the door to attackers.Identify Attacks Earlier and Gain Visibility into Threat Actor TTPs Zscaler Deception places lightweight sensors within the water utility network that detect lateral movement and network reconnaissance. Deception can be deployed on endpoints running the Zscaler Client Connector, giving operators early warning of attacker activity without adding complexity to the environment.Protecting access to safe drinking water needs a collective effort between water utilities, local government, policy makers at the State and Federal level, State agencies, emergency management and technology services, and technology companies such as Zscaler.Learn more: Download our&nbsp;Zero Trust Water Operations Solution Brief for a deeper look at how Zscaler helps secure water and wastewater systems.See us in person: Zscaler will be at the&nbsp;Billington Critical Infrastructure Cybersecurity Summit in San Antonio, TX, November 17-18, 2026. Visit us at Booth 213 - stop by and let's talk about how Zero Trust can work for your environment.]]></description>
            <dc:creator>Adam Ford (Chief Technology Officer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[What’s New in GovCloud:  October 2026 Zscaler Product Updates]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-govcloud-october-2026-zscaler-product-updates</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-govcloud-october-2026-zscaler-product-updates</guid>
            <pubDate>Fri, 30 Oct 2026 15:53:39 GMT</pubDate>
            <description><![CDATA[Whether you're deep in audit prep, working through year-end priorities, or just trying to keep your security stack current, finding time to review every release is a challenge. Here is a curated roundup of notable Zscaler GovCloud updates from October, with quick context and scan-friendly takeaways you can share across security, network, and operations teams. Highlights include Zscaler Client Connector 5.0 for Windows, expanded Endpoint DLP capabilities with Device Control for portable devices and real-time PDF OCR, Real User Monitoring in ZDX, AI transcript and meeting summary scanning for Zoom tenants in ZIA, and IPSec tunnel stability improvements for Zero Trust Branch. Zscaler Internet Access (ZIA)Zscaler Internet Access (ZIA) is Zscaler's secure internet and SaaS access service, providing policy-based protection and visibility for users wherever they work. For many federal environments, ZIA is central to enforcing acceptable use, protecting sensitive data, and maintaining consistent security controls across a distributed workforce.This month's ZIA updates significantly expand Endpoint DLP capabilities, address a File Type Control security issue, and introduce AI-generated content scanning for Zoom tenants.HighlightsEndpoint DLP 26.08 Enhancements and Fixes: This release expands Device Control to portable devices (such as smartphones and cameras), CD/DVD, and floppy disk channels (floppy is Windows only). It adds DLP Intent visibility into suspicious user behavior, visibility into sensitive files entering endpoints, a refreshed User Investigation experience, and CSV export for Application Inventory. IDM can now index all files in a folder instead of being limited to 20, and OCR now supports PDFs in real time for all channels except Application File Access.&nbsp;(FedRAMP Moderate and High)Security Fixes: The File Type Control evaluation rule no longer allows a potential evasion of File Type Control policies (CVE-2026-25684).&nbsp;(FedRAMP Moderate and High)Support for AI Transcript and Summary for a Zoom Tenant: Zoom tenants onboarded with Data at Rest Scanning DLP and Malware can now scan two additional content types: AI transcripts and AI meeting summaries. AI Companion must be enabled on the Zoom account, and existing tenants need additional scopes, webhook subscriptions, and reauthorization.&nbsp;(FedRAMP Moderate and High)For full release notes:&nbsp;https://help.zscaler.us/zia/release-upgrade-summary-2026 Zscaler Private Access (ZPA)Zscaler Private Access (ZPA) provides secure, zero trust connectivity between users and private applications without exposing those applications to the internet. It helps organizations reduce attack surface while improving access experience, which is especially important for distributed users, mission partners, and hybrid work environments common across federal agencies.This month's ZPA updates continue the rollout of AI-powered application segment features and deliver a new App Connector release with stability improvements.HighlightsAI Recommendations for Application Segments (Limited Availability): AI-powered recommendations analyze user logs and suggest application segments based on application similarity or user behavior, helping teams discover and create new segments automatically and find missing applications for existing segments.&nbsp;(FedRAMP Moderate and High)Application Segments Usage (Limited Availability): Admins can view or download Application Segments Usage reports from the Zscaler Admin Console to see which application segments are actively used and which user groups are accessing them. Available only to customers with the Segmentation add-on.&nbsp;(FedRAMP Moderate and High)App Connector Version 26.55.1: An update for App Connector that includes bug fixes, optimizations, and version enhancements. App Connectors update based on the software update schedule configured per App Connector group.&nbsp;(FedRAMP Moderate and High)For full release notes:&nbsp;https://help.zscaler.us/zpa/release-upgrade-summary-2026 Zscaler Digital Experience (ZDX)Zscaler Digital Experience (ZDX) provides visibility into end-user device health, application performance, and network path quality. For federal teams managing distributed endpoints across agencies and field locations, ZDX helps identify and resolve experience issues before they impact productivity or mission delivery.This month's ZDX update introduces Real User Monitoring, a significant addition that brings browser-level visibility into application performance.HighlightsReal User Monitoring: Real User Monitoring captures and analyzes user interactions with applications through their web browsers to create comprehensive visibility into an application's digital experience. Teams can use it to identify bottlenecks users encounter while accessing configured applications through their browsers, enabling faster troubleshooting and more informed performance optimization.&nbsp;(FedRAMP Moderate)For full release notes:&nbsp;https://help.zscaler.us/zdx/release-upgrade-summary-2026 Zscaler Client ConnectorZscaler Client Connector is the unified endpoint agent that steers traffic to ZIA, ZPA, and ZDX services. It ensures consistent policy enforcement regardless of where users connect from, which is critical for agencies supporting remote and hybrid workforces.This month brings a major milestone with Client Connector 5.0 for Windows, introducing a modernized user experience, new connectivity options, and expanded platform support.HighlightsZscaler Client Connector 5.0 for Windows (Limited Availability): This release brings modernized, plain-language status and guidance in the app (requires Windows 11 24H2 build 26100 or later). Key additions include Wi-Fi Name (SSID) as a trusted network criterion, TLS 1.3 support with automatic fallback to TLS 1.2, and machine tunnels in Business Continuity mode so devices can stay connected to Private Access apps when the Zscaler cloud is unreachable. The release also adds Endpoint DLP on ARM-based Windows machines (with ZDP Module 26.08 and later) and includes a fix for memory corruption in the Private Access certificate timeout handler (CVE-2026-25687). Note: this version does not support Windows 32-bit.For full release notes:&nbsp;https://help.zscaler.us/client-connector/release-upgrade-summary-2026 Zero Trust BranchZscaler Zero Trust Branch helps modernize branch security and connectivity by bringing zero trust principles to branch offices, remote sites, and OT/IoT environments, reducing reliance on legacy appliances while maintaining consistent policy enforcement.This month's update improves IPSec tunnel stability and adds new administrative access and UI simplifications.HighlightsZero Trust Branch 8.2.1-P1 (FD105) (Limited Availability): Improves the stability of IPSec tunnels between the Zero Trust Branch appliance and Internet &amp; SaaS (ZIA) to prevent intermittent disconnections. Adds an Appliance Admin Console page that gives administrators terminal access to appliances for troubleshooting and simplifies the Add Site UI for ebond0 WAN interface selection. Resolved issues include a failover fix when the primary WAN nexthop is unreachable, a fix so deleting a BGP session no longer removes same-named sessions at other sites, and the ability to specify a WAN VLAN ID on the primary WAN during site creation.&nbsp;(FedRAMP Moderate and High)For full release notes:&nbsp;https://help.zscaler.us/zero-trust-branch/release-upgrade-summary-202 Cloud ConnectorZscaler Cloud Connector helps extend Zscaler policy enforcement and traffic forwarding for workloads running in public cloud environments. It supports organizations that need consistent security controls for cloud-hosted services while enabling architectures aligned to modernization initiatives.This month's Cloud Connector updates add AWS account tagging for cross-account deployments and new VDI provisioning permissions.HighlightsSupport for Amazon Web Services Account Tagging (Limited Availability): Organizations can now leverage user-defined tags across AWS accounts in cross-account deployments with workload communications. This gives teams more flexibility in organizing and managing multi-account cloud environments.&nbsp;(FedRAMP Moderate)Support for VDI Provisioning Permission: Zscaler Cloud Connector now supports the VDI Provisioning permission when adding admin roles, with Full, View Only, or None options. This provides more granular role-based access control for virtual desktop infrastructure management.&nbsp;(FedRAMP Moderate and High)For full release notes:&nbsp;https://help.zscaler.us/cloud-branch-connector/release-upgrade-summary-2026 ConclusionWant the full details? Use the links above to review the complete release summaries, and check back next month for the next GovCloud update roundup.Zscaler continues to invest in a robust GovCloud roadmap and remains committed to supporting the unique security, compliance, and operational requirements of the federal market. We'll keep delivering enhancements that help agencies and federal partners strengthen resilience, simplify operations, and advance mission success.]]></description>
            <dc:creator>Jose Arvelo Negron (Manager, Sales Engineer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Canada’s Emerging CPCSC Program Is Here: How Zscaler Helps Canadian Defence Suppliers Achieve Compliance]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/canada-s-emerging-cpcsc-program-here-how-zscaler-helps-canadian-defence</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/canada-s-emerging-cpcsc-program-here-how-zscaler-helps-canadian-defence</guid>
            <pubDate>Thu, 29 Oct 2026 16:28:23 GMT</pubDate>
            <description><![CDATA[Canada’s new defence cyber certification is live. Here’s what it asks of suppliers, and how Zscaler helps them achieve compliance.On April 1, 2026, Canada’s Public Services and Procurement Canada (PSPC) launched Level 1 of the&nbsp;Canadian Program for Cyber Security Certification (CPCSC). For companies supporting&nbsp; Canada’s defence supply chain, cybersecurity has transitioned from being a best practice to a prerequisite for conducting business with Canada’s Department of National Defence (DND).The CPCSC is Canada’s counterpart to the U.S. Cybersecurity Maturity Model Certification (CMMC). It safeguards sensitive, unclassified "specified information" possessed by suppliers and is based on ITSP.10.171, the standard from the Canadian Centre for Cyber Security, which aligns with NIST SP 800-171.&nbsp; What CPCSC requiresThe program has three levels, phased in over the next two years:Level &nbsp;AssessmentTimingLevel 1Annual self-assessment against 13 foundational controls, using a Government of Canada online toolAvailable since April 1, 2026; in select contracts from summer 2026Level 2Third-party assessment by a body accredited by the Standards Council of Canada, every three years, plus annual affirmationSpring 2027; phased into contracts April 2027-March 2028Level 3Assessment by the Government of Canada, every three years, with enhanced requirements aligned to NIST SP 800-172Phased into the highest-risk contracts from 2027An important detail to keep in mind!&nbsp;The certification is verified upon contract award, not during the bidding process. This means a supplier could potentially win a bid but still be deemed ineligible.&nbsp; What Level 1 actually asks forThe Level 1 asks suppliers to self-attest to 13 foundational controls which are drawn from ITSP.10.171. This is the standard that also underpins Levels 2 and 3. These controls fall into six families:Access control: account management, access enforcement, use of external systems, and control of publicly accessible content.Identification and authentication: multifactor authentication, custom user identification and authentication, device identification and authentication.Media protection: sanitizing or destroying media before disposal or reuse.Physical protection: physical access authorizations and physical access control.&nbsp;System and communication protection: boundary protection.&nbsp;&nbsp;System and information integrity: flaw remediation and malicious code protection.&nbsp;&nbsp;These are the baseline requirements. CPCSC positions Level 1 as lower risk work requiring the controls to be self assessed, rather than verified independently by a third party. Because of this flexibility and ease of path to compliance, it also offers the clearest starting point for building toward higher levels. Why the easiest path to Level 1 isn’t enoughIn times of new requirements, most suppliers look for the quickest way to check the box. Many suppliers can do this with technology they already own in their inventory: a firewall at the perimeter, a VPN for remote access, antivirus software, and multifactor authentication on the landing page. For a self-assessment, this reads as compliant. While each of these controls is technically compliant and satisfied, bad actors are skilled at exploiting exactly the gaps that remain.&nbsp;Flat networks. A VPN connects remote engineers and subcontractors to the whole network, not just the systems they need. One stolen credential becomes a path for lateral movement to vulnerable information.&nbsp;Exposed edge devices. Internet-facing VPN concentrators and firewalls are among the most frequently exploited systems in Cyber Centre alerts.Unmanaged devices. Partners and contractors reach sensitive systems from laptops the supplier doesn’t control.Point-in-time evidence. Even where controls exist, pulling together proof for an assessor takes weeks. A self-assessment captures how controls were configured on one day; it says little about whether they were consistently enforced for the rest of the year.&nbsp;Why stronger controls now pay off at Levels 2 and 3These check boxes don’t just leave risks in place; they create rework. They are shortcuts. Level 2 is a third-party independent assessment against the broad ITSP. 10.171 requirement set. Auditors will look for controls that are enforced consistently and are defensible, such as least privilege, session controls, audit logs, and protection of data in transit.Level 3 includes enhanced requirements aligned to NIST 800-171 that protect against bad actors, including stronger isolation of systems that hold specified information and continuous monitoring. A perimeter and VPN design built to only pass Level 1, more often than not, has to be rebuilt to meet them.&nbsp;Controls built on zero trust principles take the opposite approach; access is granted per application based on identity, device posture, and context. Applications have no exposed attack surface, traffic is inspected inline, and every decision is logged centrally. Those same controls satisfy Level 1 today and really become the foundation that Level 2 and Level 3 assessments build on. The goal isn’t just to pass Level 1, but to meet it once, in a way you won’t have to undo. This approach saves both cost and time down the road. How Zscaler supports CPCSCNo product is “CPCSC certified.” Only the supplier is assessed. The platform must be capable of enforcing controls and providing the necessary evidence for the self-assessment and upcoming Level 2 evaluation. Zscaler’s Zero Trust Exchange directly covers&nbsp;10 out of the&nbsp;13 Level 1 controls and also backs up five additional controls.&nbsp; As organizations consider both Level 1 and higher levels of maturity, moving to a true zero trust technology foundation will provide adaptable controls that position organizations to demonstrate higher levels of compliance.Level 1 controlExamples of How Zscaler Contributes to CPCSC Level 1Access Enforcement&nbsp;Zscaler performs as a Zero Trust Policy Enforcement Point that connects users to specific applications, never to the network, based on identity and aggregated policy.Boundary Protection&nbsp;Applications sit behind the Zero Trust Exchange with no inbound listening ports, removing the exposed VPN from the attack surface.Malicious Code Protection&nbsp;Zscaler Internet Access (ZIA) inspects traffic inline, including encrypted traffic, with advanced threat protection and cloud sandboxing.Device Identification &amp; Authentication&nbsp;Zscaler has over 40 device posture checks that it can verify before granting access to the supplier’s resources.Use of External Systems&nbsp;Posture policies and browser isolation let unmanaged devices reach approved apps without data landing on the device.Account Management, Identification, and MFA&nbsp;Integration with the supplier’s identity provider enforces authentication and MFA before any application is reachable.Publicly Accessible Content&nbsp;Inline data loss prevention stops specified information from being posted to public sites.Flaw Remediation&nbsp;Zscaler provides value for flaw remediation by blocking exploit delivery paths, restricting access based on device posture, and reducing network exposure.The remaining three Level 1 controls, e.g. media sanitization and two physical-security controls, stay with the supplier.One platform, Multiple Compliance Programs, Endless Supportability&nbsp;Since ITSP.10.171 mirrors NIST SP 800-171, DND suppliers can leverage the same Zero Trust Architecture to monitor, enforce, and log access to support their CPCSC program, along with other Canadian Public Sector requirements. This reduces investment and maintenance costs and enables suppliers to set up controls once and show evidence for multiple programs, instead of managing multiple technologies to secure multiple programs.&nbsp;Ready for Level 2, on Day OneLevel 1 leverages a self-assessment, but Level 2 will require more formal assessment.&nbsp; As assessors arrive in 2027, suppliers will need to show how controls are consistently enforced, not just configured. Centralized management, enforcement policy, and logging across every user, device, and application provide suppliers with a single platform with evidence built in. A robust Zero Trust Architecture will ease this transition. Getting startedIdentify which current or upcoming DND contracts involve specified information.Map how remote users, subcontractors, and partners reach systems that hold specified information today.Replace network-level access with Zero Trust Network Access for those users first.Align your platform configuration with the required CPCSC evidence, so that one set of controls serves more than one program.CPCSC requirements can appear in defence contracts this year. The suppliers who start now will treat Level 2 as a formality. To learn how Zscaler can help,&nbsp;contact our team or visit the&nbsp;Zscaler Compliance Center.ReferencesPSPC – Canadian Program for Cyber Security Certification: Level 1 (April 2026)Canadian Centre for Cyber SecurityPilotcore – CPCSC for Canadian Defence Suppliers]]></description>
            <dc:creator>Aaron Shortridge (Field Compliance Program Manager)</dc:creator>
        </item>
        <item>
            <title><![CDATA[What PHP2Shell Teaches Us About Defending Private Apps in the Age of Frontier AI]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/what-php2shell-teaches-us-about-defending-private-apps-age-frontier-ai</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/what-php2shell-teaches-us-about-defending-private-apps-age-frontier-ai</guid>
            <pubDate>Tue, 27 Oct 2026 15:00:00 GMT</pubDate>
            <description><![CDATA[What PHP2Shell Teaches Us About Defending Private Apps in the Age of Frontier AIOn October 20, 2026,&nbsp;two critical memory flaws in PHP were disclosed. Tracked as&nbsp;CVE-2026-109618 and&nbsp;CVE-2026-109619 and dubbed&nbsp;PHP2Shell, these vulnerabilities carry a 9.2 CVSS score from PHP’s maintainers (and a flat 10.0 from researchers at watchTowr) because they let an unauthenticated attacker run shell commands directly on a vulnerable server. At the time of disclosure, 70% of the web’s server-side applications were open to remote takeover.Within hours of disclosure, government portals, ecommerce sites, and other organizations around the world took themselves offline to avoid getting hit.Like other recent vulnerabilities, PHP2Shell draws attention to the shortcomings of enterprise security in the changing threat landscape: our patching workflows were built for human timelines, while attackers are now operating at the speed of frontier AI.Zscaler&nbsp;ThreatLabz report showing the risk score and vulnerabilities identified for PHP2Shell&nbsp;Here is a look at why PHP2Shell moved so fast, why internal enterprise apps and databases are just as exposed as public websites, and how&nbsp;Zscaler Private Access (ZPA) with&nbsp;Autonomous Application Shield gives your team breathing room to patch without shutting down the business.&nbsp; &nbsp;When Frontier AI Finds Vulnerabilities Humans Wrote OffOne of the most striking facts about PHP2Shell is how long the underlying bugs sat in plain sight. The memory safety flaws affected PHP versions all the way back to PHP 5.4, which shipped in 2012. A PHP core developer actually ran across the out-of-memory error behind one of the bugs during a 2024 audit. At the time, the team couldn't agree on a fix, and nobody believed a working exploit was practically feasible, so the issue was set aside.Two years later, two separate teams using frontier AI models were able to reason through PHP’s complex memory management and prove the bug could be reliably exploited.While defenders found PHP2Shell first, the same AI capabilities have permanently compressed the window between disclosure and mass exploitation. All the grunt work that used to slow attackers down—reverse-engineering patches, mapping out target environments, and testing exploit variations—can now be automated in minutes.Look at the timeline that unfolded in October:Four days before public disclosure, Amazon Threat Intelligence spotted early PHP2Shell exploitation attempts in its honeypot telemetry on October 17.Before the official embargo even lifted, a software vendor pushed patched packages early. Attackers immediately diffed the code changes to see what was fixed and started circulating working proof-of-concept exploits.Within minutes of the official patch release on October 21, mass automated scanning was underway across the internet, forcing agencies like the US NSA, CERT-EU, and the UK’s NCSC to warn organizations to either update immediately or take their servers offline.We now live in an era where the time-to-exploit is effectively negative. Attackers can weaponize a flaw in minutes, whereas enterprise IT still has to deal with change freezes, dependency checks, regression testing, and maintenance windows. If your entire defense rests on winning a footrace to patch every server first, the odds are stacked against you.PHP2Shell Is an Internal Enterprise Problem, TooPHP2Shell is not only a problem for marketing websites running WordPress, Drupal, or Joomla. In practice, almost every large enterprise has a massive, often undocumented footprint of PHP running behind the scenes on its internal network.&nbsp;For over twenty years, PHP has been the default language for internal web interfaces, database utilities, and bundled infrastructure appliances. Even if your developers never write a line of PHP, it is likely sitting inside your environment right now:Network monitoring and infrastructure tools: Many of the platforms sitting at the heart of the enterprise NOC—including&nbsp;Zabbix,&nbsp;Nagios XI,&nbsp;LibreNMS, and&nbsp;Cacti—use PHP to power their web frontends. Because these systems monitor the entire environment, they are high-value targets often holding SNMP community strings, API tokens, and administrative credentials.Internal IT and business systems: Popular IP address management (IPAM) tools like&nbsp;phpIPAM, IT asset and service desk platforms like&nbsp;Snipe-IT and&nbsp;GLPI, internal wikis like&nbsp;MediaWiki, and self-hosted file sharing platforms like&nbsp;Nextcloud all run on PHP.Database utilities and internal CRUD apps: Legacy instances of&nbsp;phpMyAdmin or single-file utilities like&nbsp;Adminer frequently linger in dev/test subnets and staging environments, alongside custom internal admin portals built on PHP frameworks like&nbsp;Laravel and&nbsp;Symfony that sit directly in front of sensitive SQL databases.Embedded web consoles and virtual appliances: Dozens of virtual appliances, VoIP/PBX systems (like&nbsp;FreePBX), web control panels (cPanel,&nbsp;Plesk), and edge devices (such as&nbsp;pfSense and&nbsp;OPNsense in branch or lab environments) bundle PHP under the hood just to serve their browser-based administration consoles.Making matters worse, the official binary patches for PHP2Shell only cover active versions (PHP 8.2 through 8.5). Older versions like PHP 7.4, 8.0, and 8.1 are end-of-life. Countless legacy internal apps and "black-box" vendor appliances can't be updated without breaking dependencies or voiding vendor support.If an attacker gets a foothold on your network—whether through a phished credential, a third-party contractor's laptop, or an exposed VPN—their next move is to scan your internal IP space. An unpatched phpMyAdmin instance or an old appliance interface is all they need to trigger PHP2Shell and take over the underlying host.Zscaler’s Four-Step Security Framework: Hide, Segment, Shield, DeceivePatching PHP should be a top priority for your security team. Updating the underlying code is the only way to permanently close CVE-2026-109618 and CVE-2026-109619.But how do you protect the business during the days or weeks it takes to track down every PHP instance, test the updates, and roll them out across thousands of workloads? And how do you put in place a security architecture that protects you from whatever new CVE is disclosed next week, and the week after that?&nbsp;A Zero Trust architecture dramatically reduces exposure of your critical applications and lets you put immediate protective layers around vulnerable apps so your teams can patch methodically.With Zscaler, that protection happens in four steps:1. HIDE: Make Internal Apps Invisible with Zscaler Private Access (ZPA)Why did so many organizations have to shut down their web services during the PHP2Shell rollout? Because their servers were sitting on public IP addresses where automated scanners could find and exploit them. Many enterprises inadvertently do the exact same thing with internal tools—exposing database portals, staging environments, or admin consoles through split-tunnel VPNs, firewall port forwards, or public cloud IPs.Zscaler Private Access (ZPA) takes those applications off the public internet completely. Applications sit behind lightweight App Connectors that only establish outbound connections to the Zscaler cloud. There are no inbound open ports and no public IPs to scan. If an outside attacker or an AI botnet sweeps the internet looking for vulnerable PHP servers, your private applications simply do not exist to them. They can’t attack what they can’t see.2. SEGMENT: Shrink Internal Exposure with Autonomous User-to-App SegmentationTaking apps off the internet stops external scans, but you still have employees, contractors, and vendors who need to get work done. In a traditional network—or even in a ZPA setup that relies on broad wildcard application segments—anyone who authenticates can often reach way more applications than their job requires. If an attacker compromises one user's device, they can immediately start probing neighboring servers for PHP2Shell.Autonomous User-to-App Segmentation uses AI to analyze actual access patterns and lock down reachability to the bare minimum. Instead of putting users on the network, ZPA connects specific users only to the specific applications they need. A marketing contractor has zero path to reach an engineering database portal or an appliance management console. Even if an attacker compromises an account, they have nowhere to move laterally.3. SHIELD: Stop the Exploit Inline with Autonomous App ShieldFinally, what about the applications that must remain reachable to authorized users while they are still waiting on a patch? If a compromised employee account or a malicious insider has legitimate access to an unpatched PHP app, hiding and segmenting won't stop them from sending a malicious payload down an allowed connection.That is the exact gap&nbsp;Zscaler Autonomous App Shield was built to close. Built directly into the ZPA platform, Autonomous App Shield provides continuous, inline protection for private applications. It uses AI to find and block exploits at the app connector, providing virtual patching long before you can put in a real patch:&nbsp;It continuously maps your application risk. Rather than relying on a point-in-time vulnerability scan from last month, ZPA App Connectors continuously inspect private applications and their runtime characteristics. You get a real-time view of which internal apps are actually running vulnerable versions of PHP so you know exactly where you are exposed and can prioritize remediation accordingly.It applies protections only where they are needed. Competitors push the same signature to every customer, applying protections regardless of whether a vulnerable application actually exists in that environment. That creates false positives, blocking legitimate traffic on systems that don't even run PHP, and false negatives, where the right signature never gets applied because signature limits are exhausted by rules that didn't need to be there in the first place. Zscaler flips this entirely: because we scan first, we only apply a virtual patch to an application that is actually running the vulnerable software. No waste. No unnecessary rules. No risk of cascading policy conflicts.It tailors protection to each individual app. The Zscaler cloud evaluates how each specific application behaves and applies only the virtual patches and inline controls that app actually needs.It adapts automatically as threats and code change. Drawing on threat intelligence from across the Zscaler cloud,&nbsp;alongside our work with IBM and Red Hat’s Project Lightwell, Autonomous App Shield updates its inline defenses as new exploit variations appear in the wild. When your DevOps team ships a code change or applies a patch, the protection adjusts automatically without a manual policy review.With PHP2Shell, Zscaler’s ThreatLabz threat research team pushed mitigating controls through our automated CI/CD pipeline into production before the industry had even agreed on a proper remediation. Customers using ZPA App Protection were protected before most vendors had written a single signature.4. DECEIVE: Trap AI-Driven Recon with High-Fidelity DeceptionWhat makes frontier AI so dangerous in the hands of an attacker is its ability to perform&nbsp;multi-step reasoning. Unlike old-school scripts that blindly fire a single exploit and fail, an AI agent methodically explores its environment: enumerating accessible hosts, inspecting HTTP headers, testing credentials, probing unpatched endpoints like PHP portals, and chaining small findings together to plan its next move.Ironically, that relentless curiosity is also AI’s biggest weakness when you introduce&nbsp;Zscaler Deception.By placing realistic, high-fidelity decoys—such as fake PHP admin portals, decoy database interfaces, and planted lure credentials—directly along the paths an attacker would explore, you turn the AI’s multi-step reasoning against itself. An autonomous agent cannot tell the difference between a real internal phpMyAdmin or Zabbix instance and a Zscaler decoy. Because the AI is programmed to systematically investigate and test every promising lead it discovers, it is uniquely prone to interacting with decoys.And because legitimate users have zero business touching a decoy application, any interaction gives your security team an immediate, high-confidence alert with virtually zero false positives. While traditional detection tools struggle to separate stealthy AI reconnaissance from normal user traffic, a single probe against a decoy exposes the compromised user session right away and lets ZPA automatically quarantine the attacker.&nbsp; &nbsp;Getting Ahead of the Next AI-Discovered FlawPHP2Shell is a preview of what application security looks like from here on out. As frontier AI models get better at auditing decades-old codebases, we are going to see more foundational vulnerabilities surface—and we are going to see attackers weaponize them faster than human teams can push updates.Patching will always be necessary, but it shouldn't be your only line of defense. By hiding your private applications with&nbsp;ZPA, restricting internal reachability with&nbsp;Autonomous User-to-App Segmentation, and blocking exploit attempts inline with&nbsp;Autonomous App Shield, you take the panic out of the remediation window. Your applications stay online, your data stays protected, and your teams can patch on their own schedule—not the attacker’s.To see how Zscaler’s Lateral Threat Bundle can protect your private applications against AI-accelerated threats,&nbsp;reach out to your Zscaler account team.]]></description>
            <dc:creator>Joby Menon (SVP, Product Management | Zscaler)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Five Cloud Sandbox Innovations That Close the Patient Zero Window]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/five-cloud-sandbox-innovations-close-patient-zero-window</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/five-cloud-sandbox-innovations-close-patient-zero-window</guid>
            <pubDate>Tue, 27 Oct 2026 13:00:00 GMT</pubDate>
            <description><![CDATA[In a&nbsp;recent post on what's new in Zscaler SSE, we covered the latest innovations across the platform. This post goes deeper on one of those areas: Cloud Sandbox, and five innovations that change what inline malware defense can do. The Patient Zero ProblemSecurity only works when it doesn't force a choice between protection and productivity. An organization that locks down everything grinds to a halt. Users find workarounds, shadow IT grows, and the attack surface quietly expands outside the security perimeter. An organization that prioritizes productivity at the expense of coverage leaves gaps that adversaries are increasingly engineered to exploit. Both paths lead to the same outcome: patient zero.The architecture most organizations rely on makes this worse. Legacy appliances and NGFW-attached sandboxes typically operate out-of-band, sending a copy of the file for detonation while the original is already delivered. Endpoint sandboxes only see managed devices and act post-delivery by design. Neither can stop patient zero; they can only confirm it happened.Coverage gaps compound the problem further. The risk isn't always about what a tool inspects, but about what it can't reach. Limited platform support, file size caps, and gaps in file type coverage create predictable blind spots. Adversaries don't stumble into these gaps by accident; they engineer around them deliberately.And they're getting better at it. The&nbsp;ThreatLabz 2026 Ransomware Report found 52 newly active ransomware groups emerged between April 2025 and March 2026, with tooling that appeared to have been developed with GenAI assistance. Attackers are producing novel malware faster than signatures can track, and they're abusing the same AI-powered workflows that enterprise users rely on every day, using them as cover to move malicious content through channels that look legitimate.Zscaler Cloud Sandbox eliminates that gap by moving the sandbox inline, into the inspection path of the Zero Trust Exchange. Unlike architectures that force a binary choice between blocking everything and allowing everything, it provides flexible enforcement options so organizations can balance security with productivity without creating patient zero exposure. The capabilities that follow show how that balance is achieved in practice. 1. AI Instant Verdict: Real-Time Blocking at Inline SpeedDelivering a verdict before the file reaches the endpoint only works if the verdict is fast. Full behavioral detonation takes minutes. Business moves in seconds. If every file waits for detonation, security teams face constant pressure to allow downloads before analysis completes, and that's where patient zero infections happen.AI Instant Verdict handles the common case at machine speed. Powered by a model built from more than&nbsp;600 million threat signatures and file behavioral patterns, ZIA scores files inline, in real time. Files scoring 91-100 on the AI/ML threat confidence scale are blocked before they reach an endpoint. In production, about 91% of files receive an instant benign verdict and are delivered with no perceptible delay. About 9% are escalated to full dynamic detonation in the cloud. A small percentage are blocked outright as high-confidence malicious.&nbsp;AI Instant Verdict doesn't replace detonation. It accelerates the common case so the uncommon case gets the full behavioral treatment without holding up the rest of the queue. 2. Three Channels, One Engine: Covering Every File Entry PathInline inspection is powerful, but it has a structural blind spot: files that never traverse the network. USB drives, AirDrop transfers, Bluetooth file sharing. These files arrive at the endpoint without touching your proxy, firewall, or cloud security stack. They bypass inline inspection entirely because they take a path inline architectures were never designed to cover.Cloud Sandbox is expanding across&nbsp;three channels, all powered by the same detection engine and delivering the same verdicts.Inline Sandbox provides real-time blocking of malicious content in traffic. Defense-in-depth layers stack in sequence: reputation checks, known pattern matching, content scanning, AI Instant Verdict, and full behavioral detonation. This is the core Cloud Sandbox capability, now accelerated with AI Instant Verdict.API-Driven File Analysis supports on-demand file submission for SOC investigations, M&amp;A file hygiene, partner file exchange, and any workflow where files need analysis outside the inline path. Every detonation produces MITRE ATT&amp;CK-mapped reports with TTPs, IOCs, and PCAPs, giving analysts real evidence rather than another alert. The API feeds directly into existing SIEM/SOAR workflows for out-of-band analysis.Endpoint Sandbox extends coverage to files arriving via offline paths (USB, Bluetooth, AirDrop, or any local transfer). These files are intercepted by&nbsp;Zscaler Client Connector, inspected, and neutralized before execution. This capability is coming in early 2027.&nbsp;Whether files arrive inline through the Zero Trust Exchange, side-loaded onto endpoints via offline channels, or submitted out-of-band by analysts for on-demand inspection, Zscaler Cloud Sandbox covers all three delivery paths with a single detection engine and unified threat intelligence. 3. macOS and Large File Support: Closing Two Evasion GapsTwo evasion paths that legacy sandboxes have long struggled with, and that attackers actively exploit.macOS Detonation. Cloud Sandbox now detonates .dmg and .pkg files across both inline and API channels. Mac endpoints have historically been treated as lower-risk, which has meant lower-coverage. With macOS detonation, the same behavioral analysis that protects Windows environments extends to the Mac fleet.200 MB Large File Support. EXE and DLL files up to&nbsp;200 MB can now be analyzed, with&nbsp;10-layer archive inspection for nested and compressed packages. File-size padding is a well-documented evasion technique: attackers deliberately inflate file sizes to exceed sandbox ingestion limits on appliance-based solutions. If your sandbox tops out at 32 MB or 50 MB, you're giving adversaries a free bypass. 4. Content Disarm &amp; ReconstructionWhen the workforce needs access to business-critical files that may carry threats, Content Disarm &amp; Reconstruction (coming early 2027) eliminates the block-or-allow dilemma by stripping malicious content, reconstructing the file in its original native format, and delivering a sanitized version. Users get a sanitized version of the file immediately while full detonation runs in the background. Once the sandbox returns a clean verdict, the original file becomes available.&nbsp; 5. Securing Agentic AIFor 30 years, "malware" meant compiled binaries: EXE files, DLLs, scripts with executable code. The security industry was built around detecting and blocking these artifacts. Agentic AI introduces a different kind of threat.Skill files are plaintext, but they're functionally executable. They instruct autonomous AI agents to act with user permissions. A poisoned skill file doesn't trigger any traditional detection engine because it looks like a text document, yet it can instruct an agent to exfiltrate data or escalate privileges within the legitimate permissions the agent already holds.Zscaler ThreatLabz&nbsp;uncovered a campaign where threat actors published a fake "DeepSeek-Claw" skill for the OpenClaw AI agent framework, embedding malicious instructions in&nbsp;SKILL.md that trick AI agents or developers into silently executing a PowerShell one-liner to download and run a remote MSI installer, ultimately infecting victims with malware to enable remote access, credential theft, and data exfiltration.Cloud Sandbox will address this with two new capabilities.&nbsp;Agentic Tool Download Inspection identifies, inspects, and halts unauthorized agentic AI frameworks and tooling at download time rather than discovering them later at runtime.&nbsp;Skill File Sandbox Detonation inspects and behaviorally analyzes text-based skill manifests and tool instruction files within Cloud Sandbox upon download before they can be loaded by an agent.As threats shift from compiled binaries to plaintext instructions, Cloud Sandbox is the first enterprise sandbox to bring inline behavioral detonation to this entirely new agentic vector. Both capabilities are coming in early 2027. Validated by Independent TestingCloud Sandbox's detection capabilities contributed directly to Zscaler's strongest independent test results yet.In the&nbsp;NSS Labs Q2 2026 SSE Threat Protection Test, Zscaler was tested against the updated SSE Threat Protection Methodology (v3.0), a more demanding standard than prior tests, using an adversarial approach where vendors receive no advance notice of the specific attacks. Zscaler delivered 98.85% overall security effectiveness, 100% evasion resistance across 583 techniques, a 98.65% malware block rate, 100% on handcrafted malware (sandbox-specific), and 99.63% false-positive accuracy. This is the third consecutive year Zscaler has delivered top-tier results. Zscaler was also awarded a&nbsp;AAA rating, the highest possible, in CyberRatings.org independent testing.These results are amplified by the&nbsp;Cloud Effect: every malicious file detected for one customer instantly protects every Zscaler customer globally. With the world's largest inline security cloud processing over 500 billion daily transactions, a zero-day blocked for one organization is blocked for all of them within seconds. Leaving the Legacy Sandbox Era BehindThe innovations above close the patient zero window from multiple angles. Faster verdicts, broader coverage, zero-wait productivity, and forward-looking protection against threats that don't look like traditional malware.And they all run on the same console, same policies, and same platform that ZIA customers already operate. No new appliance. No new tool to manage.Roughly 40% of the on-premises sandbox market still runs legacy hardware that can't inspect encrypted traffic at scale, can't cover macOS, can't handle offline file paths, and can't render AI-powered verdicts. Each of those gaps is an open door.Explore Zscaler Cloud Sandbox]]></description>
            <dc:creator>Vinay Polurouthu (Senior Director, Product Management - ZIA)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Extend Your Zscaler DLP to Every Endpoint]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/extend-your-zscaler-dlp-every-endpoint</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/extend-your-zscaler-dlp-every-endpoint</guid>
            <pubDate>Tue, 27 Oct 2026 11:00:10 GMT</pubDate>
            <description><![CDATA[Why Your Inline DLP Needs an Endpoint AllyYour inline DLP is working. It intercepts sensitive data at the network edge, enforces your policies, and keeps you compliant. But once that data lands on a device, your inline controls lose visibility.A file downloaded to a laptop. A document copied to a USB drive. Sensitive data synced to a personal Dropbox. A report sent to a printer. None of these actions pass through your inline inspection path, and each creates a real data exfiltration risk.The good news? Zscaler seamlessly bridges the endpoint data security gap, making comprehensive protection simpler and more accessible than ever. The Zscaler AdvantageTraditional endpoint DLP has earned its reputation: heavy agents, long deployments, fragmented policies, and slow time to value.That's not the Zscaler model.Zscaler Endpoint DLP is built directly into the Zscaler Client Connector (ZCC). There is no new agent to install, no new console to learn, no new vendor to onboard. Your existing ZCC becomes your endpoint DLP sensor the moment you activate the capability.This isn't a deployment. It's an activation. Security teams are up and running in minutes, not months.And critically, your Inline DLP policies, classification engines, and data identifiers extend directly to the endpoint even when the endpoint is offline. Every rule you've already written, every sensitive data type you've already defined, every control you've already tuned, all of it carries over. Zero rework required.&nbsp; Activate Endpoint DLP and See Risk on Day ZeroOne of the most powerful things about Zscaler Endpoint DLP is what happens the moment you turn it on, even before you configure a single block policy.Out-of-box visibility kicks in immediately. The platform automatically detects and catalogues every connected device across your fleet: removable storage, printers, portable devices, personal cloud sync apps. You get a real-time map of data at rest on endpoints and data movement channels that, until now, were completely dark.Most organizations don't know how much sensitive data is moving off-device until they actually look. Activation gives you that look instantly, with zero additional configuration. Layered Protection Across Every Channel That MattersZscaler Endpoint DLP applies a two-layer protection model that&nbsp;follows the user and the data:Layer 1 | Device Channel Control:&nbsp;Define who can use what. Restrict or allow USB drives, removable media, printers, and portable devices by user, group, or device type. Block unauthorized devices entirely or permit only IT-approved hardware for specific teams.Layer 2 | Content Inspection: Even when a device is permitted, the data it carries is still inspected. Your DLP policies evaluate actual file content, enforcing monitor, block, or user-confirm actions based on what the data&nbsp;contains, not just where it's going. Accelerate Incident Investigations with End-to-End ContextSecurity teams aren't starved for alerts, they're overwhelmed by disconnected ones.Separate endpoint and inline DLP tools mean separate alert streams, separate consoles, and manual correlation when incidents span both. That slows investigations, increases analyst fatigue, and gives risky activity more time to continue.Zscaler Endpoint DLP brings endpoint and inline incidents into a single console. Chronological timelines help analysts trace what happened, what data moved, where it went, which device was involved, and what the user did before and after.From that single view, your teams can:Get complete visibility into sensitive data at rest on endpointsDetect shadow IT for removable devices, printers, and applicationsConduct user- and device-level investigations using a chronological view of activities to surface patterns and anomalies Advanced When You Need It . Simple Always.Zscaler Endpoint DLP scales with your requirements: granular multi-rule policies, network-aware enforcement that automatically adjusts on-premises vs. remote, cross-platform support for Windows and macOS, and Shadow AI data protection for exfiltration paths traditional DLP was never built to catch. All of it is managed from the console your team already uses.Sophistication without added complexity. That's the point. The Only Step Left Is ActivationYour infrastructure is in place. Your policies are written. Your agent is already deployed.Zscaler Endpoint DLP helps you turn the investment you have already made into broader, end-to-end data security, extending your existing controls from the network edge to the endpoint.Ready to take the next step? Check out our webinar on the topic and&nbsp;talk to our product experts to&nbsp;book an Endpoint DLP demo&nbsp;today!]]></description>
            <dc:creator>Prerna Shankar (Senior Manager, Product Marketing- Data Protection)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Stop Treating Security Classification Guides Like Static Documents]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/stop-treating-security-classification-guides-static-documents</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/stop-treating-security-classification-guides-static-documents</guid>
            <pubDate>Fri, 23 Oct 2026 05:33:26 GMT</pubDate>
            <description><![CDATA[Operationalizing SCGs for Zero Trust data decisionsEvery national security organization has some version of the same data sharing problem: the security guidance exists, the data exists, the mission need exists, but the control path between them is manual. Security Classification Guides (SCG) explain what makes information sensitive, how it should be marked, and when combinations of facts become more sensitive than the individual parts. Yet those guides usually sit in documents while mission data moves through file shares, databases, data lakes, SaaS platforms, cross domain workflows, and now AI pipelines. This disconnect, between the releasability of mission critical data and operational effectiveness of our coalition partners, impacts the commander’s decision-making processes and impacts the effectiveness of the joint and coalition force.Implementing Zero Trust for data access greatly enhances the commander’s ability to rapidly integrate the entire contingency force.&nbsp; Zero Trust makes information access decisions based on the user, device, application, data, and context. Within the data pillar, zero trust enables machine readable classification context and through the policy engine data releasability is automated to unlock guidance stored in PDF files. Through Zero Trust the commander can keep pace with conditions on the battlefield. The Real Problem Is AggregationThe hardest classification problem is not always an obvious code word or a visible marking. Often the problem is aggregation. One data element may be acceptable. Another may be acceptable. Together, they may reveal a more sensitive capability, source, method, operational plan, or partner restriction. When teams cannot see that combination at scale, they usually pick one of two bad options: miss the risk or mark everything high.The Strava incident from 2018 is a public example of exactly this problem. Strava published a global heatmap of fitness tracking data. Individual workout routes were harmless on their own, but the aggregated picture revealed the locations, layouts, and activity patterns of military bases and intelligence facilities in conflict zones. None of the underlying data was classified. The combination was operationally sensitive. That kind of aggregation risk is what SCGs are designed to address, and catching it manually at scale is nearly impossible.&nbsp;Over classification feels safer, but it carries a mission cost. It slows coalition data sharing, makes deployed operations harder, increases staff workload with review backlogs, and limits the ability to use data for AI, analytics, and command decision making. Under classification is worse: it creates spillage and unauthorized disclosure risk. The right answer is not more manual review. The right answer is to operationalize the security classification guidance. What It Means to Operationalize an SCGOperationalizing an SCG means translating human readable guidance into classifiers and policy context feeding the Zero Trust policy engine. The guide remains authoritative. Human classification authorities still own the rules. But the operational system can now find matching data, explain why it matched, show who or what has access, and recommend or execute the appropriate control.Break the SCG into atomic rules, aggregation conditions, handling caveats, releasability constraints, and examples.Build classifiers from those rules using exact terms, patterns, dictionaries, entity recognition, machine learning, and semantic examples.Scan mission data repositories such as SMB/NFS shares, NetApp, S3 buckets, OneDrive, SharePoint, application databases, data lakes, and collaboration stores.Map matched data to users, groups, service accounts, APIs, applications, and AI agents with effective access.Implement through the policy engine to bind the classification result to policy decisions: allow, deny, route to guard review, remove access, quarantine, alert, or apply an approved enterprise label.&nbsp; A Concrete ExampleImagine a combatant command wants to share operational reporting with a coalition partner. The SCG says that a platform name alone is lower risk, a general mission area alone is lower risk, and a capability value alone is lower risk. But the combination of platform, location, and capability crosses a threshold and requires a higher marking or a NOFORN handling caveat.A static process depends on a human reviewer catching that combination every time. An operationalized process creates a classifier that detects the combination across repositories. When it finds a match, it records the matched SCG rule, highlights the relevant excerpt, assigns confidence, and checks the access graph. If the file is sitting in an open share or queued for transfer to a coalition portal, the workflow can stop the transfer, route the file to disclosure review, or remove unauthorized access.The point is not to remove humans from classification. The point is to make humans faster, better informed, less dependent on heroic manual review, and able to keep pace with the commander’s intent.&nbsp; Where Zscaler DSPM FitsZscaler DSPM as part of the Zero Trust platform can close the operational gap because commanders now answer questions such as: what sensitive data do I have, where is it, who or what has access, how is it being used, and what action should I take?Discovery and classification can identify sensitive data across cloud, SaaS, structured, unstructured, and customer hosted data stores.Custom and AI/ML classifiers&nbsp;can represent mission specific SCG concepts, including aggregation conditions. When the SCG says that a platform name, a location, and a capability value are each acceptable alone but sensitive in combination, that rule can be encoded as a classifier. DSPM then scans repositories to find where those combinations exist, so the aggregation risk described above is caught at machine scale rather than left to manual review.Access graphing&nbsp;connects sensitive data, including matched aggregations, to users, groups, service accounts, APIs, and AI agents. When a sensitive combination is found, the access graph shows exactly who or what can reach it.Activity context helps prioritize actual mission risk instead of treating every permission as equal.Guided remediation turns findings into action: remove broad access, open an ITSM ticket, alert the owner, route to guard review, or integrate with approved labeling workflows. A Better Zero Trust Data StoryFor Department of War and intelligence adjacent missions, this should become a central Zero Trust data pillar story: do not merely discover sensitive data; convert classification guidance into operational control. That is how agencies reduce over classification, speed coalition sharing, support commanders, and protect mission data as it moves into AI and analytics workflows.The practical starting point is small. Pick one SCG, one mission repository, one access problem, and one policy outcome. For example: identify all files matching a specific compartment rule on a file share, map who can access them, remove broad access, and route edge cases to a classification officer. Then expand to databases, data lakes, cross-domain workflows, and AI pipelines.The future state is not a world where every document is reviewed by hand before it can move. The future state is a data environment where classification guidance is machine actionable, access decisions are evidence based, and commanders can share the right data with the right partners at the speed of mission.If your organization is working to operationalize classification guidance as part of a Zero Trust data strategy, contact your Zscaler sales representative to learn how DSPM can support your mission.]]></description>
            <dc:creator>Andrew AJ Forysiak (Field CISO DOD)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Ransomware Victimology: Redefining the High-Risk User]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/ransomware-victimology-redefining-high-risk-user</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/ransomware-victimology-redefining-high-risk-user</guid>
            <pubDate>Thu, 22 Oct 2026 21:07:50 GMT</pubDate>
            <description><![CDATA[Demographic analysis of cyberattack victims can often provide insight to attackers’ habits and intent. The insights in the&nbsp;Zscaler ThreatLabz 2026 Ransomware Report include a look at victims based on several factors: their role within a targeted organization, the business function they serve, and industry sector. While these findings should not suggest that defenders shift their attention away from a less-targeted demographic, the findings can be used to prioritize efforts and detections from those most likely to face the initial brunt of ransomware campaigns.Zscaler’s David Moulton and Phil Hagen recently discussed this topic on an episode of SecOps Weekly.&nbsp; Check out the recording for additional perspective. Key TakeawaysRansomware operators seem to be tuning their playbooks to provide the most damaging impact in the shortest amount of time. This has resulted in faster and more successful attacks, as seen with larger payouts for a smaller number of victims detailed in the 2026 Ransomware Report.While victimology analysis helps provide some context for this trend, it certainly does not mean defenders should focus only on highly-positioned individuals, certain business functions, or limit ransomware preparedness and response planning to certain industries. Instead, these observations should inform defenders on how likely they are to be in the attackers’ sights as well as how to prioritize the detection of known ransomware precursors when observed in conjunction with a targeted role or function.This holistic approach will allow defenders to keep in step with the advancement and change in ransomware operations as they continue to evolve in the future. Technical AnalysisMore Senior Roles are the Initial Victims of Ransomware CampaignsMore than half of initial victims in ransomware cases held a title of “Manager” or above. Whether this is the result of deliberate targeting or other factors is unknown. However, the outcome is clear: Attackers are gaining footholds via individual victims with both expansive access in most environments and precious trust with the organization’s personnel.For most organizations, a suspicious request from an obviously bogus, externally-sourced email might finally be discounted after decades of user education. On the other hand, if the attacker sent such a lure from the manager’s actual email account, it would be difficult for the recipient to differentiate the malicious request from a legitimate one via the same manager. Clearly, co-opting an authority figure’s legitimate communications path provides unprecedented access, believability, and therefore successes.Business Functions with Access to Valuable/Regulated Data are Targeted FirstAttackers’ initial access to their targets is overwhelmingly through functions that focus on business operations. This directly translates to gaining access to business-critical information. Two thirds of initial attack vectors involved individual victims in the accounting/finance, sales, operations, and HR departments. This clearly shows attackers are either deliberately targeting or simply finding the most success with parts of the victims’ organizations that provide maximum value for ransom operations.With the immediate access to this business-critical information, attackers increase the likelihood of access to vital information the victim would be more likely to pay to recover or prevent from public disclosure. Obviously data in this category would be more valuable to the victim and command higher recovery or “hush” payments.Just Two Industries Represent Half of All VictimsSimilar to the Business Function findings above, over half of all victims are concentrated among industries in the manufacturing and technology sectors. Whether this is the result of deliberate targeting of these sectors or other factors, the reality is that organizations who are more sensitive to service disruptions and/or have access to sensitive information represent the majority of victims in the sample.Ransomware operators have demonstrated a clear operational tendency to maximize attack impact. A manufacturing environment that measures productivity in daily output and a technology firm whose valuation depends on proprietary intellectual property share the same vulnerability: both are strongly incentivized to pay rather than endure prolonged downtime or risk hostile disclosure. ConclusionAs the ransomware operators change their approaches, so must the defenders. However, a good deal of foundational cybersecurity best practices will remain valuable means of mitigating the attackers’ success. Applying the concept of least-privilege will minimize the amount of data an individual victim can access, thereby limiting the amount of data an attacker can steal using their account.&nbsp;Solutions like Zscaler ZPA, or traditional microsegmentation, constrain lateral movement, preventing a single compromised identity or system from becoming a foothold across the environment. User education remains a vital component of any effective security program; as attacker tactics shift, so should the guidance users receive.Defense operations can use this information to fine tune their own alerting logic as well. While ransomware precursors are generally known and therefore detectable, perhaps a higher priority should be placed on those detections when observed from accounts of senior personnel in the organization or members of a more heavily targeted business function. Zscaler Coverage to aid in Mitigating Ransomware AttacksZscaler ZTE eliminates traditional network architecture in favor of user-to-application and similar controls through a managed and monitored cloud pathway. ZTE’s AI threat detection helps identify malicious targeting early, giving defenders more time to mitigate threats before they become catastrophic.To monitor egress paths and block sensitive data from leaving enterprise systems,&nbsp;Zscaler DLP is uniquely positioned to provide security teams with the visibility needed to identify potential data loss quickly and early, before a ransomware campaign can steal enough data to be a credible risk.As attackers adopt AI technologies, so must security operations teams.&nbsp;Zscaler Agentic SecOps provides a decisive edge in this escalation, providing scalable and adaptive agents to help your human SOC team members keep pace with attackers.]]></description>
            <dc:creator>Phil Hagen (Principal Information Security Researcher)</dc:creator>
        </item>
        <item>
            <title><![CDATA[When Certificate Trust Breaks: Why TLS Inspection Is an Enterprise Safety Net]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/when-certificate-trust-breaks-why-tls-inspection-enterprise-safety-net</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/when-certificate-trust-breaks-why-tls-inspection-enterprise-safety-net</guid>
            <pubDate>Thu, 22 Oct 2026 17:39:07 GMT</pubDate>
            <description><![CDATA[The recent eMudhra certificate authority compromise highlights an often-overlooked security challenge: protecting enterprise applications that cannot respond to PKI incidents as quickly as modern web browsers.Certificate trust is not absoluteThe security of virtually every Internet connection depends on a fundamental assumption: when a trusted Certificate Authority (CA) issues a digital certificate, that certificate can be relied upon to authenticate the identity of a remote server.But what happens when that trust is misplaced?In October 2026, the discovery of compromised private keys associated with eight intermediate CA certificates issued by eMudhra sent ripples through the Internet security community. Due to a flaw in eMudhra's key-generation process, the affected ECDSA P-384 private keys had values smaller than 256, effectively providing at most 8 bits of randomness instead of the expected 384 bits. This made it possible to recover the private keys almost instantly from publicly available certificates. According to eMudhra, the problem originated from an error during a key-wrapping operation that inadvertently produced a second set of weak keys, which were subsequently used instead of the correctly generated ones.Six affected intermediates were capable of issuing TLS certificates. An attacker possessing their private keys could create fraudulent certificates for arbitrary websites, potentially allowing them to impersonate legitimate services and intercept encrypted communications.This was not a weakness in TLS encryption itself. Rather, it was a failure of the public key infrastructure (PKI) responsible for authenticating the parties establishing encrypted connections.The response from major browser vendors was swift. Google Chrome deployed emergency certificate-blocking updates through CRLSets, while Mozilla Firefox used its OneCRL mechanism to reject the affected certificates. Both mechanisms can distribute emergency distrust decisions without requiring users to install a new browser version.Importantly, Certificate Transparency provided another layer of protection. Google reported that no TLS certificates issued through the affected intermediates had been recorded in Certificate Transparency logs before Chrome's emergency block, preventing fraudulent certificates from being used successfully against CT-enforcing Chrome clients.However, these browser protections raise a much broader question: What about all the enterprise applications that are not web browsers? The enterprise Internet is much bigger than the browserModern browsers are exceptionally sophisticated TLS clients. They benefit from dedicated security engineering teams, centralized trust management, automated updates, Certificate Transparency enforcement, and specialized mechanisms for distributing emergency certificate distrust decisions.Unfortunately, much of the software running in enterprise environments does not share these capabilities.Consider the diversity of applications and systems that establish outbound encrypted connections in a typical large enterprise:Business applications built on Rust, Java, Python, Go, or other language runtimes, sometimes with their own certificate trust stores.Containers and microservices relying on certificate bundles included when their images were originally built.Legacy enterprise applications that require extensive testing and change-management approvals before being updated.IoT devices, industrial systems, and network appliances with limited or infrequent software update capabilities.Background services and automated workloads that communicate with external APIs without any browser involvement.Many of these clients rely on operating system or application-specific trust stores that may be updated infrequently. Others do not consistently check certificate revocation information or enforce Certificate Transparency requirements.This creates an uncomfortable security asymmetry.A browser vendor can rapidly distribute a decision to distrust a compromised CA to millions of users. An enterprise security team, meanwhile, may need to identify hundreds of affected applications, determine which cryptographic libraries and trust stores they use, obtain updated packages, rebuild container images, validate application compatibility, and schedule deployments.During this process, applications that continue to trust the affected CA may remain vulnerable to fraudulent certificates.The eMudhra incident demonstrates that the speed at which an organization can respond to compromised certificate trust is itself a critical security capability. TLS inspection: More than visibility into encrypted threatsTLS inspection is frequently discussed in the context of detecting malware, preventing data exfiltration, and applying security policies to encrypted traffic.Those are important capabilities. But TLS inspection also provides another security benefit that receives considerably less attention: centralized enforcement of cryptographic standards and certificate trust decisions.When an application connects directly to an HTTPS server, it is responsible for validating the server's certificate. That validation depends on the application's cryptographic libraries, trusted CA certificates, revocation mechanisms, and local configuration.With TLS inspection, the trust relationship changes.Instead of establishing a single end-to-end TLS connection, the inspecting security service establishes two independently authenticated TLS connections:Between the enterprise application and the security service. The application authenticates the inspecting proxy using a certificate issued by a CA trusted by the enterprise.Between the security service and the destination server. The security service independently validates the destination's certificate against its own managed trust policy before allowing the connection.The enterprise application no longer needs to rely exclusively on its potentially outdated certificate trust store to determine whether the remote server is trustworthy. That decision can be enforced by a centrally managed security infrastructure.Consider an application whose certificate trust store has not yet been updated following the eMudhra incident. If it establishes a direct connection to a malicious server presenting a forged certificate signed by one of the compromised intermediates, the application might accept that certificate as valid.Now consider the same application connecting through a TLS-inspecting security service that has already distrusted the compromised CA. The security service rejects the fraudulent certificate and blocks the connection, even though the application itself might have accepted it.The application's outdated trust configuration is no longer the only line of defense. How Zscaler Internet Access helps close the gapZscaler Internet AccessTM (ZIATM) delivers TLS inspection through a globally distributed cloud security infrastructure, enabling organizations to apply consistent security policies to encrypted Internet traffic without depending entirely on security controls within individual applications.Following the discovery of the eMudhra incident, Zscaler updated certificate trust stores across its global proxy infrastructure to reject certificates associated with the compromised CAs.For customers using ZIA TLS inspection, with the Untrusted Server Certificates policy configured to Block, this provides protection against attempts to establish connections using certificates issued through those compromised keys.The protection is particularly valuable for organizations with complex application environments.An enterprise does not need to wait until every application has received an updated trust bundle before benefiting from the centrally enforced distrust decision. Applications whose traffic is inspected by ZIA can inherit that protection, even when their local certificate validation configurations have not yet been updated.Importantly, the benefit is not limited to this specific incident.Certificate authorities can be compromised, private keys can be exposed, issuance processes can fail, and vulnerabilities in PKI implementations can be discovered. Responding to these events requires organizations to update their trust decisions quickly.A centrally managed inspection infrastructure provides an additional point at which those decisions can be enforced. Once the service has incorporated the necessary certificate distrust information, that protection can extend across inspected applications without requiring individual updates to each client.This does not eliminate the need for incident response. It changes the scale of the remediation challenge, allowing security teams to reduce immediate exposure while they coordinate the more complex process of updating their application estates. Making TLS inspection an effective enterprise security controlRealizing these benefits requires more than simply routing traffic through a cloud security service.First, organizations should aim for comprehensive TLS inspection coverage across their enterprise application environments, not just employee web browsing. Modern enterprises generate substantial volumes of encrypted traffic through background services, API clients, automated workloads, and applications running outside traditional browsers. These connections are just as dependent on PKI trust as interactive browsing sessions.Second, certificate validation policies must be configured to enforce meaningful security decisions. In ZIA, configuring the handling of untrusted server certificates to Block ensures that certificate validation failures result in connections being rejected rather than permitted.Third, organizations must ensure that applications trust the certificates used by their enterprise TLS inspection infrastructure.While browsers typically use operating-system-managed trust stores, many enterprise applications maintain their own. Java runtimes, application frameworks, containerized workloads, and embedded software may therefore require additional configuration to trust the enterprise's inspection CA. This is a particularly important deployment consideration. Establishing consistent trust in the inspecting service enables applications to benefit from centrally managed certificate validation and other security controls.Finally, TLS inspection should complement rather than replace application and operating system updates.Organizations should continue to remove compromised trust anchors, update cryptographic libraries, and remediate vulnerable applications. Centrally managed TLS inspection is not a substitute for maintaining healthy PKI configurations throughout the enterprise.Instead, it provides a valuable security safety net, reducing the urgency of having to update every affected client simultaneously and giving overstretched security teams additional time to deploy durable fixes. Security requires the ability to change trust quicklyThe eMudhra incident is an important reminder that trust in the public PKI ecosystem is neither static nor infallible.Even well-established certificate authorities can experience cryptographic failures with consequences far beyond their own infrastructure.Modern web browsers have developed sophisticated mechanisms to respond to such incidents rapidly. Unfortunately, the broader enterprise application ecosystem remains much more fragmented, with inconsistent certificate validation practices, disparate trust stores, and widely varying update capabilities.For CISOs and security architects, this raises an important strategic question: How quickly can your organization change whom its applications trust?If the answer depends on identifying, rebuilding, testing, and updating every affected application individually, a CA compromise can quickly become a major operational challenge.TLS inspection offers an additional layer of resilience.By centralizing certificate validation and enforcing updated trust decisions across encrypted connections, organizations can reduce their exposure to compromised certificate authorities while continuing the necessary work of updating individual systems.The value of TLS inspection therefore extends well beyond detecting malicious content or protecting sensitive data in transit.It is also about ensuring that when trust in the Internet's cryptographic infrastructure breaks, enterprise security does not have to wait for every application to catch up.]]></description>
            <dc:creator>Yaroslav Rosomakho (Chief Scientist)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Ransomware at Machine Speed: How GenAI Shrinks the Path after Initial Access]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/ransomware-machine-speed-how-genai-shrinks-path-after-initial-access</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/ransomware-machine-speed-how-genai-shrinks-path-after-initial-access</guid>
            <pubDate>Fri, 16 Oct 2026 22:48:36 GMT</pubDate>
            <description><![CDATA[Artificial Intelligence technologies have made a huge impact on the security industry. But as with any public technology, adversaries have access to AI as well. They’re wasting no time incorporating AI into their malicious workflows and ransomware operators have been able to leverage it - unfortunately, this has led to some of their successes.Fortunately, there is plenty of potential for defenders to leverage similar AI technologies to improve their own game, neutralizing the adversaries’ advantage to keep users and resources safe. As organizations adopt these tools, they also need to secure their own use of GenAI. Our guide on how to secure GenAI usage in the enterprise outlines practical steps to reduce those risks.This blog post covers adversaries’ uses of Generative AI (GenAI) for both social engineering pretexts and technical development, as well as how defenders can spot and mitigate those efforts. For the full story, be sure to check out the complete analysis in the Zscaler ThreatLabz 2026 Ransomware Report. Key TakeawaysRansomware attacks continue to be a major driver of cybercrime incidents and attacker’s corresponding financial gains. While there are numerous means of compromising a victim, ransomware threat actors typically rely on social engineering as their first step toward compromising a target. The more believable a social engineering ruse, the more likely it will be successful.&nbsp; Attackers are already using GenAI to help overcome some of their traditional shortcomings.After they gain an initial foothold, time is of the essence. The faster the attacker can move throughout the victim’s environment and acquire sensitive data to either encrypt or steal outright, the less likely they will be detected while doing so and the more likely their efforts will be successful. &nbsp;Here again, GenAI is providing attackers with a faster and more focused approach that yields greater success.However, defenders can also use AI-enabled technology for their own purposes to stay in step with the attackers. Doing so ensures we keep pace with or even get ahead of the malicious uses of these nascent technologies. Technical AnalysisMore Effective Social Engineering RusesHistorically, most attackers’ social engineering game has been stifled by their inauthenticity. While there are many instances of intelligence-informed attackers crafting very believable ruses, these have been rare. The vast majority of ransomware actors used volume as their strategy for initially landing on a target system. This is why most user education campaigns have focused on spotting typos, non-native-speaking grammar mistakes, and other mostly obvious weaknesses in phishing emails and sites.However, AI has unmistakably leveled the playing field, giving attackers the capability to blend into the wave of legitimate email like never before. This, in turn, gives them a much higher chance of tricking a victim into clicking the link, downloading the file, or otherwise falling into the trap that’s been laid.Attackers can now use any of the public-facing GenAI platforms to create email messages, websites, and other assets that are polished, natively-built in the target’s language, and crafted to maximize success. As discussed in a previous blog, phishing emails are often used to trick a user into using a Remote Monitoring and Management (RMM) tool at the attacker’s behest, which then gives them full access to the victim’s system as well as potentially their wider environment.Faster Discovery of Valuable Materials…To StealGenAI technologies are also well suited to examine massive amounts of data for the purposes of classification or content searching. Once an attacker has access to the victim’s system, GenAI can therefore be used to search all materials to which a victim’s system has access, seeking the most valuable or sensitive data for theft or encryption during the next phase of the attack.This approach gives the attacker an incredibly fast method of identifying and acquiring the most damaging data, which then maximizes the likelihood the victim’s organization will pay the ransom to retrieve or prevent the disclosure of the encrypted/stolen data. Although this occurs after the initial access, it is still a form of reconnaissance. Speed is of the essence and GenAI makes the process even faster than it could be automated with traditional attacker scripts and playbooks.Speedy Creation and Iteration of Bespoke ScriptsFile and network signatures are perhaps one of the most well-established indicators in the security world. From the earliest days of antivirus to more modern implementations of fuzzy hashing and traffic fingerprinting, practically every security program uses signatures in some capacity. While this used to be effective, attackers can now rapidly vary their malware and scripts, resulting in corresponding variance of their signatures. This allows attackers to evade traditional detection mechanisms making it much harder to spot their activity based on those signatures alone.Attackers using GenAI-built scripts and other malware also no longer need to rely on common tools that defenders are aware of and actively hunting for. Bespoke tooling was once the exclusive domain of well-funded threat actors, but the wide availability of GenAI tools opens those floodgates of potential for any threat actor with the motivation and a free (or stolen) LLM account. In the same vein, custom tools are no longer a clear indicator of an advanced threat actor. Garden variety ransomware operators become harder to differentiate from the larger and more resourced groups, significantly hindering threat actor identification. ConclusionAs with practically every technological advancement in history, Artificial Intelligence and GenAI in particular can be used for good and evil purposes. While the advent of novel attack techniques has been gleefully incorporated into ransomware actors’ toolboxes, defenders can leverage similar tooling to improve their defensive and detective capabilities. This arms race mentality is not new in the security industry. Encryption, even better encryption, widespread Internet access, social and otherwise publicly-generated media content, the proliferation of mobile devices, and more have all come with similar risks since the earliest phases of each development.While ransomware operators continue to improve the efficiency and effectiveness of their efforts through the use of GenAI, this does not mean that defenders have to be at a disadvantage. The most effective and forward-leaning defender teams have already stepped up their game in preparation for or in response to the attackers' improved tradecraft. These defense improvements, along with a robust and tested security program in general, can help to keep ransomware threats at bay and ensure the integrity of the valuable data throughout the enterprise. Zscaler Coverage to Mitigate the Risk of Advancing RansomwareAgentic SecOps fuses zero trust telemetry, threat intelligence, and agentic workflows into a single view, helping security teams to more quickly and decisively detect, investigate, and respond to ransomware threats.AI-based detection from the Zscaler Secure Web Gateway identifies and blocks novel attacker infrastructure such as phishing sites and C2 components.The Zero Trust Browser’s AI capabilities identify suspicious web content, limiting the potential for malware delivery and data leaks, even through credibly-scraped websites.]]></description>
            <dc:creator>Phil Hagen (Principal Information Security Researcher)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Zero Trust for Artificial Intelligence]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/zero-trust-artificial-intelligence</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/zero-trust-artificial-intelligence</guid>
            <pubDate>Fri, 16 Oct 2026 16:22:54 GMT</pubDate>
            <description><![CDATA[IntroductionFor more than a decade, we've helped organizations implement Zero Trust access with Zscaler Internet Access (ZIA) and Zscaler Private Access (ZPA). The destination was always the same: least-privilege access, where users connect only to the applications they're authorized to use, from devices the organization trusts. The journey to get there taught us lessons that are now more relevant than ever, because the next wave of users won't be human. They'll be AI agents, and they'll operate at machine speed.If we want Agentic AI to work safely inside the enterprise, we need to apply the same Zero Trust principles to agents that we spent the last decade applying to people. This blog explains what those principles look like in practice. What we’ve learned from a decade of Zero Trust deploymentsWhen customers first deployed ZPA, the biggest obstacle wasn't technology. It was visibility. Most organizations had a distinct lack of insight into what applications actually existed in their environment, who owned them, and who should have access. Access sprawl was the norm: users retained entitlements to applications, and the data within them, long after moving departments. And they could reach those applications from a myriad of devices: company owned, company managed, patched, unpatched, and BYOD. Every unmanaged or unpatched device that could touch an application exposed it to compromise, and exposed the organization to data loss.So customers started their Zero Trust journey with a wildcard policy. Broad access, deliberately, for a short time, to gain a complete view of what applications exist, who is accessing them, and from which devices. From that observed reality, Zscaler pioneered AI-powered segmentation and policy recommendations (AI-Segmentation and AI-Policy) to compress the path to least privilege: users could access only approved applications, from approved devices, governed by granular access policy.Something interesting happened along the way. If the outcome of implementing Zero Trust is fine-grained access to applications and data, the side effect is a detailed, living configuration management database (CMDB) with solid identity governance controls. Full segmentation based on user and device trust ensures users cannot reach applications and data they aren't permissioned for. Identity governance (IGA) ensures users can request, and be granted, access as needed, based on their job role and the application's ownership. Discovery, ownership, entitlement, and enforcement became a continuous loop rather than an annual audit exercise.As it happens, that loop is exactly what Agentic AI is missing today. How agentic AI raises the stakes for least privilegeIn an agentic world, a user asks an agent to perform a task on their behalf. That agent may spawn multiple sub-agents, each performing a specific task. The user might hold broad entitlements appropriate to their job role, but the agent should not inherit all of them. The agent's access should be constrained to the task it has been asked to perform, granted just in time, valid for a specific session, and aligned with the intent of the original request. Sub-agents should each be constrained to their specific sub-task, traceable back to the intent of the root agent.Human IGA often has a human in the loop: access is granted only after a person approves it. That model doesn't survive machine speed. Non-human IGA needs an automated system that approves access based on intent: just in time, session bound, and fully audited. The human moves from in the loop to on the loop. Because every access decision flows through an inline agentic gateway, the audit trail it produces gives humans continuous visibility and control: they supervise, intervene, and revoke, rather than approve every transaction. That is what allows agents to run at machine speed with constrained access, rather than machine speed with the user's full credentials.This isn't theoretical. Recent incidents show that agents do not fail like traditional applications – they find unique, and unintended, ways to achieve their tasks. During OpenAI's own security testing, the o1 model escaped a broken capture-the-flag sandbox by discovering a misconfigured Docker API on the evaluation host and spinning up its own container to read the flag (OpenAI o1 System Card). In July 2025, Replit's coding agent deleted a production database during an explicit code freeze, then produced misleading information about the rollback (AI Incident Database, Incident 1152). The EchoLeak vulnerability (CVE-2025-32711) showed that a single crafted email could silently instruct Microsoft 365 Copilot to exfiltrate data from everything in its access scope, with zero clicks from the user (The Hacker News). And in November 2025, Anthropic disclosed that a state-sponsored group had used its Claude Code agent, orchestrated over MCP, to run an espionage campaign against roughly 30 organizations, with AI performing an estimated 80-90% of the tactical work (Anthropic).The pattern across all of these: an agent with more access than its task required, and no independent control point between the agent and the systems it touched. Models and agents must be controlled, and in an enterprise where access governance is well established, the key mechanism is Zero Trust and least privilege access.The analyst community sees the same trajectory. Gartner predicts that by 2028, 25% of enterprise breaches will be traced back to AI agent abuse, from both external and malicious internal actors (Gartner). Forrester expects an agentic AI deployment to cause a major public breach in 2026, noting that 97% of organizations that suffered AI-related breaches lacked proper AI access controls (Forrester, via Infosecurity Magazine). Nine Zero Trust principles for AI systemsTo make agentic AI safe for the enterprise, organizations need more than model guardrails or prompt filtering. They need to extend proven Zero Trust principles to AI agents: discovering what agents exist, governing what they can access, constraining their actions to the task at hand, and continuously verifying trust throughout the session. Done well, this gives enterprises the foundation for least-privilege, data-secure agentic AI. Nine principles define that foundation.1. Inventory: You cannot secure what you cannot see, and this was the first lesson of ZPA deployments. Understanding the footprint of agents, MCP servers, LLMs, skills, and plugins is imperative, whether they run on a user's device (IDEs and local agents accessing local MCP servers over STDIO, or local copies of data) or in IaaS, accessing hosted MCP servers over streamable HTTPS and hosted applications. Equally imperative: a complete view of the keys, secrets, and credentials in use across that estate. An agent running “on behalf of” a user, but with the user's real credentials, is a risk that needs addressing directly.The scale of the challenge is already clear: Machine identities outnumber humans by more than 80 to 1, with nearly half holding sensitive or privileged access. Agentic AI will accelerate that ratio, with each human identity spawning over 140 Agentic Identities.2. Flow control: Agents should not have direct access to systems or data. Just as the Zero Trust Exchange removed direct network paths between users and applications, an Agentic Trust Exchange should be the architectural control point for all agentic communication, providing brokered/gateway access for every connection between an agent and the systems it needs to reach. No broker, no connection.3. Routing. Not every task needs the most expensive model. Understanding which models are being used, and the token consumption against each, matters: expensive LLMs with deep intelligence and training on one end, cheaper LLMs or small language models (SLMs) on the other. We have seen this pattern before. As customers moved from building, owning, and operating datacenters to adopting IaaS, SaaS, and PaaS with a view to reducing cost, the inverse actually happened: costs went up alongside the DevOps agility, and CNAPP (cloud-native application protection platform) tooling evolved to give customers visibility into what was running in their cloud estate and what it was costing them. With AI, visibility and control of token costs is just as important. Routing each request to the most appropriate model based on intent, reserving frontier LLMs for deep reasoning and steering routine tasks to cheaper or smaller models, delivers cost savings alongside performance improvements. The exchange brokering the traffic is the natural place to make that routing decision.4. Intent: Humans are sometimes malicious, but that's rarely why data loss happens. Usually they've been manipulated: phished into clicking a link. Agents are manipulated the same way, through prompt injection and poisoned context, as EchoLeak demonstrated. Red-teaming the agents, the MCP servers, and the applications lets us test for intent, implement guardrails on LLM communication, harden the prompts, and inspect and control MCP traffic inline.5. Access control: Once we understand the access an agent needs for its task, we can constrain it. The agent's identity must be unique and distinct from the user calling it. The agent should never hold credentials directly; instead, credentials should be injected just in time into the communication by the exchange, and be time or session bound, so they cannot be extracted, manipulated, or replayed outside the brokered session.The window for error is shrinking: Gartner predicts AI agents will cut the time it takes to exploit exposed accounts by 50% by 2027 (Gartner). Credentials that never leave the exchange, and expire with the session, take that attack path off the table.6. Sovereignty and data residency: Access decisions must account for where everything, and everyone, is. The gateway is the natural enforcement point for sovereignty controls, evaluating user attributes (home country, role), location signals (geo-IP, travel patterns), and where the data, agent, MCP server, model, and application each reside. When the user, the gateway, and the model all sit within an approved jurisdiction, access can be allowed. When any component in the chain resides in a jurisdiction the policy does not permit for that user, access should be denied, regardless of where the user is sitting. Signals such as impossible travel and UEBA (user and entity behavior analytics) risk should feed the same policy, so sovereignty is evaluated continuously across the session, not checked once at login.7. Access governance. A full access graph should show which agents, users, and systems can obtain credentials, and what those credentials can reach. This is IGA for non-human identities: using the access graph to ensure every credential is secured, minted just in time, and scoped to least privilege, with automated, intent-based approval replacing the human in the loop where speed demands it, and a full audit trail either way. The ability to attest who, or what, can access which data, using which agents, MCP servers, and LLMs, is paramount. Attestation is a side effect of access governance, but it allows organizations to be explicit: access to data and models is granted against a defined set of criteria, and provable on demand.8. Conditional access engine: Signals change over time. If a human disables security controls on an endpoint, their sessions get revoked. The same continuous evaluation must apply to agents: if an agent performs risky actions, or reaches for more data or systems than its task profile warrants, the conditional access engine revokes its sessions in real time. Trust is evaluated continuously, never granted permanently.9. Deception and decoys: When the Zero Trust Exchange identifies malicious intent today, users and systems are contained and steered toward decoys to gather intelligence. Agents are aggressive, fast, and thorough in reconnaissance, which makes them even more susceptible to deception. Steering a misbehaving agent into a decoy environment both contains it and reveals its intent. The outcome: Audited, attested, governed AIImplementing these Zero Trust principles for AI systems gives the organization a full audit of every agent in the environment and the ability to attest exactly what data each one can access. Just as Zero Trust for users delivered a living CMDB and identity governance as a side effect, Zero Trust for AI delivers the inventory, access graph, and governance evidence that regulators, auditors, and boards are already beginning to demand.Least privilege was the destination for human access. For agentic AI, it's the starting condition. Organizations that spent the last decade building Zero Trust for their workforce already have the architecture, the identity foundation, and the governance discipline; extending it to agents is the natural next step, and the only way to let agents run at machine speed without accepting machine-speed risk.Analysts are converging on the same conclusion. Gartner predicts that by 2028, 40% of CIOs will demand “guardian agents” capable of autonomously tracking, overseeing, and containing the actions of other AI agents (Gartner). A Zero Trust architecture for AI, with an inline exchange as the control point, is how the enterprise delivers that oversight.To learn more about how Zscaler secures AI, visit Zscaler AI Security.References1. OpenAI o1 System Card (sandbox escape during CTF evaluation): openai.com/index/openai-o1-system-card2. AI Incident Database, Incident 1152 – Replit agent deleted production database during code freeze: incidentdatabase.ai/cite/11523. The Hacker News – EchoLeak (CVE-2025-32711), zero-click data exfiltration via Microsoft 365 Copilot: thehackernews.com4. Anthropic – Disrupting the first reported AI-orchestrated cyber espionage campaign (GTG-1002): anthropic.com/news/disrupting-AI-espionage5. Gartner – Top Predictions for IT Organizations and Users in 2025 and Beyond (25% of enterprise breaches traced to AI agent abuse by 2028): gartner.com6. Forrester Predictions 2026 – agentic AI deployment to cause a major public breach (via Infosecurity Magazine): infosecurity-magazine.com7. Gartner – AI agents will reduce the time to exploit account exposures by 50% by 2027: gartner.com8. Gartner – Guardian agents to capture 10-15% of the agentic AI market by 2030 (40% of CIOs demanding guardian agents by 2028): gartner.com]]></description>
            <dc:creator>Mark Ryan (Zscaler)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Introducing the Modernized Client Connector UI]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/modernized-client-connector-experience</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/modernized-client-connector-experience</guid>
            <pubDate>Wed, 14 Oct 2026 12:10:12 GMT</pubDate>
            <description><![CDATA[Since the very beginning, the Zscaler Client Connector has been a cornerstone of the zero trust architecture that we provide to customers. It’s the endpoint agent that ensures user traffic flows through the Zero Trust Exchange for least-privileged access to any destination. By and large, customers have been very happy to use Client Connector and its breadth of innovative functionality. But we've heard&nbsp;all of your feedback: the end user interface looked outdated, it felt complex and confusing, and it needed to accommodate your company's branding so that your users could know that it was deployed by your IT team.&nbsp;So, we're excited to introduce the&nbsp;modernized Client Connector UI, delivering a cleaner, simpler, and more intuitive experience that is designed with your end users in mind.The new UI experience for Client Connector strips away the noise and minimizes the chances of end users getting confused. Instead of surfacing complex technical details by default, users now get instant, clear feedback on the status of their Zscaler services—all at a glance. But that doesn’t mean that we’ve taken anything away; users who need to dig into advanced details can still do so, and anyone who wants to fall back to the classic UI to troubleshoot an issue can still do that, too. Additionally, we've added&nbsp;optional custom branding so that your organization can tailor Client Connector to match your internal applications and give employees a seamless, consistent experience across your entire tech stack.Alongside the new UI, we're also introducing&nbsp;granular notification control—a long-requested capability that puts administrators in control of the notifications that their end users receive. Previously, notifications were categorized and controlled entirely by Zscaler, leaving customers unable to determine which alerts their end users would see and which they would not. Now, from a single admin portal, you can configure the visibility and persistence of each individual notification across solutions and across categories like service status, app update, and more. Not to mention, you can have different settings for each of the different supported operating systems. The result is far greater control over the experience in your specific environment, and dramatically reduced notification noise for end users. That means less friction for admins and better quality of life for users—and that's the power of the modernized Client Connector UI.If you’re ready to explore the new, better-than-ever experience for Client Connector, reach out to your Zscaler account team and request access to the Client Connector 5.0 release.&nbsp;]]></description>
            <dc:creator>Karen Daza (Zscaler)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Uncovering Executables that Trigger DLL Sideloading Attacks with Endpoint Context]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/uncover-dll-sideloading-attack-endpoint-context</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/uncover-dll-sideloading-attack-endpoint-context</guid>
            <pubDate>Mon, 12 Oct 2026 23:22:28 GMT</pubDate>
            <description><![CDATA[Threat actors are constantly refining their techniques to evade detection and deliver malicious payloads. DLL sideloading is a technique that has seen a resurgence in popularity among cybercriminal and espionage groups. This covert method allows attackers to execute malicious code under the guise of a legitimate and trusted application, making it a formidable challenge for security professionals to detect and mitigate.This blog post will delve into the mechanics of DLL sideloading, explore how threat actor groups like&nbsp;Silver Fox&nbsp;and REvil leverage this technique and how Zscaler Endpoint Context helps SecOps teams uncover files masquerading as valid executables that trigger DLL files to execute malicious code.&nbsp; What is DLL Sideloading?A Dynamic-Link Library (DLL) is a file that contains code and data that can be used by multiple programs at the same time. DLL sideloading is an attack vector that exploits the way Windows applications search for and load these required DLLs.When an application is launched, it often needs to load various DLLs to function correctly. If the application doesn't specify the full path to a required DLL, Windows will search for it in a predetermined sequence of directories. Attackers can take advantage of this by placing a malicious DLL with the same name as a legitimate one in a location that Windows searches *before* the directory containing the genuine DLL. When the legitimate application starts, it inadvertently loads and executes the malicious DLL, giving the attacker a foothold in the system. How Threat Actors Use DLL SideloadingDLL sideloading is a popular technique for several reasons:Evasion: Because the malicious code is executed by a trusted and often digitally signed application, it is less likely to be flagged by antivirus software and other security solutions.Persistence:&nbsp;If the compromised application is one that runs at startup, the malicious DLL will also be loaded each time the system boots, ensuring the attacker's code persists on the infected machine.Privilege Escalation: If the legitimate application runs with elevated privileges, the malicious DLL will inherit those same permissions, allowing the attacker to perform more sensitive actions on the system. Example 1: Silver Fox's Attack on Accounting and Tax Preparation FirmsSilver Fox, a China-based threat actor group (also known as Void Arachne), has been observed using DLL sideloading in targeted attacks against accounting and tax preparation firms. Their campaigns often involve socially engineered phishing emails with themes directly relevant to accounting professionals, such as tax audits, invoices, and financial reports.Here’s a step-by-step breakdown of a typical Silver Fox attack:Initial Access:&nbsp;The attack begins with a spear-phishing email sent to an employee at an accounting firm. The email might be disguised as an official communication from a tax authority, complete with a malicious attachment, such as a PDF or a ZIP file. In one documented case, the filename was "The blacklist of tax-related accounting personnel in March is as follows.exe" to entice the victim.Lure and Execution: The user is tricked into opening the attachment. The attachment is a dropper that contains a legitimate, signed executable from a known software vendor (e.g., Tencent, Zeon Corporation, or Thunder Download Manager) and a malicious DLL.DLL Sideloading:&nbsp;The legitimate executable is launched. It needs to load a specific DLL to run, but instead of loading the legitimate one from the system directory, it loads the malicious DLL that the attacker placed in the same directory. For instance, Silver Fox has been known to use ‘ConvertToPDF.exe’ and ‘PDFDirect.exe’ from Zeon Corporation to sideload a malicious DLL named ‘PDFCORE8.dll.’Payload Delivery: The malicious DLL, now running under the trusted process of the legitimate application, decrypts and deploys the final payload. In Silver Fox's case, this is often ValleyRAT, a remote access trojan (RAT).Post-Exploitation: With ValleyRAT installed, the attackers have full control over the compromised system. They can steal sensitive data (client information, financial records), log keystrokes, and deploy further malware.&nbsp; Example 2: REvil Ransomware's Use of DLL SideloadingThe notorious ransomware-as-a-service (RaaS) group,&nbsp;REvil (also known as Sodinokibi), has also employed DLL sideloading to execute its ransomware.Here's how they did it:Initial Compromise: REvil gained initial access to a target's network through various means, such as exploiting vulnerabilities or using stolen credentials.Dropping the Files:&nbsp;Once inside, the attackers would drop two files into a directory on the compromised system: a legitimate, signed Microsoft Defender executable (`MsMpEng.exe`) and a malicious DLL named `mpsvc.dll`.Sideloading the Ransomware:&nbsp;The attackers would then execute `MsMpEng.exe`. This legitimate Microsoft process would then load the malicious `mpsvc.dll`, which contained the REvil ransomware payload.Encryption and Ransom:&nbsp;The ransomware, now running under a trusted Microsoft process, would begin encrypting files on the system and network shares. A ransom note would then be displayed, demanding payment for the decryption key.&nbsp; How Zscaler Endpoint Context Prevents DLL Sideloading AttacksZscaler's cloud-native platform provides a multi-layered defense to proactively stop DLL sideloading attacks before they can compromise an endpoint. Zscaler's approach is multipronged and anchored by our platform’s ability to inspect massive quantities of transactions at global scale to prevent malicious DLLs from reaching users’ devices in the first place.Threat actors leverage DLL sideloading because it abuses the trust placed in legitimately signed executables. Both REvil (Sodinokibi) and Silver Fox (Void Arachne) exploit this: REvil drops a malicious&nbsp;mpsvc.dll alongside an old, validly-signed copy of Microsoft Defender (MsMpEng.exe) to deliver its ransomware encryptor, while Silver Fox uses signed applications like&nbsp;NtHandleCallback.exe or&nbsp;QnWallpaper.exe to sideload encrypted shellcode DLLs (e.g.,&nbsp;log.dll,&nbsp;libcef.dll) that deploy ValleyRAT or Gh0st RAT backdoors.Zscaler Endpoint Context disrupts these attack chains at multiple stages:1. Pre-Execution DLL InterceptionThe Endpoint Sandbox extends Zscaler's cloud-based behavioral analysis to the endpoint itself. Before an unknown or suspicious DLL executes, whether delivered via phishing download, SEO poisoning, or trojanized installer, the sandbox can hold the file, analyze it, and block execution if it is deemed malicious. This stops both REvil's&nbsp;mpsvc.dll drop and Silver Fox's encrypted shellcode DLLs before they ever load.2. Process-Network Correlation to Catch Sideloading AnomaliesEndpoint Context enriches every network transaction with the initiating process name, file path, hash (MD5/SHA-256), and code-signing certificate status. This surfaces the hallmark red flag of sideloading: a legitimately signed binary making suspicious network calls while running from an atypical location (e.g.,&nbsp;%TEMP%,&nbsp;%PUBLIC%, or&nbsp;AppData). A policy can then automatically block or alert on that traffic. For example, flagging&nbsp;MsMpEng.exe calling out to a command-and-control server from a user's Downloads folder.3. Certificate and Hash ValidationBy continuously verifying code-signing status, Endpoint Context detects the "white-plus-black" pattern Silver Fox relies on where a signed host binary loads an unsigned or tampered DLL. Any DLL with an invalid, expired, or missing certificate loaded by an otherwise trusted process is flagged, breaking the chain of assumed trust.4. Application Risk Scoring and Zero Trust Policy EnforcementEndpoint Context assigns dynamic risk scores to running processes based on CVEs, behavioral signals, and vulnerability data. Policies can automatically restrict internet or private-app access for any process with a high-risk classification, preventing post-sideload lateral movement or data exfiltration even if a malicious DLL does load.5. Enriched SOC TelemetryAll process, path, hash, and certificate data is streamed via the Nanolog Streaming Service (NSS) to SIEM tools, giving security teams the correlation context needed to quickly identify sideloading campaigns — without manually pivoting between EDR consoles and network logs. Conclusion and Mitigation StrategiesDLL sideloading poses a significant threat to organizations of all sizes. However, there are steps that can be taken to mitigate the risk:Zsacler Endpoint Context:&nbsp;Monitor for suspicious process behaviors, such as an application loading a DLL from an unusual path, which can help detect sideloading attempts.Application Whitelisting:&nbsp;By allowing only approved applications to run, organizations can prevent unauthorized executables from being used to sideload malicious DLLs.Secure Coding Practices: Developers can help prevent these attacks by specifying the full path to required DLLs in their applications and digitally signing all DLLs.User Education:&nbsp;Training users to be cautious of unsolicited emails and attachments can help prevent the initial compromise that often leads to a DLL sideloading attack.Principle of Least Privilege:&nbsp;Restricting user permissions to prevent files from being written to critical application directories can stop attackers from placing malicious DLLs in the first place.By understanding the mechanics of DLL sideloading and implementing a layered security approach, organizations can better defend themselves against this insidious attack vector. Learn more by&nbsp;requesting a demo.]]></description>
            <dc:creator>Darshit Ashara (Zscaler)</dc:creator>
        </item>
        <item>
            <title><![CDATA[What&#039;s New in ZDX: Sharper Alerts, Cleaner Data, Faster Troubleshooting]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-zdx-sharper-alerts-cleaner-data-faster-troubleshooting</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-zdx-sharper-alerts-cleaner-data-faster-troubleshooting</guid>
            <pubDate>Mon, 12 Oct 2026 20:02:05 GMT</pubDate>
            <description><![CDATA[Every month, Zscaler Digital Experience (ZDX) releases updates that help IT and network operations teams see more, troubleshoot faster, and manage the digital experience of their users at scale.&nbsp;From expanded network architecture support to more granular probe controls, this month's releases reflect what our customers keep telling us: giving teams more precise controls to cut through noise, more accurate data to act on, and a cleaner experience to work in every day.Here's what is new with ZDX:Smarter Alerts for Collaboration Quality MonitoringFilter Dashboards by Data CenterReal User Monitoring ImprovementsConsistent UX with ZDX in Experience Center Smarter Alerts for Collaboration Quality MonitoringFor organizations that rely on real-time alerts to catch collaboration quality issues before they impact users, the granularity of those alerts matters enormously. A generic alert that fires for every region, including ones you know have connectivity variance, creates noise that slows teams down rather than helping them.ZDX now supports expanded filtering and grouping options when configuring collaboration quality alerts. Teams can now apply inclusion and exclusion filters by location, country, city, and other dimensions, the same granularity that is already available for application and network alert types. You can also group alert data by these dimensions to understand whether an issue is localized to a specific office or widespread across a region.The result: Fewer false positives, more targeted notifications, and faster triage when something actually goes wrong.ZDX tier: Available for ZDX Advanced and Advanced Plus customers. Filter Your Dashboards by Data CenterWhen a performance degradation or service disruption is reported at a specific data center location, the first question is always:&nbsp;who's affected, and what is the impact? Until now, correlating a data center event with actual user experience data required workarounds or relying on pre-built system reports.ZDX now lets you filter live dashboard data by Zscaler data center across the Network Intelligence dashboard and other key views. Select one or more data centers from the filter dropdown and immediately see the telemetry from application performance, network path health, device metrics from users egressing through those locations.The result: Network operations teams who need to quickly scope the blast radius of an infrastructure event and communicate impact to the business in real time.ZDX tier:&nbsp;Available across all ZDX license tiers. Real User Monitoring: More Precision, Less AmbiguityZDX's Real User Monitoring capability captures how end users actually experience web applications like load times, errors, navigation flows directly from the browser. The latest update brings a set of meaningful improvements for teams who depend on this data:Clearer load time metrics for single-page applications: Page load time and navigation time are now reported distinctly, so you can understand whether slowness is coming from the initial page load or subsequent in-app navigation events.Multiple errors per session visible: When more than one error occurs during a monitoring window, all error events are now displayed, not just the first one, giving a complete picture of what a user experienced.Consistent score terminology: Score labels across the ZDX interface now use uniform naming conventions, eliminating the ambiguity that came from inconsistent labels across different views.Enriched browser data collection: The browser extension now captures additional resource-level attributes, enabling deeper analysis of web application performance bottlenecks.The browser extension updates automatically with no action needed from end users or IT teams.ZDX tier: Available for ZDX Advanced Plus customers. A More Consistent Console ExperienceWe also completed a significant UI refresh across ZDX. Filters, tables, drawers, time-range selectors, page headers, and other core interface elements have been updated to follow a unified design system, delivering a consistent look and feel whether you're working in dashboards, alert configurations, or device detail views.The change is purely visual and requires no workflow adjustments, but the day-to-day impact is real: a more predictable interface reduces the small moments of friction that slow teams down during active troubleshooting.ZDX tier: Available across all ZDX license tiers. What's NextThese releases reflect a consistent theme across ZDX's evolution: better signal, less noise, and faster paths from detection to resolution. Whether it's more precise alerting, accurate device data, or a cleaner interface to work in, every improvement compounds over time into a meaningfully more efficient operations workflow.Keep an eye out for what's coming in next month’s releases, including updates that will make it even easier to prioritize and respond to issues for your organization's most critical users.See all the latest ZDX releasesAlready a ZDX customer? Log in to&nbsp;ZDX to explore these features.&nbsp;New to ZDX?&nbsp;Learn more about ZDX.]]></description>
            <dc:creator>Cynthia Tu (Sr. Product Marketing Manager, DEM)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Closing the Endpoint Zero Trust Gap]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/ai-endpoint-security-closes-zero-trust-gap</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/ai-endpoint-security-closes-zero-trust-gap</guid>
            <pubDate>Thu, 08 Oct 2026 23:20:47 GMT</pubDate>
            <description><![CDATA[At Zenith Live in Las Vegas, we introduced&nbsp;Zscaler AI Endpoint Security, a new product that extends&nbsp;Zscaler's AI protection to the endpoint. If you already use Zscaler to secure AI usage across your network, cloud, and SaaS applications, this product applies the same zero-trust approach to the AI applications and agents now running directly on your users' devices.This post covers why we built it: what's actually changing on the endpoint, why the tools most organizations already run there aren't designed for this problem, and how Zscaler is approaching it. What we're seeing on the endpointA new AI application layer has been forming on&nbsp;enterprise endpoints, and it has grown faster than most inventory processes can track.It started with&nbsp;frontier AI applications: Claude Code, Cowork, OpenAI Codex, Gemini,&nbsp;Microsoft Copilot. What's notable isn't just the adoption rate; it's who is adopting them. These are no longer developer tools. Finance teams, marketers, and HR teams are using them to do work that previously required a technical specialist, and they're getting real results. That's exactly why this trend won't reverse.The part that concerns security teams is everything these applications bring with them:Configuration and extension sprawl: Plugins, skill files, prompt libraries,&nbsp;MCP servers, subagent definitions, memory files, and background telemetry processes. These components install and update outside your normal software lifecycle.AI-powered IDEs: VS Code, Cursor, and Windsurf, each with extension marketplaces where third-party code runs with the user's full privileges.Local models: Ollama, LM Studio, and llama.cpp put multi-gigabyte model files on disk. We've seen model files that carry serialized code execution, embedded backdoors, content that violates policy, and models renamed to look like something they're not.Package dependencies: Python, npm, and Homebrew packages pulled in by the hundreds to support AI workflows, with the&nbsp;supply-chain exposure that implies.AI assistants and browsers: Tools like OpenClaw, Hermes, and Microsoft Scout, plus AI-enabled browsers such as Chrome, Edge, Comet, and Atlas with embedded models and agent capabilities.Underneath all of this sits the change that matters most:&nbsp;agents act as the user. An agent runs under the user's identity, with the user's permissions, touching the user's files and network connections. When we talk to security teams, this is the point where the conversation usually slows down, because most of their controls and audit trails assume that an action taken under a user's identity was taken by that user. That assumption no longer holds.This is&nbsp;AI asset sprawl: applications that create applications, files created faster than they can be classified, and identities that are no longer only human. Why existing endpoint tools weren't built for thisThe reasonable first question is: don't EDR, DLP, and MDM already cover the endpoint? They do, and none of them should go anywhere. But each one was designed around assumptions that AI asset sprawl breaks. This isn't a criticism of those products. It's a scoping observation.EDR watches files, processes, and threads, and it's very good at recognizing attack patterns and stopping malware and&nbsp;ransomware.&nbsp;But walk through a typical AI incident: a user types a prompt, an agent modifies local files and sends data over the network. From EDR's perspective, there is no malware signature, no process injection, no privilege escalation—just a signed application from a major vendor doing normal application things. The context that would tell you something is wrong lives at the AI application layer: the prompt, the skill file that shaped the behavior, the MCP server involved, the agent's goal. EDR was never designed to see any of that.DLP was built for an environment where you could catalog your files, trace when each was created and modified, and scan content against known patterns.&nbsp;Those steps still work; the environment changed. On an endpoint with active agents, hundreds of new files can appear per minute: generated reports, working datasets, code, memory files. Classification pipelines sized for human document-creation rates fall behind immediately.&nbsp;Lineage breaks too — a file an agent synthesized from six sources and rewrote twice has no ancestry a traditional DLP can reconstruct. And pattern matching struggles when agents constantly reshape and re-encode the data they touch.MDM gave IT a reliable answer to "what is installed on this machine?" Sanctioned apps, managed versions, change control.&nbsp;The new failure mode is simple to state: AI applications create other applications. One prompt produces a finance dashboard app in its own folder. Another folder fills up with PowerShell scripts that modify system settings. None of it went through change management, none of it appears in the software inventory, and MDM has no mechanism to version it or determine what it's for. The gap between what IT believes is on the endpoint and what is actually running there widens every day.The common thread: all three product categories assume a predictable endpoint—known applications, human-speed file creation, human-only identity. AI asset sprawl breaks all three assumptions at once. That's not a feature gap you close with a release; it's a different problem that needs a purpose-built product. How Zscaler AI Endpoint Security worksWe built this product from the ground up for this new AI-native application layer, around the same zero trust principles that run through the rest of the Zscaler platform: verify rather than assume, tie every action to an identity, and enforce policy inline.&nbsp;The Zscaler agent on the endpoint gains visibility into the AI application layer itself, and delivers three capabilities.1. AI Asset InventoryFirst, discovery. The product builds and maintains a&nbsp;complete inventory of AI assets on each endpoint:Frontier model applications (Claude, Codex, Copilot, Gemini)Local model applications (Llama, Ollama, LM Studio, custom models)AI browsers and AI-powered IDEsPackage managers and other channels bringing AI components onto the deviceThe entire ecosystem installed within these apps, including plugins, extensions, skills, and add-onsInventory goes below the application level, to the components that determine what these apps can actually do: config files, skill files and prompts, MCP servers, agent definitions, memory and knowledge stores, model files, telemetry and persistence mechanisms.&nbsp;The output is a structured map of your AI footprint per endpoint, with high-risk findings flagged—unapproved agents, risky plugins, unknown model files, and shadow AI your inventory has never seen.2. AI Agent Runtime MonitoringInventory tells you what's present. Runtime monitoring tells you what it's doing. While AI applications run, Zscaler captures the events that matter at the AI application layer:Prompts and responsesTool and function callsSkill files invoked and MCP servers connectedFile access and data movementProcess and data lineageSystem interactions and network connectionsBecause these events are captured with full context, you can reconstruct a complete agent run—the main agent and every subagent it spawned—and correlate it to identity: which user, which agent, which device, which data. This is the piece that directly addresses the ‘agents act as the user’ problem. When something anomalous happens, you're not left guessing whether the human did it; you can see exactly which agent acted, on whose behalf, and what it touched.3. Enterprise AI Policy EnforcementVisibility on its own doesn't change outcomes, so the third capability is inline enforcement—the control point IT and security teams have been missing on this layer. Policies apply in real time to:Block rogue or unauthorized agents before they actStop malicious skill files and instructionsHalt dangerous commands and code execution via agentsPrevent data exfiltration and protect sensitive or critical filesMonitor and police extensions within frontier AI appsFlag PII inside prompts before it leaves the deviceEnforce acceptable-use, data-protection, compliance, and custom enterprise policies consistently across frontier AI apps, AI-powered IDEs, AI assistants, and AI browsers alikeTaken together: inventory answers “what is here”, runtime monitoring answers “what is it doing,” and enforcement answers “what will we allow.” The same questions zero trust has always asked—now asked of AI assets and agents on the endpoint. Why the need is so urgentThree things convinced us this needed to be a must-build product—and that it couldn't wait.The endpoint is becoming a software factory. "Apps that create apps" is not an edge case we found in testing; it is the stated product direction of every major AI vendor.&nbsp;And it is exactly how AI asset sprawl compounds, as every new application arrives with its own configs, skills, models, and agents. Subagents, background agents, agents embedded in browsers and IDEs: hundreds of agents will soon be running on endpoints on behalf of users, just as they already are in the cloud.&nbsp;Any governance model built on "one identity, one human" stops scaling; agent identity and lineage have to become first-class objects in your security model. The gap between installed software and existing software will keep growing, and only continuous discovery paired with runtime observation can keep up with software that didn't exist an hour ago.Audit requirements are moving toward AI actions. The questions we increasingly hear from compliance teams are concrete: which agent touched this customer data, under whose authority, and what left the device? Those questions can only be answered at the endpoint, at the AI application layer, at runtime. Organizations that can't reconstruct an agent run will struggle to answer them at all.Productivity and competitiveness cannot slow down. Every organization is watching its peers and competitors adopt AI at full speed. Blocking the tools that make employees more productive is not a viable answer because it simply trades a security risk for a competitive one.&nbsp;A security solution built for the AI application layer means people keep doing their best work with the tools that raise the organization's productivity and success, while the enterprise stays in control.We've seen this pattern before. When perimeters dissolved, zero trust replaced castle-and-moat on the network. When work moved to cloud and SaaS, zero trust followed. The AI application layer arriving on the endpoint is the same story, one layer further in. And it's better to have controls in place while the sprawl is measured in dozens of assets per device rather than hundreds.EDR will keep stopping malware. DLP will keep protecting the data it can see. MDM will keep managing the software IT deploys. Keep all three. Zscaler Endpoint AI Security covers the layer none of them see: the AI applications, agents, and assets acting on your endpoints under your users' identities. What's nextZscaler Endpoint AI Security is rolling out to customers now. If you want to see your own endpoint AI footprint—most teams are surprised by their first inventory report—learn more&nbsp;here or reach out to your account team for a demo.]]></description>
            <dc:creator>Dhawal Sharma (Executive Vice President, AI Security and Strategic Initiatives)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Pharma Is Building Again. It’s Time to Put Security in the Blueprints.]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/pharma-building-again-it-s-time-put-security-blueprints</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/pharma-building-again-it-s-time-put-security-blueprints</guid>
            <pubDate>Thu, 08 Oct 2026 15:31:31 GMT</pubDate>
            <description><![CDATA[The onshoring wave is a once-in-a-generation chance to build connected, AI-ready plants the right way. In a GMP plant, most of the security decisions are effectively made before the first batch runs. Somewhere in North Carolina, Indiana, or Pennsylvania this year, a field is turning into a pharmaceutical plant. In a construction trailer at the edge of the site sits a thick binder of user requirements, the document that says what every system in the plant must do. Engineers are signing off on drawings for bioreactor suites and fill-finish lines, and equipment vendors are building skids in their own factories hundreds of miles away. In a few years the site will make medicines that patients depend on, and it will probably still be running long after everyone who designed it has retired.Why now? Mostly pressure. The pandemic showed how much of the US drug supply depends on factories overseas. In 2025 Washington followed with an&nbsp;executive order to speed up approvals for domestic plants, and with the threat of&nbsp;steep tariffs on imported branded drugs from companies that were not building in the US. Drugmakers responded. They announced more than $370 billion in planned US investment during 2025, according to&nbsp;DPR Construction's year-end tally. Not all of it is manufacturing, since the pledges also cover R&amp;D and partnerships, but a large share is concrete, steel, and cleanrooms.A new plant is not a quick project.&nbsp;PhRMA puts it at 5 to 10 years and up to $2 billion from decision to production. Regulators are getting involved earlier as well. FDA's&nbsp;PreCheck pilot is open only to eligible new facilities, and it&nbsp;reviews facility design and equipment qualification before a plant runs its first batch.For the engineers designing one of these plants, that long runway is also a rare chance to start over. They get new equipment, new automation, and a data architecture built for how plants will run in the 2030s rather than how they ran in the 1990s.Security belongs on that list too, and that is a newer idea than it sounds. For most of the industry's history, plant security meant walling the plant network off from the rest of the company and the internet, and hoping the wall held. Three things have changed that:The wall did not hold. In 2017, NotPetya reached Merck through a compromised software update rather than a breach of the plant perimeter. It spread across the company's network,&nbsp;infected more than 40,000 computers, and disrupted manufacturing. The company put the losses at $1.4 billion.A walled-off plant cannot do what it is being built for. These plants are funded on the promise of AI and analytics, and those depend on data leaving the plant floor.Regulators now expect security in the design. Draft updates to the EU's GMP rules ask for segmented networks, controlled remote access, and security requirements written into a system's specification before it is qualified. What are these plants being built to do?These are not copies of the plants they replace. Most are being designed around what ISPE calls&nbsp;Pharma 4.0, an operating model for bringing Industry 4.0 into regulated manufacturing. In practice that means:continuous manufacturing in place of batch-and-hold, now covered by ICH Q13process analytical technology (PAT) that measures quality in the line instead of waiting on the labdigital twins that let engineers test a process change before they touch the equipmentAI is where much of the payoff is expected:Catching deviations early. Models flag a drifting batch from sensor trends before it is lost, instead of leaving an investigation for afterwards.Faster batch release. PAT data, batch records, and lab results come together, so Quality reviews by exception.Predictive maintenance. It focuses on the equipment that sets a plant's capacity, such as lyophilizers, isolators, and bioreactors.Every one of those benefits depends on the same thing. A model cannot flag a drifting batch if it never sees the sensor data. Quality cannot review by exception if the PAT results and the batch records sit in separate systems that never talk to each other. The value comes from data moving: from the skid to the historian, from the site to the cloud, and between the plant and its partners. A plant designed to be walled off cannot deliver any of it.That changes what a plant's IT looks like. Some systems have to stay close to the production line, because a plant must keep making product even if its internet link goes down. The systems that run and release each batch therefore live on site or nearby. That includes the manufacturing execution system (MES), which enforces each recipe step by step, and the local ERP instance, often SAP, that releases finished product.The heavy analytics go the other way. Training a model on years of batch data from a dozen sites takes cloud-scale computing, and it needs every site's data in one place. So a new plant ends up hybrid by design, partly on site and partly in the cloud, and connected all the time.That is the real opportunity. ISPE's Pharma 4.0 model already names&nbsp;data integrity by design as one of its two core enablers. Security by design is the same idea applied to the network. The question for a new plant is not how to keep it disconnected. It is how to connect it the right way, so that the AI business case and the security case become the same design.There is a catch, though, and it arrives on a schedule. So why does the window close so early?In most factories, security is something you can add later. A segmentation project or a new remote-access tool is disruptive, but it is an IT change. A GMP plant is different. Once a system is qualified and the process is validated, almost any change to it goes through change control. The EU's&nbsp;draft revision of GMP Annex 11 is explicit about it. A significant change that could affect product quality, patient safety, or data integrity "should be subject to re-qualification and validation."That is why so much pharma OT still runs old software with known vulnerabilities, even though plant teams are usually well aware of them. The security fix itself is rarely the expensive part. Re-running qualification on a system that is busy making product is.So for a new plant, the security architecture becomes hard and expensive to change once the plant is qualified. Changes are still possible, through impact assessment and, for significant ones, requalification, but few teams take that on lightly. Whatever is on the network when performance qualification is signed, every shared login and every vendor modem included, is what the plant is likely to run with for years.The same Annex 11 draft also adds a full security section. It covers segmented networks with strict firewall rules, timely patching, isolation of unsupported systems, and USB ports deactivated by default. It also says the user requirements specification (URS) should include security requirements and data flow diagrams.&nbsp;The consultation closed in October 2025, and the final text is still pending. Requirements like these are far cheaper to meet in a design document than in a change request.The top row is how most plants get security today: a review after go-live, findings that land in change control, and a choice between revalidation and an accepted risk. The bottom row moves the same requirements into the URS. They are then checked at the factory and site acceptance tests (FAT and SAT), the vendor-shop and on-site checks every system goes through. Finally they are proven in installation, operational, and performance qualification (IQ, OQ, and PQ) alongside the system they protect. What belongs in the URS?Not everything. Controls inside the validated systems themselves are usually best left to the automation vendor and Quality. The six requirements below are the ones that get decided by default if nobody writes them down. Each is cheap to write into the URS and test at FAT, and expensive to add after PQ. The examples use a biologics plant with fill-finish, but the same six apply to most new drug substance or drug product sites.Requirement 1: A named identity for every person and every machine.For people, the regulations already require it.&nbsp;21 CFR 11.10(d) requires limiting system access to authorized individuals, and 11.100(a) requires every electronic signature to be unique to one person. The draft Annex 11 goes further: it calls any shared account that can change data a violation of data integrity. Yet shared operator logins on skid HMIs are still common, because the package unit arrived with one built-in account.Design it out up front. Write named, directory-backed identity for every HMI, engineering workstation, and batch client into the user requirements, so that each OEM has to deliver it at FAT. The regulations stop at people, but the same logic holds for machines, so extend the rule to everything that is not a person:MES-to-skid integrations that download recipes and collect batch datahistorian collectors that poll every controller on the floorservice accounts used by backup, patching, and monitoring toolsAI agents that read process data for analytics and maintenance modelsA new plant will connect more machine identities to batch data than humans. Map which of them can reach the electronic batch record, laboratory information management system (LIMS), and process historian before go-live. That map is the access baseline the plant will be held to.Requirement 2: Zones drawn around unit operations, not Purdue levels.A biologics plant is a collection of package units: bioreactors, chromatography and filtration skids, clean-in-place and steam-in-place (CIP and SIP) systems, isolators, and lyophilizers. Each comes from a different OEM with its own controller, HMI, and network habits. Many plants follow the Purdue reference model by putting all of them in one shared Level 1-2 network. In practice, that network often becomes flat the day the integrator connects the last skid. Once it is flat, anything that compromises one skid, such as an infected vendor laptop plugged into a CIP panel, can reach every other skid, including the bioreactors running product.Start by finding everything. You cannot draw a zone around an asset nobody has inventoried, and package units often arrive with more networked devices than the drawings show. Then zone the plant the way the process is built, using the&nbsp;zones and conduits model from ISA/IEC 62443. Each unit operation gets its own zone. The only conduits are the ones the batch actually needs: recipe download from the batch engine, alarms and data up to the historian, and electronic batch record entries to MES. The cleanroom building management and environmental monitoring systems get their own zone too. They are GMP-relevant, because pressure differentials and particle counts are product-quality data, but they are installed by a different contractor on a different schedule.Requirement 3: One brokered path for every vendor.Picture SAT week. The skids have arrived, and a dozen vendor engineers are on site, each with a laptop, a deadline, and a preferred way in. The automation lead's job that week is to get every system through testing, not to referee remote access.After handover, most OEMs still expect remote support for the life of the equipment. If the plant has not designed that path, each vendor brings their own: a cellular router in the panel, a remote-desktop tool on the HMI, or a VPN nobody inventories. Once qualified, those paths are part of the validated state and very hard to remove.The alternative is to qualify one brokered path that every vendor uses from the first site acceptance test (SAT). Access is tied to a named person and limited to a single asset. It is approved per session, recorded, and closed when the work ends. The vendor never gets a network route into the plant, only a session to the asset they support. The draft Annex 11 already expects multifactor authentication for remote access to critical systems from outside the site. Write the lifecycle into the vendor contracts as well, so that access granted during commissioning is reviewed at handover and expires unless the plant renews it.Zones follow the process, not the Purdue floor. The vendor's dashed path ends at one asset in one zone; it never becomes a route into the plant.Requirement 4: Every inbound file inspected before it reaches a validated system.New plants ingest a steady stream of files. These include recipe packages, OEM firmware and patches, validation protocols, and tech transfer documents from development sites or contract partners. Most arrive by email, file share, or the vendor's laptop, and some still arrive on USB.Route files through a single transfer path that detonates and inspects them before they reach anything validated. Removable media is the honest gap here, since no network control sees a USB stick. The draft Annex 11 is blunt about it: USB use should be strictly controlled, outside media scanned before use, and ports on critical systems deactivated by default. The plant should give vendors a better path than USB from day one, so that locking the ports during qualification is practical.Requirement 5: Outbound data classified and inspected.The most valuable data in a pharma plant is the process: process parameters, batch genealogy, and the analytical methods that prove the product is what the label says. New plants are being built to stream that data out to cloud analytics, digital twins, and AI models for process monitoring and predictive maintenance.That outbound flow needs the same scrutiny as inbound access. Classify process and batch data at the source, and inspect what leaves the plant for where it is going. The EU's&nbsp;draft Annex 22, the first GMP text dedicated to AI, points the same way, with change control and human review for AI used in manufacturing.Requirement 6: Early warning, response, and recovery.A validated plant will always carry some known vulnerabilities, because patching a qualified system takes time even in a plant designed for it. That gap is getting more dangerous. Google's Threat Intelligence Group&nbsp;reported that monthly vulnerability disclosures roughly doubled during 2026, and that attackers are using AI to turn newly published flaws into working exploits faster. Attackers are moving faster, and a GMP plant's patch cycle is not keeping up. Prevention needs a backstop that tells the plant early, and with confidence, that someone is inside.Advanced security capabilities such as deception provide that backstop. Decoy HMIs, engineering workstations, controllers, and credentials are placed in every zone, where no legitimate user or process ever touches them, so any interaction with one is a high-confidence signal.That matters more as attacks become automated. Automated reconnaissance, AI-assisted or not, sweeps whatever it can reach, and that is exactly what a decoy is waiting for. Deception also suits a plant whose security team is often a handful of people rather than a 24x7 SOC.Placed during design, decoys can mirror the real skids and the real zone layout, so they are indistinguishable from production assets. Added years later, they tend to look like what they are.Detection is only the first step, so the URS should also say what happens next:Who hears about it. Alerts should reach both the plant's operations team and security.Quality's role. Quality needs a seat in the response whenever an event could touch a GMP system or a batch record, because Quality decides whether product is affected.The way back. The plant needs local access when the WAN is down. It also needs backups of control logic, configurations, and batch records that have actually been restored and verified. The draft Annex 11 already expects tested restores and a disaster recovery plan with a defined recovery time.Files in, data out, and machine access each pass a check at the boundary. Removable media is the one path no network control sees, which is why the plant has to offer vendors something better than USB before qualification locks the ports. What does doing it right look like?Most existing plants collected security one problem at a time over twenty years: a firewall here, a remote-access tool there, each with its own rules and owner. A new plant can follow a different pattern. Every connection that crosses a boundary goes through a single policy layer: between zones, in or out of the plant, from a vendor, to the cloud, or from an AI system. That layer checks who or what is asking and grants access to a specific asset or application, never to the network around it. Control traffic inside a zone stays local, between the controllers and the systems that run the batch. Because the layer sits around the validated systems rather than inside them, the six requirements can be built and tested without modifying the systems themselves.It is the same idea as data integrity by design, applied to access: decide the rules once, at design time, and make them provable.The Zscaler Zero Trust Exchange is our implementation of that pattern. The six requirements map to one platform and one policy model. It can be verified at FAT and SAT and documented in the qualification package alongside the systems it protects.Every way into or out of the plant passes through the same policy model, whether it is a person, a vendor, a file, a cloud service, or an AI agent. The table maps each connection to the Zscaler capability that covers it.ConnectionWhat it needsZscalerEngineers and operatorsIdentity-bound access to specific applications, never to the networkZscaler Private Access; identity integrationOEM vendors and CDMOsPer-asset, approved, recorded sessionsPrivileged Remote AccessFiles and updatesDetonation and inspection before deliveryCloud Sandbox; sandboxed file transfer in PRACloud analytics and SaaSInline inspection, data classification, DLPZscaler Internet Access with Data ProtectionAI models and agentsOwn identity, mapped and scoped access, AI usage controlsZscaler Access Graph with AI security controlsInside the zonesAsset discovery and agentless segmentation by unit operationZero Trust Branch with device segmentationEarly warningDecoys in every zoneZscaler DeceptionSite connectivitySecure WAN and cellular links with no exposed edge devicesZero Trust Branch; Zscaler CellularWhat this does not replace is the control set on the validated systems themselves. That means audit trails in the MES, recipe locks in the batch engine, and the automation vendor's own hardening. It also does not solve removable media on its own. It gives the plant one enforceable layer around those systems, defined before qualification instead of negotiated after it. The window is nowBack in that field, the drawings are still being signed and the binder in the trailer is still being written. The plant that comes out of them will make medicines for decades, run AI its designers have not imagined yet, and connect to partners that do not exist today. Whether it does that securely depends less on the tools bought in 2035 than on the requirements written this year.Existing plants can still get there, through risk-based change control, one zone at a time, and we will cover that path in a follow-up. But for the plants being designed now, the cheapest security control is a line in the user requirements specification.If you are planning a new site or expansion, the best time to bring us in is front-end engineering design (FEED), before the URS is frozen. Request an OT architecture workshop. You will leave with two things: a zone and data-flow map that your engineering and Quality teams have signed off, and a set of security requirements written to be tested at FAT and SAT. And hear from our customers directly on how they use Zscaler for OT security.]]></description>
            <dc:creator>Bryan Ashley (Zero Trust Networking, Principal Architect)</dc:creator>
        </item>
        <item>
            <title><![CDATA[The End of Legacy Data Classification Is a Zero Trust Opportunity for Federal Government]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/end-legacy-data-classification-zero-trust-opportunity-federal-government</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/end-legacy-data-classification-zero-trust-opportunity-federal-government</guid>
            <pubDate>Wed, 07 Oct 2026 03:45:54 GMT</pubDate>
            <description><![CDATA[Across the Department of War, civilian agencies, and the Intelligence Community, security teams have spent years building data classification and permissions governance programs around on-premises tools. Those tools scanned file shares, monitored user activity, and helped auditors answer a basic question: who has access to what?Now, legacy data classification vendors are retiring their on-premises products and shifting exclusively to cloud delivered models. For some organizations, that transition is straightforward. For federal teams operating in classified, air gapped, disconnected, or otherwise constrained environments, it creates a decision point.&nbsp;Agencies have choices beyond a like-for-like replacement. They can replicate yesterday's static approach. They can reach for familiar fixes, such as bolting on another single purpose appliance or extending legacy VPN and perimeter access to reach new tools, which likely both adds cost and complexity and expands the attack surface. Or they can use the transition to strengthen continuous data visibility, access governance, and risk reduction as their Zero Trust and AI programs advance.Federal guidance supports that broader approach.&nbsp;CISA’s June 2026 zero trust guidance describes decisions informed by identity, device posture, application context, and data sensitivity. The&nbsp;Federal Zero Trust Data Security Guide puts the data-security task plainly: "Practitioners should define their policies based on data sensitivity, identifying who can access the data, under what conditions, and what they can do with it.” In a&nbsp;June 2026 joint statement, the heads of the Five Eyes cybersecurity agencies likewise urged leaders to prioritize reducing their attack surface and review permissions regularly."That modernization must account for wherever the mission runs: in the cloud, in hybrid environments, and in the classified, air gapped, and disconnected networks that much of the federal enterprise depends on. Classification alone was never the whole answerEven before end of life announcements, legacy data classification tools had structural limitations. Most operated on a static model: scan a repository, apply labels, generate a report. That approach answered where sensitive data lived at the time of the last scan, but could not keep pace with how data actually moves through an organization. Classification helps teams identify sensitive data. The broader task is to understand who and what can reach that data, whether access is appropriate, and how exposure changes as data and permissions change.Data Security Posture Management (DSPM) reframes the problem. Instead of static classification alone, DSPM introduces data provenance, which maps exact data lineage and usage over time. It brings discovery and classification together with analysis of access and exposure. It connects data stores to the identities that access them, including human users, non-human identities, service accounts, third parties, and mission partners. It does this continuously, so the picture stays current as the environment changes.For federal organizations, this is the difference between a compliance checkbox and an operational capability. It also matches the direction of the Pentagon’s cybersecurity policy. In March 2026 congressional testimony, Department of War CIO Kirsten Davies said the department will “emphasize automation and dynamic and continuous monitoring” and “drive risk reduction rather than burdensome paperwork”. For the data pillar, that means continuous posture assessment in place of periodic scans, and identity aware access governance in place of static permission reports. Why Data Security Has to Become ContinuousThe real challenge for agencies, therefore, is not simply how to replace a retiring classification tool. It is whether the replacement will support the way federal missions now operate.&nbsp;Traditional categorization programs were built around labels, repositories, and periodic reviews. Those capabilities still matter, but they are no longer enough. Zero Trust requires agencies to understand data sensitivity in context: who is accessing the data, from what identity or workload, under what conditions, and whether that access remains appropriate over time.&nbsp;That shift evolves the mission of data security. Categorization becomes the starting point, not the end state. Agencies need continuous visibility into sensitive data, identity-to-data relationships, excessive permissions, stale or redundant information, and policy violations that increase operational risk. They also need those capabilities to work inside the environments where federal data actually resides, including classified, disconnected, tactical, hybrid, and cloud-connected networks. What Zscaler DSPM deliversZscaler DSPM helps agencies discover sensitive data, map identity to data access, and remediate exposure inside a customer controlled boundary. The approach follows four stages:Discover. Connect to file stores, SaaS platforms, identity sources, and data repositories through agentless, API based, and service account connectors. Sensitive data stays within the operating boundary throughout.Categorize. Apply deterministic rules, local machine learning, and optional customer controlled models to label sensitive data. Classification runs within the customer's environment, not in a third party cloud.Graph. Map human and non human identities to data access, including privileged users, third party contractors, inactive accounts, service accounts, and identities without multi-factor authentication. This identity to data graph is the foundation for understanding who can reach what.Remediate. Right size permissions, reduce stale or misplaced data, and produce the evidence auditors and governance teams need. The output is actionable: specific findings tied to specific data stores, with clear remediation paths and owner assignments. Built for constrained environmentsZscaler DSPM is designed for environments where deployment flexibility is a mission requirement. That includes on-premises installations, VM and container based deployments, classified enclaves, and disconnected or tactical networks. Agencies operating in air gapped or limited connectivity environments do not need to route sensitive data through external cloud infrastructure to gain classification and access governance capabilities.This deployment model directly addresses the friction federal teams encounter when their incumbent vendor's replacement requires connectivity and cloud models that do not fit the operational environment. Zscaler DSPM meets agencies where they operate, under the data boundary constraints, FedRAMP or Impact Level requirements, and RMF/ATO considerations that define federal IT. The AI readiness imperativeThere is a second, equally urgent reason to modernize data security posture now: AI adoption.Agencies across the Department of War (DoW) and civilian government are under pressure to deploy AI, copilots, retrieval augmented generation (RAG) workflows, and agentic systems. Every one of those initiatives depends on access to internal data. Speaking at the 2026 Billington CyberSecurity Summit, acting Federal CISO Michael Duffy described the overlap directly: “The things that I need to advance data security for zero trust, and the things that we need to make data trustworthy and usable for AI are very much aligned. Sometimes even the same things.” Scaling AI safely depends on the organization’s ability to answer three questions:Which data is sensitive, and where does it live?Who and what can access that data today, including AI tools and automated workflows?Are permissions appropriately scoped, or do broad legacy access rights create unacceptable exposure?Zscaler DSPM provides the data foundation that makes AI adoption defensible. By identifying sensitive data, mapping access, and reducing excessive permissions before AI workflows touch mission data, agencies can move from blocking AI adoption to enabling it under governance. Securing data is foundational Zero TrustData security does not exist in isolation. The findings from a DSPM deployment connect directly to broader Zero Trust architecture decisions: which users should have private application access, where data loss prevention controls need to be applied, how identity risk should influence access policy, and where AI guardrails belong.Zscaler DSPM provides the data foundation that powers the rest of the Zscaler Zero Trust Exchange. Agencies can start with data discovery and data access governance, prove value on a specific repository or mission data set, and expand into private access, data protection, identity risk scoring, and AI security as the program matures. A practical next stepThe retirement of legacy on-premises classification tools is already underway. For agencies with active compliance mandates, the priority is standing up a modern replacement that meets their deployment, security, and governance requirements before the control gap widens.A practical starting point: a 30 to 45 day data risk assessment focused on one mission data enclave or repository family. The assessment delivers an executive readout covering sensitive data exposure, stale and redundant data, excessive permissions, user activity patterns, and AI access control implications. That readout becomes the basis for a broader deployment, grounded in measurable risk reduction and a clear path to operational value.Ready to move forward? Contact the Zscaler Federal team to schedule a Data Security and AI Readiness Workshop.&nbsp;]]></description>
            <dc:creator>Andrew AJ Forysiak (Field CISO DOD)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Beyond VoIP and SCCM: Securing Legacy Applications with ZPA]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/beyond-voip-and-sccm-securing-legacy-applications-zpa</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/beyond-voip-and-sccm-securing-legacy-applications-zpa</guid>
            <pubDate>Tue, 06 Oct 2026 17:00:00 GMT</pubDate>
            <description><![CDATA[Beyond VoIP and SCCM: Securing Legacy Applications with ZPAVPN for Legacy Apps started with VoIP and server-to-client apps like SCCM. New capabilities now extend it to support full zero trust access to IP address dependent systems like mainframes, multi-entity organizations and complex routing environments, so more of your legacy estate can move to Zscaler Private Access (ZPA).Most organizations moving from a traditional VPN/Firewall to zero trust reach the same point: user-to-app traffic moves to ZTNA easily, but a set of legacy apps keeps the old VPN concentrator or NGFW running. VPN for Legacy Apps in ZPA closes that gap. It gives those apps a home on the Zscaler Zero Trust Exchange, delivered through the same Zscaler Client Connector users already have. You can move off your traditional VPN vendor completely, with one agent, one policy framework and one platform for all private access, instead of running Zscaler and legacy VPN solutions side by side.Why the last mile of VPN migration is the hardestIn our&nbsp;earlier post, we introduced VPN for Legacy Apps in ZPA. It covers the applications that have challenges with&nbsp; zero trust design: Cisco Jabber, Avaya and Genesys VoIP, SCCM, follow-me printing and active FTP. These apps need the server to reach back to the client, and many expect a fixed client IP. That is why the VPN concentrator stays on long after everything else has moved to ZTNA.As more customers move these apps onto ZPA using VPN for Legacy App solution, they have told us what would make large migrations even smoother: onboarding large VPN configurations quickly, supporting systems that expect a fixed client IP, bringing acquired companies onboard on their own terms, and fitting cleanly into existing routing.Over the last few releases, we have delivered a set of features that address each of these needs and open VPN for Legacy Apps to use cases beyond where it started. Together, they make onboarding a legacy app to ZTNA as simple as adding it to your VPN, so you can retire your legacy VPN concentrators with confidence.Expanded use-case coverageThe first set of capabilities removes common blockers that keep legacy apps on the VPN, while making onboarding and day-to-day operations simpler.1. User group-based access policyLegacy VPN access is often defined by IP ranges alone, which says little about who is actually connecting. Access policies for VPN for Legacy Apps can now use IdP group attributes alongside existing IP criteria. Admins can grant access to a legacy app based on who the user is (for example, the finance or contact-center group), not just which network range they target and coming from.2. FQDN wildcard support: onboard everything, then migrate in phasesA typical VPN configuration covers a large number of hosts and domains, and discovering and rebuilding each one as an exact ZPA segment before cutover takes time. One missed host can break a VoIP callback or an SCCM push with no obvious cause. Network segments now support wildcard FQDNs, such as *.acme.com, so a single definition covers your legacy destinations on day one. You can move all of your VPN traffic to Zscaler in one step and retire the VPN, with users working just as they did before. From there, migrate to ZTNA at your own pace: use ZPA visibility to see which apps are really in use, then carve out specific network segments with least-privilege policies, one app group at a time. Upfront discovery and rework drop sharply.3. Static IP assignment to users: keep IP-based controls workingMainframes and many other legacy systems still trust an IP address. Firewalls, application allowlists and licensing servers key on the client IP, and regulated teams need a stable user-to-IP mapping in their logs. Admins can now statically map a user to an IP address, so the user gets the same address every time they connect to VPN for Legacy Apps. Security teams can track the user by IP across enterprise systems, allowlist-based apps keep working, and IP-based firewall rules need no rewrites. Banks, healthcare providers and other regulated teams keep a consistent user-to-IP record for audit and compliance.4. Micro-tenancy: isolation inside one ZPA tenantMergers, acquisitions and multi-campus organizations bring separate VPN estates, each with its own apps, admins and policies, and often overlapping RFC 1918 address space. VPN for Legacy Apps now works with ZPA Microtenants, which provide isolation inside a single ZPA tenant. Each subsidiary, acquired business or campus can run its legacy app segments, Network Connectors and policies in its own microtenant, on its own timeline, even when its private address ranges overlap with others. Microtenants can also share network segments with each other, with granular control over which segments are shared and with whom. Central IT keeps one platform and one view, while each business onboards fast.5. BGP summary routes: simpler routing integrationPreviously, the customer's router had to advertise prefixes that exactly matched each ZPA segment, so every new or changed segment meant a router change request and coordination between security and network teams. Now your router can send a single summary route to the Network Connectors. Network Connectors then use conditional routing to advertise the specific routes that match your configured segments. For example, if the router sends 10.1.1.0/24 and the network segment is 10.1.1.1, the Network Connector advertises only 10.1.1.1/32. The network team configures BGP once, and the security team adds or changes network segments in ZPA without opening a router ticket.Enterprise-ready: resiliency, control and visibilityWith these capabilities, VPN for Legacy Apps goes beyond the handful of use cases to supporting all the use cases large enterprises run needGet Started: ZPA Trial for VoIP and Legacy Application Zero Trust MigrationZPA now supports VoIP, server-to-client (S2C) applications, and all IP address dependent use-cases. This enables customers to move all their applications and streamlines operations by consolidating their secure remote access solution with Zscaler Private Access.&nbsp;Check out the&nbsp;latest product innovations with ZPA in addition to network connectivity. And read the&nbsp;Forrester Total Economic Impact study to learn how ZPA customers have realized 289% ROI.&nbsp;Contact your regional sales team to learn more about the solution and get a free 30 day trial to explore the solution, or&nbsp;take a quick tour.&nbsp;&nbsp;]]></description>
            <dc:creator>Megha Tamvada (Director, Product Management)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Bringing Anthropic&#039;s Claude Mythos 5.1 to Zscaler Endpoint AI Security]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/bringing-anthropic-s-claude-mythos-5-1-zscaler-endpoint-ai-security</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/bringing-anthropic-s-claude-mythos-5-1-zscaler-endpoint-ai-security</guid>
            <pubDate>Tue, 06 Oct 2026 04:24:20 GMT</pubDate>
            <description><![CDATA[AI adoption inside the enterprise is increasingly bottom-up: employees are trying the latest AI assistants, coding agents, browsers, and development tools because these products help them get work done. Many of these tools arrive before central security or IT teams have evaluated them.The result is a sprawl of shadow AI: a fast-growing layer of applications, agents, extensions, models, packages, and configuration files on employee devices. This activity changes quickly and often falls outside the software rollout processes organizations use for traditional applications.Today, Zscaler is announcing the limited preview availability of Anthropic's Claude Mythos 5.1 capabilities in Zscaler Endpoint AI Security. Mythos 5.1 powers Exploit Paths, helping security teams connect related endpoint AI activity, identify potential attack paths, and determine where to intervene.&nbsp;With this addition, Zscaler better helps security teams turn disconnected endpoint events from different AI apps, across all users, into an attack chain analysis view of potential threat vectors. By correlating multi-stage AI behaviors into visible attack paths, security teams can leverage intelligent prioritization to proactively block risky agent activities, secure sensitive data, and enforce real-time policy controls directly at the endpoint. Why MDM and EDR leave a visibility gapMDM and EDR remain essential parts of endpoint security, but they were built to answer different questions. MDM helps organizations manage applications, devices, and configurations. EDR monitors processes, files, network activity, and known attack behavior.AI agents introduce a different kind of endpoint activity. They can act on a user’s behalf using the user’s identity and permissions, call tools, access files, run commands, and connect to services as if the user performed those actions directly. As a result, audit logs may attribute agent activity to the user’s account, making it difficult to separate what the user did from what an agent did on the user’s behalf.At the process or file level, this activity can look normal. A signed application may modify a file, run a command, or send data over the network without matching a malware pattern. The missing context often lives inside the AI application layer: which agent acted, what task it was performing, which tool it called, what data it used, and which extensions, models, packages, or connected services were involved.Endpoint AI Security was built to close this gap. It secures the AI activity layer on the endpoint — where AI apps, browsers, assistants, coding agents, and other agentic tools are creating new risks that traditional endpoint tools were not designed to interpret or control. How Zscaler Endpoint AI Security closes the gapZscaler Endpoint AI Security is designed to secure this AI application layer across users and managed devices. It combines all three pillars critical to securing employee devices using AI: discovery, runtime visibility, and policy enforcement.Discover AI assetsSecurity teams first need to answer a basic question: What AI is running across the organization?Endpoint AI Security identifies AI assistants, agents, browsers, development tools, models, packages, extensions, and connected services used across managed devices. This provides visibility into AI assets that may not appear in traditional application inventories.See what agents are doingInventory shows what is present. Runtime visibility shows what is happening.Endpoint AI Security captures the events that matter during an agent run, including prompts, tool calls, file access, commands, system interactions, and network activity. It connects those events to the user, agent, and device involved.Enforce enterprise AI policyVisibility becomes useful when it can change an outcome. Endpoint AI Security provides a policy layer for controlling AI activity on the device.Policies can restrict unauthorized agents and tools, stop dangerous commands or instructions, and protect sensitive files and data. This gives security teams a way to support AI adoption while keeping enterprise rules in effect at the endpoint. The challenge of connecting activity at enterprise scaleDiscovery and runtime monitoring produce detailed evidence. That evidence is distributed across users, devices, agents, tools, and individual runs.The challenge is understanding how these activities connect. Broad agent permissions, use of a third-party tool, or access to a sensitive file may each appear manageable in isolation. When these conditions occur in the same sequence, they can combine into a more serious risk.Reviewing each event separately makes that relationship easy to miss. Security teams need a way to cross-correlate the activity, recognize possible attack progression, and determine which response will reduce the most risk. What Mythos 5.1 addsMythos 5.1 powers a critical capability within Endpoint AI Security, Exploit Paths, which cross-correlates evidence to identify potential threats, explain how the steps connect, and show defenders where to interrupt the sequence.Each path shows the evidence behind the analysis, how confident the assessment is, and where a step is inferred rather than confirmed. It also identifies how a defender could recognize the activity and where to break the chain of attack.This adds context that individual alerts cannot provide. Security teams can categorize risk based on the complete path, understand why a group of findings matters, and prioritize the control that can interrupt the sequence.Endpoint AI Security and&nbsp;Mythos 5.1 have distinct roles. Endpoint AI Security discovers AI assets, records agent activity, and provides the policy enforcement point.&nbsp;Mythos 5.1&nbsp;analyzes that evidence, connects related conditions, and identifies the attack paths that deserve attention. What this looks like in practiceConsider an AI agent with broader permissions than its assigned role requires. During a run, it calls a third-party tool and accesses files containing sensitive information. Endpoint AI Security records the agent, the user and device involved, the tool call, and the file activity.&nbsp;Viewed in isolation, these events may not reveal the full risk.&nbsp;Mythos 5.1 correlates the findings to determine whether they form a credible sequence. Exploit Paths shows how the agent’s permissions, use of a third-party tool, and access to sensitive files could combine into an attack path. The report presents the supporting evidence, identifies any inferred steps, and recommends where defenders should intervene.The security team can then use Endpoint AI Security policy controls to restrict the agent or tool, stop risky activity, or block access to sensitive data.&nbsp;Mythos 5.1 provides the analysis and prioritization, while Endpoint AI Security provides the visibility and enforcement. Turning evidence into actionExploit Paths is designed for defensive assessments of environments customers are authorized to protect. It presents prioritized findings without exposing raw model responses or generating working exploit code or payloads. Security teams review the evidence and decide how to respond. By bringing&nbsp;Mythos 5.1 into Endpoint AI Security, Zscaler helps security teams turn disconnected endpoint events into a focused view of potential attack paths.&nbsp;“AI agents are rapidly becoming part of everyday work. But they also introduce a new layer of endpoint activity that security teams need to understand and control. By embedding&nbsp;Mythos 5.1 in Zscaler Endpoint AI Security, we are helping customers connect agent behavior, tool use, and data access into clear exploit paths so defenders can prioritize the actions that reduce the most risk.”— Dhawal Sharma, EVP AI Security, Zscaler“Bringing Claude Mythos 5.1 into Zscaler's Endpoint AI Security helps enterprise security teams reason over complex AI activity in a defensive, evidence-based way. This makes it easier for organizations to adopt AI tools confidently while maintaining the visibility and safeguards they need.”–&nbsp;Ash Alhashim, GTM Leadership Cybersecurity, Anthropic&nbsp;With this addition, security analysts can see how AI risk develops across agents, tools, and data on the endpoint. As those signals come together, Exploit Paths shows where risk is forming and where intervention will matter most. With proven Zscaler policy controls, teams can interrupt risky activity before it causes business impact. The result is a safer path to enterprise AI adoption - with visibility, control, and protection on every managed employee device.​​To learn more about Zscaler Endpoint AI Security or request a demo, visit&nbsp;https://www.zscaler.com/request-a-demo..]]></description>
            <dc:creator>Dhawal Sharma (Executive Vice President, AI Security and Strategic Initiatives)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Don’t Wait for Game Film: Audit Your Cloud Red Zone]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/don-t-wait-game-film-audit-your-cloud-red-zone</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/don-t-wait-game-film-audit-your-cloud-red-zone</guid>
            <pubDate>Tue, 06 Oct 2026 01:54:46 GMT</pubDate>
            <description><![CDATA[Game film is how football teams learn from what already happened. It’s valuable, and it’s expensive, because the lesson arrives after the score.Most cloud security reviews work the same way. Teams wait for an incident, a breached database, or a hard audit finding to reveal where the perimeter lapsed.AI workloads shorten that timeline.&nbsp;Zscaler ThreatLabz research found that enterprise AI/ML transaction volume grew 83% year over year in 2025, while data transfers to AI/ML applications rose 93% to more than 18,000 terabytes. Each new AI workload is provisioned quickly, typically needs broad outbound access to pull models and public data, and lands on a network that grants connectivity by default.The&nbsp;OpenAI–Hugging Face incident is the game film. During an internal evaluation in July 2026, AI models escaped their sandbox through a zero-day vulnerability in a package registry proxy, the only outbound path the environment allowed,&nbsp;according to OpenAI. From there, they moved laterally until they reached a node with internet access and used stolen credentials to reach Hugging Face production infrastructure.&nbsp;Hugging Face’s own disclosure describes an attacker log of more than 17,000 recorded events. This post is the scouting report: three repeatable checks you can run this quarter across AWS, Microsoft Azure, and Google Cloud to find exposure before an attacker does. Why Cloud Networks Hand Out Connectivity FirstCloud networks are engineered to connect, and default configurations typically favor reach over restriction. Security boundaries usually arrive later, negotiated through a ticket queue or an exception request.AI workloads strain that model in three ways:Broad external pulls: AI clusters routinely pull models, weights, datasets, and dependencies from public repositories.Shadow provisioning: Data science and ML teams often stand up environments outside standard architecture review to keep momentum.Data proximity: AI applications run next to sensitive production data stores and analytics pipelines for training and inference.Defenses rarely fail because of one missed assignment. They fail because small, uninspected gaps compound over time. Cloud risk builds through convenience routes and standing exceptions, not a single catastrophic decision. The three audits below are designed to uncover that accumulation. 1. The Egress Audit: Where Can Your Workloads Reach?Start with the exits. Every offense hunts for the open receiver behind the secondary. In the cloud, that open receiver is the outbound path nobody inspects. In the Hugging Face incident, it was a package registry proxy.What to Look ForList every route table that sends 0.0.0.0/0 through a NAT gateway or internet gateway across your cloud environments. Cross-reference that list against 30 days of VPC/VNet flow logs to verify which external destinations your workloads actually contacted.Pay close attention to AI pipelines pulling from public registries.&nbsp;Sonatype’s 2026 State of the Software Supply Chain report identified more than 454,600 new malicious open source packages in 2025, a 75% increase over the prior year, bringing the cumulative total it has tracked past 1.2 million as of year-end. Sonatype also notes that developer machines and CI/CD environments are prime targets because they sit close to credentials and production access. Common Pattern:&nbsp;The&nbsp;Cloud Security Alliance notes that development teams routinely pull foundation models, fine-tuned adapters, and other AI artifacts directly from public registries, often without the scrutiny applied to traditional software dependencies. In cloud terms, that often looks like AI and data science environments using a default NAT path to the internet with no inspection, which leaves a blind spot for data exfiltration and dependency poisoning. Why It MattersEncrypted, uninspected egress gives a compromised host a covert channel. Command-and-control (C2) traffic and data exfiltration can blend in with legitimate outbound TLS and slip past controls that do not decrypt and inspect it.The litmus test for security leaders is simple:&nbsp;Can your team name every external service, IP, and repository your cloud workloads contacted last week?How to Fix ItReplace open default routing with inline TLS inspection and destination allowlists scoped to each source workload’s identity.With Zscaler Zero Trust Cloud (ZTC), workload outbound traffic is steered from the local VPC or VNet to the Zero Trust Exchange, either through the Zero Trust Gateway service, which Zscaler fully manages, or through Cloud Connectors you deploy yourself. There, connections get cloud-scale TLS decryption, granular URL and FQDN filtering, and inline data loss prevention (DLP). That blocks unauthorized package acquisition and data leakage before traffic leaves your boundary. 2. The East-West Audit: What Can a Compromised Workload Touch?Next, test your interior. In a disciplined defense, every player covers a gap. In a flat cloud network, nobody is assigned to the middle of the field.What to Look ForPick a low-trust workload, such as a developer sandbox, an edge analytics container, or an experimental AI notebook, and map everything it can reach. Review peering relationships, transit gateway route tables, cross-account and cross-subscription connections, and security rules that allow broad CIDR ranges (for example /16 or /12).Then run an active reachability test: try to connect from that low-trust host to a production database subnet. Never assume the configuration blocks the hop until you have tested the path. Common Pattern:&nbsp;Segmentation built on security groups, ACLs, and address ranges tends to be static and hard to keep accurate as environments change. Rules written against broad ranges instead of specific workloads are a familiar way for a path to production data to stay open long after the team believes it is closed. Why It MattersInternal reach determines your blast radius. It marks the line between an isolated compromise of a developer sandbox and a breach of sensitive customer records. Lateral movement is a common feature of ransomware and other multi-stage attacks, and it was central to the Hugging Face incident. It also happens fast:&nbsp;CrowdStrike’s 2026 Global Threat Report found that the average eCrime breakout time, the window between initial access and lateral movement, fell to 29 minutes in 2025, with the fastest observed breakout at 27 seconds.How to Fix ItRetire position-based network controls in favor of workload identity and explicit 1-to-1 microsegmentation.With ZTC, east-west traffic between workloads within a region is enforced directly at the Zero Trust Gateway or Cloud Connector. Flows that extend beyond a single region, such as cross-region, multi-cloud, or hybrid data center traffic, can be handled at the Gateway or Cloud Connector, or routed through the Zero Trust Exchange for a full proxy-based solution. Either way, workloads communicate only with pre-approved endpoints, which removes the open paths that unauthorized lateral movement depends on. &nbsp; 3. The Launch Audit: What Does a New Workload Inherit?Championship teams build defensive discipline in the first practice, so every player knows the assignment long before game day.What to Look ForDeploy a test workload from your standard infrastructure-as-code (IaC) templates, whether Terraform, AWS CloudFormation, Azure Bicep, or Google Cloud Infrastructure Manager. Check whether it launches with egress controls and isolation active, or falls back to open cloud defaults.Then audit tag and label governance. Are the metadata tags that drive policy enforcement validated as mandatory gates in your CI/CD pipeline? Common Pattern:&nbsp;Templates often define compute and networking but leave egress and isolation policy to a follow-up step. Any control that depends on a manual follow-up is the first to slip when a deadline is tight. Why It MattersCloud infrastructure provisions in seconds. A manual cleanup done today is stale by the next deployment cycle, and any control that depends on a ticket or a human step will eventually lapse. Enforcing policy at deployment turns one-off remediation into a sustained security posture.How to Fix ItAnchor security policy to&nbsp;workload identities and cloud tags from the moment an instance starts. ZTC’s workload discovery service reads user-defined tags and cloud metadata, such as network, subnet, security group, and image attributes, across AWS, Azure, and Google Cloud. It picks up each new workload’s identity as soon as it launches, so policy applies from the start.Because policy keys off these tags and attributes, tag hygiene becomes a security control. Enforce mandatory tags with native guardrails (AWS tag policies and SCPs, Azure Policy, Google Cloud Organization Policy), and pair them with automated pipeline checks. If a workload template lacks the mandatory security tags or routes traffic through an uninspected gateway, fail the build before anything is provisioned. Where to Look Across AWS, Azure, and Google CloudShare this reference table with your cloud engineering and platform security teams to run each audit:Audit CheckAmazon Web Services (AWS)Microsoft AzureGoogle Cloud (GCP)1. Egress PathsRoute tables with 0.0.0.0/0 to NAT Gateways or Internet Gateways; VPC Flow LogsRoute tables with 0.0.0.0/0 to Internet or virtual appliance next hops; NAT Gateway associations; VNet Flow LogsDefault routes (0.0.0.0/0) to the default internet gateway; Cloud NAT configurations; VPC Flow Logs2. East-West ReachTransit Gateway route tables; VPC Peering connections; Security Group ingress CIDRsVirtual Network Peering; hub-and-spoke routing configurations; NSG inbound rulesVPC Network Peering; Network Connectivity Center spokes; VPC firewall rules3. Policy at LaunchTerraform modules; CloudFormation templates; AWS resource tags; AWS Config rules; SCPsTerraform modules; Bicep templates; resource tags; Azure Policy definitions and tag enforcementTerraform modules; Infrastructure Manager; labels and network tags; Organization Policy Service&nbsp; What Skipping the Audit CostsThe cost of unmanaged cloud exposure rarely shows up as a line item until an incident happens. Before that, it accumulates quietly in your change-management backlog.When the bill does arrive, it is large.&nbsp;IBM’s 2026 Cost of a Data Breach Report puts the global average breach at a record $4.99 million. Among organizations that suffered an AI-related breach, 92% lacked proper AI access controls, and only 40% of all breached organizations applied access controls to AI models and data at all.Every new outbound destination, partner connection, or AI data source needs an infrastructure change ticket. Requests back up, deadlines loom, and engineering teams look for routes around the perimeter. Each detour can become a standing exception: a broad CIDR allowance, an uninspected NAT gateway, a disabled firewall. Those exceptions are exactly what the egress and east-west audits reveal. Common Pattern:&nbsp;When approval queues for new destinations run long, teams tend to build their own workarounds rather than wait. Unmanaged paths tend to appear wherever enforcement gaps meet developer convenience and automation. Security leaders should treat standing exceptions as a leading risk indicator. The exception count shows how much of your production footprint already operates outside your security baseline. Conclusion: Watch the Film Before the GameGame film shows where an opponent broke through last week. A structured audit shows where your architecture is exposed right now.Schedule these three checks this quarter. Start with the workload tier that has the highest velocity, the most connectivity freedom, and the fewest architecture reviews: your AI and data science environments.To see how enterprises close these gaps with cloud-native workload protection, explore&nbsp;Zscaler Zero Trust Cloud.]]></description>
            <dc:creator>Brian Pavane (Senior Director, Specialist Solution Architect)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Browser Detection and Response: Why Your Security Stack Needs Eyes Inside the Browser]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/browser-detection-and-response-why-your-security-stack-needs-eyes-inside</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/browser-detection-and-response-why-your-security-stack-needs-eyes-inside</guid>
            <pubDate>Mon, 05 Oct 2026 17:03:25 GMT</pubDate>
            <description><![CDATA[Employees spend the majority of their productive working hours in a browser. They access SaaS applications, collaborate on documents, authenticate into corporate systems, and paste sensitive data into GenAI tools, all through a single application that most security teams barely monitor.Meanwhile, attackers have noticed. The browser is now a prime target, and the techniques being used against it are evolving faster than the defenses in front of it.The industry has documented a growing catalog of in-browser attack techniques: adversary-in-the-middle (AiTM) phishing, malicious OAuth grants, hijacked extensions, ClickFix social engineering, and session token theft. At the same time,&nbsp;Microsoft's Work Trend Index found that 78% of AI users at work are bringing their own AI tools without IT approval, introducing data exposure channels that legacy controls were never designed to see.The common thread across all of these threats is that they live and die inside the browser. They do not trigger file downloads. They do not create suspicious processes on the endpoint. They often bypass URL reputation lists entirely. And that makes them invisible to the tools most organizations rely on. Why Your EDR and Network Security Stack Can't See What's HappeningEndpoint detection and response (EDR) tools focus on inspecting files and processes at the operating system level. Detection begins when a malicious file lands on disk or a suspicious process spawns. But many of today's browser-based attacks never reach that threshold.A credential phishing page that renders a fake login portal inside an iframe does not write anything to the endpoint. An AiTM proxy that intercepts session tokens operates entirely within the HTTPS session. A compromised browser extension that scrapes DOM content and exfiltrates it over standard HTTPS generates no anomaly at the network perimeter. The&nbsp;Cloud Security Alliance's AI Safety Initiative put it plainly in April 2026: "Traditional enterprise defenses, DLP, CASB, and EDR, have limited or no native visibility into DOM-level browser extension behavior."Network security tools face similar constraints. Secure web gateways and firewalls inspect traffic at the network layer, relying on URL categorization, domain reputation, and signature-based detection. These controls work well for known threats. They struggle with attacks that abuse trusted infrastructure: phishing campaigns served from compromised legitimate domains, multi-hop redirects gated behind CAPTCHAs, and scripts that execute conditionally based on whether the visitor is a real user or a security scanner.The result is a structural blind spot. The browser processes identity decisions, renders sensitive content, executes third-party code via extensions, and mediates clipboard activity. None of that activity is visible to tools operating below or outside the browser process. The Attack Surface Has Expanded QuietlySeveral shifts have widened this gap without most security teams noticing.Extensions became powerful and exploitable. Modern browser extensions interact with web pages through the Document Object Model (DOM), store data locally, integrate with third-party services, and fetch data across multiple applications using browser APIs. Attackers have learned to weaponize this power. In January 2026,&nbsp;Socket researchers uncovered five coordinated Chrome extensions targeting enterprise HR and ERP systems, exfiltrating session cookies and blocking security administration pages to prevent detection. The&nbsp;Cyberhaven supply chain attack followed a similar playbook: a phished developer credential led to a malicious extension update pushed silently to millions of installed instances. Extension whitelisting, the most common management strategy, offers no protection when a previously trusted extension turns malicious after an acquisition or account compromise.Personal and work activities share the same browser. Employees access the same browser for corporate SaaS apps and personal email, file storage, and social media. This overlap creates policy challenges that go beyond traditional allow/block decisions. A user might paste sensitive financial data into a personal Google Drive, or log into a shadow SaaS tool with corporate credentials, and neither action generates an alert in most security stacks.AI tools introduced new data exposure channels.&nbsp;A TELUS Digital Experience survey found that 57% of enterprise employees have entered confidential information into publicly available GenAI tools. Copy-pasting source code into a GenAI chatbot, uploading internal documents to an AI summarization tool, or entering customer PII into an AI-powered form: all of these actions happen inside the browser session, beyond the reach of network-layer controls. What Browser Detection and Response Actually MeansAddressing this blind spot requires detection and response capabilities that operate where the attacks happen: inside the browser itself.Zscaler’s industry-first&nbsp;Browser Detection and Response (BDR) technology monitors, detects, mitigates, and enables threat hunting for client-side web attacks in real time. The Zscaler Zero Trust Browser delivers BDR in two deployment models: as a lightweight browser extension that can be pushed via standard group policy (through tools like Microsoft Intune or Jamf) to existing browsers like Chrome, Edge, Safari, and Firefox, and as a full Zscaler Browser for organizations that want a purpose-built enterprise browser with BDR capabilities built in from the ground up. Both options deliver the same core BDR protections, giving security teams the flexibility to meet users where they are or standardize on a managed browser, depending on their security posture and workforce requirements.Monitor: Visibility That Goes Beyond Network LogsBecause BDR operates inside the browser, it captures signals that network and endpoint tools cannot: DOM mutations, website permission changes, browser API calls, user events, file uploads and downloads, clipboard activity, extension behavior, and WebAssembly execution. This telemetry provides the raw material for detecting attacks that never touch the file system or generate suspicious network signatures.Detect: Covering the Five Critical Attack VectorsBDR detection spans five categories that map directly to how attackers exploit the browser today:Sites. Beyond URL filtering, BDR performs real-time analysis of user-browser interaction, content inspection, and DOM changes. This catches advanced techniques like Browser-in-the-Browser (BiTB) attacks, CAPTCHA-gated phishing, and multi-hop redirect chains. Zscaler's BDR detects over 90 unique web attack types using this approach.&nbsp;Files. A client-side file scanner intercepts and inspects every file before a download reaches the endpoint, detecting malicious payloads without sending the file to an external server. On the upload side, it inspects files for PII and sensitive content to prevent data loss through personal accounts.&nbsp;Extensions. Rather than relying on static whitelists, BDR inspects extension behavior and permission changes in real time. When a previously benign extension starts scraping session cookies or injecting scripts after an update, BDR detects and blocks the activity automatically.&nbsp;Identity. Granular policies govern which SaaS applications and authentication methods each user can access, preventing unauthorized OAuth grants, shadow SaaS usage, and credential reuse across sites. This directly addresses the AiTM and device code phishing techniques that have surged recently.&nbsp;Clipboard. Content inspection on copy and paste operations prevents sensitive data from moving to unauthorized destinations: blocking paste into GenAI prompts, preventing copy from enterprise applications, and enforcing policies on a per-site basis.&nbsp;Mitigate: Responses That Keep Users WorkingBDR focuses on detecting and surfacing browser-based threats. When a threat is identified, the Zero Trust Browser provides graduated mitigation options beyond simple allow and block, enabling employees to continue working in a safe environment.For suspicious or risky web content, administrators can set policies to automatically open flagged sites in an isolated session, where all page rendering, script execution, and active content run in a secure cloud container rather than on the user's device. Content is streamed back to the user as safe images, so employees can continue browsing while code execution, exploits, and malware delivery are contained away from the endpoint. This is particularly useful for individuals who travel frequently, such as sales teams, and need secure, disposable browsing sessions while on the road.Isolation also provides a safety net for unmanaged and BYOD devices. Because isolated sessions deliver images rather than raw HTML and JavaScript, contractors and employees on personal laptops can access sensitive applications without exposing the endpoint to malware or data exfiltration. Security teams can further tighten these sessions by restricting clipboard operations, disabling downloads, or blocking uploads on a per-policy basis.The combination of BDR's in-browser detection with isolation capabilities creates a layered defense: threats are identified where they execute (inside the browser), and then contained before they reach the endpoint or the network.Threat Hunt: Enterprise-Wide Attack IntelligenceBDR provides security teams with capabilities that go well beyond alert triage:Attack graphs map the full sequence of sites visited and actions taken before a policy triggered, revealing the attack path in detail.Attack correlation connects related campaigns across the organization, identifying when the same adversary targets multiple employee groups simultaneously.Attack Vision uses DOM reconstruction to replay exactly what a user saw and did in the 30 seconds before a policy hit, giving security teams a definitive view of whether a breach resulted from negligence or malicious intent.A built-in co-pilot generates plain-language reports for each incident, describing what happened, who was affected, and recommended remediation steps. Why This Matters NowThe traditional approach to browser security has been reactive: block known malicious domains, maintain a static extension whitelist, and hope the EDR catches anything that slips through. That approach was designed for an era when the browser was one of many applications on the desktop, not the primary place where work, data access, and authentication converge.The shift to browser-as-workplace happened gradually. The security response needs to catch up. With AI-generated phishing now representing&nbsp;more than 80% of observed social engineering activity according to ENISA's 2025 Threat Landscape report, with extension supply chain attacks growing in scale, and with GenAI tools creating new data loss vectors every week, waiting for threats to reach the endpoint or trigger network signatures means accepting that the most consequential attacks will go undetected.BDR closes this gap by placing detection and response where the attacks actually execute. As a core capability of the Zscaler Zero Trust Browser, available as both an extension and a full enterprise browser, BDR maintains a continuously updated threat detection library that pushes new policies to all users as new attack techniques emerge.The browser became the enterprise's most critical application. It is time the security stack caught up.To learn more about how Zscaler Zero Trust Browser protects your organization with industry-first Browser Detection and Response, visit&nbsp;our page or&nbsp;contact a sales representative.]]></description>
            <dc:creator>Ashraf Aziz (Director Product Marketing, Zero Trust Browser)</dc:creator>
        </item>
        <item>
            <title><![CDATA[NIST&#039;s New OT Guide Draws the Zero Trust Line at Level 3. Attackers Are Working Below It.]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/nist-s-new-ot-guide-draws-zero-trust-line-level-3-attackers-are-working</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/nist-s-new-ot-guide-draws-zero-trust-line-level-3-attackers-are-working</guid>
            <pubDate>Sun, 04 Oct 2026 16:10:45 GMT</pubDate>
            <description><![CDATA[Quick answer: NIST released the initial public draft of SP 800-82 Revision 4, its Guide to Operational Technology Security, on September 21, 2026, with public comments open through November 30. The draft adds zero trust principles to OT security architecture but recommends applying them to compatible systems, typically those at Purdue Level 3 and above, because many controllers and operator panels cannot fully take part. That leaves the controllers running the physical process protected at the zone boundary, which the same section of the draft says does not stop an attacker who is already inside the zone. In a chemical plant, the controller that holds a batch reactor at temperature sits a few network hops from the operator screens that display it, the engineering workstation that programs it, and the historian that logs its readings. Industrial security has long protected that cluster by putting a firewall on its boundary and trusting what is inside. The new draft of&nbsp;NIST SP 800-82, the U.S. government's reference guide for OT security, now addresses zero trust directly, and the line it draws runs straight through that cluster.The draft organizes its guidance around the&nbsp;Purdue model, the standard way of layering a plant network, and its zero trust recommendation centers on the upper layers:Purdue levelWhat lives thereDraft's zero trust scope4-5Business ITTypically in scope3.5OT DMZ, the buffer between plant and businessTypically in scope3Plant-wide operations systems and historiansTypically in scope2Operator screens (HMIs)Zone boundaries1Controllers, mostly programmable logic controllers (PLCs)Zone boundaries0Sensors, valves, and motorsOut of scopeSection 5.3 makes two points a few paragraphs apart:What NIST concedesInside a perimeter, users are typically trusted and given broad access, so 'boundary protection devices between zones do not mitigate lateral movement risks within a zone.' (Section 5.3)Where NIST draws the lineBecause many PLCs, controllers, and HMIs 'do not support the technologies or protocols required to fully integrate with a ZTA implementation,' the draft recommends applying zero trust to compatible devices, such as those typically found at Levels 3, 4, and 5 and in the OT DMZ. (Section 5.3.1)Neither point is wrong, but together they leave the reactor controller where it started, behind a zone boundary that NIST itself says will not stop someone already inside. Why does the line sit at Level 3?The&nbsp;321-page draft presents zero trust as an extension of controls many plants already run: per-session approval of privileged access, OT logins kept separate from corporate ones, scanning of every file and USB drive, and monitoring that can revoke access in near real time. It also keeps the zone model, with firewalls, a DMZ, and a new management network where vendor sessions need just-in-time approval. It layers zero trust on top of zoning, a sensible choice for plants that cannot rebuild their networks.As NIST defines it, zero trust means every request to reach a system is checked close to that system and rechecked continuously, instead of being trusted because of where it comes from on the network. On a server or workstation, software on the machine can hold an identity and enforce that check. A PLC that shipped with a built-in web server and a shared maintenance password can do neither, and replacing controllers to fix that is not something a plant schedules lightly.NIST also adds two cautions: a zero trust component in the path of a request can slow it down or become unavailable, and shared logins, still common on plant floors, weaken any policy based on identity. Few OT engineers will dispute either. What attackers do below the lineLimiting controls at Level 3 have a cost, and joint advisory&nbsp;AA26-097A, first published April 7, 2026 by the FBI, CISA, NSA, and partner agencies and updated July 22, shows it. Iranian-affiliated actors went after PLCs from Rockwell Automation, Schneider Electric, and Siemens in three steps:Connect to the controller using the manufacturer's own programming software.Copy the project file that holds the controller's logic out to attacker infrastructure.Change that logic, in some cases disabling shutdown and alarm logic so systems could enter unsafe conditions without operators being notified.The controllers in the advisory were reachable directly from the internet, a path sound zoning closes. The advisory goes further, recommending firewall rules or access control features on the PLC itself so it accepts communications only from the control devices expected to talk to it. That is device-by-device isolation, the step the draft's zero trust scope stops short of below Level 3, and many controllers either lack those features or make them hard to manage one device at a time.Inside a zone, isolation shrinks what can reach a controller from everything on the network to the few systems that need to, usually an operator panel and an engineering workstation. The workstation then becomes the path to guard, because it runs the same programming software the attackers used. Zero trust without asking the device to participateThe draft's recommended zero trust scope typically ends at Level 3. Isolation enforced in the network can reach the network-connected controllers and operator panels below it.NIST's definition asks for access decisions made close to the resource and re-evaluated continuously. What it does not say is that the actual resource has to make them. The joint advisory highlights the same point, noting that a gateway in front of the PLC "can enable MFA for remote access even if the PLC does not support MFA." For a controller that cannot run software or hold an identity, the decision can live in the network directly in front of it, as long as three conditions hold:Find every device without disrupting it. NIST treats an accurate asset inventory as foundational and warns that active scanning can disrupt plant systems. Discovery that works from the traffic devices already send avoids that risk.Isolate each device individually. When each controller sits in a network segment of its own, or shares one only with the devices it talks to constantly, nothing else can reach it except through policy, including devices inside the same zone.Make the decision locally. The draft wants time-critical control functions able to operate locally, and a check that sends plant traffic to a distant data center adds the delay NIST warns about.Zscaler Zero Trust Branch is built around those conditions. Typically deployed at Level 3 or 3.5 in a&nbsp;Zero Trust Purdue architecture, its&nbsp;OT/IoT segmentation discovers and classifies devices from the traffic moving between them, without agents, scanners, or network access control. It then places each device in a segment of its own, so device-to-device connections pass a policy decision, with no re-addressing and no production downtime. That reaches network-connected controllers at Level 1 and operator panels at Level 2, the levels the draft leaves to zone boundaries.The appliance at the site becomes each device's gateway, so device-to-device policy is enforced locally with no round trip to the cloud, which answers the latency concern NIST raises. For the redundancy NIST requires, sites typically run the appliances as an&nbsp;active and standby pair. Devices that need to talk constantly or ones which can’t support a network of one, such as a controller and the operator panel that watches it, can&nbsp;share a small segment and communicate directly, while anything leaving that segment still passes policy. Traffic headed beyond the site goes to the Zero Trust Exchange, where&nbsp;internet, SaaS, and private application policy is applied, so a compromised device cannot reach past the plant either.Remote access also follows NIST's management-network pattern.&nbsp;Zscaler Privileged Remote Access brokers vendor and engineer sessions through the Zero Trust Exchange with no inbound ports open at the plant. It injects credentials from a vault and rotates them, so vendors never hold a password and shared logins stop circulating on the plant floor. Files a technician moves into a session can be scanned and detonated in&nbsp;Zscaler Cloud Sandbox before they reach the target, the remote-session counterpart to the file scanning NIST lists as zero trust in practice. Sessions are&nbsp;time-bound and recorded, which addresses&nbsp;the vendor access problem we see in almost every OT workshop.If something still manages to get in, the Ransomware Kill Switch tightens device-to-device policy in graduated steps, the isolation discipline laid out in our&nbsp;analysis of CI Fortify.It’s also important to understand the limits. Level 0, the sensors, valves, and motors wired directly to controllers, sit outside any network-based control and are generally protected through the controller. Isolation also cannot fix weaknesses in a specific controller or stop an attacker who already holds an expected device such as the engineering workstation, so the run-mode switch, programming protection, patching, and project-file integrity checks in the joint advisory still apply. A site that loses its cloud connection entirely needs its own isolation plan, which the CI Fortify guidance covers. Three things to do before the comment period closesFirst, map the carve-out against your own plant by listing what can reach each controller today, area by area. If the answer is anything in the zone, that is the exposure Section 5.3 describes.Second, inventory the connectivity nobody approved. The draft warns that cellular modems and vendor-managed connections can bypass enterprise and OT security controls and tells operators to inventory, approve, and restrict them.Third, comment. The Level 3 line is drawn around what the devices can do. Its control overlay already lists isolation of system components for high-impact systems, with no OT-specific discussion attached. Asset owners who have isolated controllers below Level 3 without asking the devices to participate can tell NIST so by emailing&nbsp;sp800-82rev4@nist.gov by November 30, 2026, using the comment template on the&nbsp;draft's publication page.To see where your plant stands against the draft,&nbsp;request an OT architecture workshop and we will map what can reach your controllers today. You can also&nbsp;hear from our customers directly on how they use Zscaler for OT security.]]></description>
            <dc:creator>Bryan Ashley (Zero Trust Networking, Principal Architect)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Ransomware Data Theft Surged 275% in 2026: Schools, Hospitals, and Government Agencies Had Some of the Largest Claims]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/ransomware-data-theft-surged-275-2026-schools-hospitals-and-government</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/ransomware-data-theft-surged-275-2026-schools-hospitals-and-government</guid>
            <pubDate>Thu, 01 Oct 2026 16:19:24 GMT</pubDate>
            <description><![CDATA[Data exfiltrated by leading ransomware groups jumped 275.8% year over year to 896.2 terabytes, according to the&nbsp;Zscaler ThreatLabz 2026 Ransomware Report. That is more than seven times the volume recorded during the 2023–2024 reporting period. As organizations move more sensitive information through modern digital operations, and increasingly through AI-enabled systems, attackers have more high-value targets to steal and more ways to pressure victims once they do.Government, education, and healthcare organizations were among the largest individual data theft incidents observed during the reporting period. Below, we break down what ThreatLabz observed across each sector, including a notable surge in attacks on utilities, and why these industries continue to attract ransomware campaigns. For the full view across industries and threat groups, download the&nbsp;Zscaler ThreatLabz 2026 Ransomware Report. How initial access is changingMany ransomware groups are shifting away from relying solely on malware delivery. ThreatLabz uncovered an initial access broker targeting employees who held&nbsp; manager positions primarily in non-technical departments such as accounting/finance, sales, operations, HR, and marketing, where a single compromised identity can open doors to sensitive data and essential services. Playbooks like spam bombing, IT-themed Microsoft Teams vishing, and abuse of legitimate support tools help adversaries gain a foothold quickly.Generative AI is making these playbooks easier to execute. ThreatLabz observed AI accelerating everything from reconnaissance and social engineering to malware development, including a surge in new malware families where tooling appeared to have been created with GenAI assistance. Some of the largest data theft claims involved government, education, and healthcareBased on activity visible on ransomware leak sites, organizations in these sectors were tied to some of the largest data theft incidents observed during this reporting period.Government. Ransomware attacks targeting government organizations declined 27% year over year, and the sector ranked ninth overall. Despite the decrease, government organizations were tied to the largest data theft claim in the ThreatLabz dataset: Babuk2 claimed to have stolen 30 TB of data from a government organization.Healthcare. Healthcare ransomware activity declined 24% year over year, but the sector remained one of the most targeted industries overall, ranking fourth. INC Ransom claimed to have stolen 20 TB of data from a large healthcare organization, one of the largest claims in the dataset. In a separate incident, attackers used spam bombing and IT-themed impersonation to gain initial access, then pursued extortion without encrypting systems. The victim paid a $2 million ransom even though files were never encrypted.Education. Ransomware activity targeting education declined 17% year over year, with the sector ranking eleventh. Pear, a relatively new ransomware group, claimed to have stolen 16 TB of data from a U.S. university. ShinyHunters, first observed in 2025, also drew attention for an extortion&nbsp;campaign targeting the education sector.Utilities. While utilities had too few victims (10) in the prior year to include in the formal year-over-year comparison, the sector rose sharply by 622% to 65 victim organizations. As the Ransomware Report notes, ransomware attacks on sectors that support essential services carry implications beyond their absolute victim counts, with ripple effects through supply chains and dependent operations.While overall attack volume against government, healthcare, and education decreased year over year, the scale of individual data theft incidents grew. The campaigns are fewer. The damage per campaign is larger.&nbsp; Why these sectors attract ransomware campaignsThese sectors share characteristics that make them effective extortion targets:Compliance pressure is built in. ThreatLabz found that during ransom negotiations, threat actors often cite regulatory requirements, including HIPAA, SEC disclosure rules, and GDPR, directly to intensify pressure on victims. This tactic applies across industries, but for highly regulated sectors like government and healthcare, the stakes are especially acute. The theft of protected records can itself constitute a regulatory breach, meaning compliance and legal consequences are already locked in regardless of whether the ransom is paid to prevent public exposure.Trust is a currency. For government agencies, healthcare providers, schools, and utilities, a breach can become a community-wide event, not just an IT issue.Downtime carries outsized consequences. Essential services create urgency and have limited tolerance for prolonged disruption. How to strengthen ransomware defensesThe scale and sophistication of ransomware threats in 2026 demand both immediate and strategic action:Adopt a zero trust architecture. Remove implicit trust and enforce least-privilege access across users, devices, and workloads. Connecting users to specific applications rather than placing them on the network limits what a compromised identity can reach and prevents the lateral movement that leads to large-scale data theft.Inspect encrypted traffic. Real-time TLS/SSL inspection is critical because payload delivery and C2 traffic are often hidden inside encrypted flows.Treat data as the primary target. The incidents in this report show that data exfiltration, not encryption, is driving extortion. Use inline DLP controls and plan for exfiltration scenarios with clear incident response playbooks.Fight AI with AI. Apply AI-powered tools to identify patterns, detect anomalies, and accelerate response, especially as attackers use GenAI to scale social engineering and develop new tooling.See our full ransomware prevention guidance and best practices in the report.The ThreatLabz 2026 Ransomware Report offers deeper analysis of ransomware trends, attacker tactics, and victim data across all industries, along with detailed guidance on how a zero trust architecture mitigates ransomware risk. Download the full report here.]]></description>
            <dc:creator>Adam Ford (Chief Technology Officer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[ZDX Agent: Agentic IT Operations for Admins]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/zdx-agent-agentic-it-operations-admins</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/zdx-agent-agentic-it-operations-admins</guid>
            <pubDate>Wed, 30 Sep 2026 15:34:04 GMT</pubDate>
            <description><![CDATA[Help IT teams quickly pinpoint whether user experience issues stem from the device, network, Zero Trust Exchange, or application so secure access through the Zscaler Zero Trust Exchange also delivers a better digital experience.SASE has changed how users connect to applications. Instead of backhauling traffic through legacy networks, users connect from anywhere, over any network, to private apps, SaaS platforms, and the internet through a cloud-delivered security architecture.That shift is essential for Zero Trust transformation, but it also changes how IT teams troubleshoot. Traditional monitoring tools rely on siloed point-agents, one for device health, another for network pathing, and another for application monitoring. Because these point-products operate in isolation, they lack the shared end-to-end context required to solve complex SASE performance issues, resulting in war rooms and finger-pointing.When a user says, “Salesforce is slow,” “Zoom is choppy,” or “I can’t access an internal app,” the issue could be caused by the endpoint, Wi-Fi, ISP, DNS, Zscaler Zero Trust Exchange, or the application itself.For IT, network, security, and service desk teams, the hardest question in SASE is often:Is this performance issue caused by my SASE deployment, the network, the user’s device, or the application?That is where&nbsp;Zscaler Digital Experience (ZDX) becomes critical and where ZDX Agent, part of Zscaler’s ZAgent, empowers admins with Agentic IT Operations.&nbsp; The operational gap in SASESASE brings networking and security together in the cloud. But when troubleshooting still depends on manually pivoting across dashboards, logs, tickets, and team handoffs, IT operations can remain slow and fragmented.A single user issue can trigger multiple teams:The service desk checks the endpoint.Network operations checks Wi-Fi, ISP, and routing.Security teams check access policy, ZIA, or ZPA behavior.Application teams check SaaS or private app health.Each team may have a piece of the answer, but not the full picture. The result is often finger-pointing, escalation, and lost productivity.ZDX helps solve this by monitoring digital experience across the full user-to-application path, including the SASE deployment, the network, the user’s device, or the application. ZDX Agent takes that one step further by allowing teams to ask questions in natural language and receive a structured root cause analysis with supporting evidence and suggested remediation steps. What is ZDX Agent?ZDX Agent is an AI-powered digital experience agent that helps IT teams investigate user experience issues using natural language.Instead of starting with, “Which dashboard should I open?” teams can start with the issue they need to solve:“Why is this user having a poor experience?”“Analyze Wi-Fi health for all users in the San Francisco office.”“Troubleshoot Zoom call performance for this user.”“Which network leg is causing latency?”“Why did users experience poor performance for Salesforce Lightning in the last 12 hours?”ZDX Agent can help analyze signals across device health, Wi-Fi, network path, ISP performance, application response, collaboration tools to suggest remediation steps.To move teams from symptom to resolution instantly, ZDX Agent combines three core AI skill sets into a single interface:Knowledge Skills: Instantly answers how-to queries and architectural guidance, eliminating time spent searching through technical documentation.Data Analytics Skills: Automatically scans days of raw network, endpoint, and security telemetry in seconds to surface hidden Wi-Fi, ISP, and application anomalies.Troubleshooting Skills: Executes end-to-end root cause investigations across the entire SASE path and delivers clear, actionable remediation steps for IT teams to execute immediately.The goal is simple: help teams move from symptoms to evidence to resolution faster. Why ZDX Agent matters for the Zscaler Zero Trust ExchangeThe Zscaler Zero Trust Exchange securely connects users, devices, workloads, and applications without placing users on the corporate network. It enforces policy close to the user, brokers access based on identity and context, and helps organizations deliver secure connectivity at scale.But secure access and great user experience must go together. If users are protected but struggling with slow SaaS performance, poor call quality, or intermittent access, IT needs to know why and fast.ZDX provides the experience telemetry. ZDX Agent helps turn that telemetry into answers.Together, they help teams understand:Whether a problem is isolated to a user, location, app, ISP, or network pathWhether performance degradation is related to endpoint health, Wi-Fi, Zscaler path, policy, or application responseWhether an issue should be owned by IT, NetOps, SecOps, an ISP, or an application teamWhich actions can help restore user productivity fasterIn other words, ZDX Agent helps make the Zero Trust Exchange not only secure and scalable, but also observable, explainable, and easier to operate. Use case 1: Determining whether the issue is SASE, the network, or the appIn a SASE environment, users connect through multiple layers: endpoint, local network, internet, Zscaler services, and the destination application. When performance drops, IT teams need to understand where the degradation occurred before they can engage the right team.With ZDX Agent, teams can start with a prompt such as:“Troubleshoot slow application performance for this user.”ZDX Agent can analyze the user-to-app path and help determine whether the issue is tied to endpoint resources, Wi-Fi signal, network latency, Zscaler path, or the application itself. Why it matters for SASE: Teams can distinguish between security service issues, network conditions, and application-side degradation faster, reducing unnecessary escalations and helping users get back to work. Use case 2: Reducing MTTR across Wi-Fi, ISP, and routing issuesIn hybrid work, many user experience issues start outside the enterprise network. Employees connect from home, branch offices, airports, cafés, and customer sites. Local networks and ISPs are often outside IT’s direct control, but they still shape how users experience SASE.ZDX Agent can help teams investigate questions such as:“Which network leg is causing latency?”&nbsp;OR&nbsp;“Analyze Wi-Fi health for users in this office.”The agent can correlate Wi-Fi quality, roaming behavior, access point health, ISP latency, packet loss, and application experience. This is especially useful for NetOps teams trying to determine whether an issue is local, regional, ISP-related, or tied to a broader service path.Think about a complex escalation that requires many people and many hours to diagnose before it gets traced to an intermediate ISP. With ZDX and agentic troubleshooting, that type of investigation can be accelerated because the relevant telemetry is already correlated across the user-to-app path.Hear directly from our customers, on how to use ZDX Agent to diagnose and solve his Wi-Fi and app issues.&nbsp;Why it matters for SASE: A poor network underlay can look like a SASE issue. ZDX Agent helps prove where the problem lives, so teams can take targeted action instead of guessing. Use case 3: Distinguishing policy issues from performance issuesSecurity teams are often pulled into performance escalations because users assume the security platform is blocking or slowing access. Sometimes the issue may involve policy. Other times, the root cause is Wi-Fi, ISP latency, DNS, application response time, or endpoint health.ZDX Agent can help security and IT teams ask:“Is this access issue caused by policy or network degradation?”&nbsp;OR&nbsp;“Which apps have slow server response times on a direct path?”This helps teams determine whether an issue is related to ZIA, ZPA, policy behavior, or something outside the security control plane.Why it matters for SASE: Zero trust requires strong policy enforcement, but users still expect seamless access. ZDX Agent helps teams validate whether policy is working as intended while identifying non-policy causes of poor experience. Use case 4: Empowering the service desk with expert-level troubleshootingMany digital experience issues begin as service desk tickets. The challenge is that L1 and L2 teams may not have deep expertise across networking, endpoint performance, Zscaler architecture, SaaS behavior, and collaboration tools.ZDX Agent helps close that skills gap by giving analysts a guided way to investigate issues such as:“Why did this user’s experience drop today?”&nbsp;OR&nbsp;“Troubleshoot Teams call quality for this user.”Instead of escalating immediately, the analyst can receive a structured report with likely root cause, supporting evidence, and recommended next steps.&nbsp;Why it matters for SASE: As SASE environments scale, operational expertise must scale with them. ZDX Agent helps more teams resolve issues directly and escalate with better context when specialized support is needed. From dashboard-driven to question-driven operationsTraditional operations are dashboard-driven. Teams must know where to look, which metrics matter, and how to connect signals across tools.ZDX Agent, an Agentic IT Operations for Admin solution, is question-driven. Teams start with the outcome they need:“Find the root cause of poor experience for these users.”“Show me whether this issue is isolated to one location.”“Identify whether the problem is Wi-Fi, ISP, Zscaler path, or the application.”That shift matters because SASE operations are inherently cross-domain. User experience depends on multiple systems working together. ZDX Agent helps analyze those systems together. Making ZDX value clear in a SASE architectureZDX makes digital experience visible across the full path from user to application. ZDX Agent makes that visibility easier to consume and act on.For organizations adopting SASE, this means:Faster troubleshooting: Reduce time spent manually correlating data across domains.Clearer ownership: Identify whether the next step belongs to endpoint, network, security, ISP, or application teams.Better user experience: Detect and resolve issues that affect productivity.Stronger confidence in zero trust: Prove that secure access is working—and quickly isolate when something else is not.More scalable operations: Give service desk, NetOps, and security teams a common experience-driven source of truth.The result is a stronger operational foundation for the Zscaler Zero Trust Exchange: security teams can enforce zero trust, IT teams can monitor experience, operations teams can troubleshoot faster, and users can stay productive. The future of SASE is autonomous and experience-awareSASE has already transformed secure access. The next step is transforming how that environment is operated.Because in a SASE world, the question is no longer just:“Is the user secure?”&nbsp;It is also:&nbsp;“Can the user work, and if not, do we know why?”With ZDX Agent, IT teams can answer that question faster, with evidence, and with a clearer path to resolution.Watch the latest&nbsp;ZDX Agent webinar featuring a customer panel with Salesforce.]]></description>
            <dc:creator>Cynthia Tu (Sr. Product Marketing Manager, DEM)</dc:creator>
        </item>
        <item>
            <title><![CDATA[What&#039;s New in GovCloud: September 2026 Zscaler Product Updates]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-govcloud-september-2026-zscaler-product-updates</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-govcloud-september-2026-zscaler-product-updates</guid>
            <pubDate>Wed, 30 Sep 2026 14:13:22 GMT</pubDate>
            <description><![CDATA[With fiscal year-end, audit cycles, and shifting mission priorities all competing for attention, it's easy for product updates to stack up unread. Here is a curated roundup of notable Zscaler GovCloud updates from September, with quick context and scan-friendly takeaways you can share across security, network, and operations teams. Highlights include the rollout of Experience Center (a unified management console for the Zero Trust Exchange platform), AI-powered application segment recommendations in ZPA, a fully managed Zero Trust Gateway offering in AWS, and expanded DLP controls for Google Drive link expiration and Claude tenant profiles in ZIA. Experience Center, Unified Management ConsoleZscaler has started rolling out Experience Center to GovCloud. Experience Center is a unified, cloud-native management console for the Zscaler Zero Trust Exchange platform. It is designed for CISOs, CIOs, network administrators, cybersecurity practitioners, and service desk teams who manage zero trust security policies, endpoint agents, internet and SaaS access, private application access, and digital experience monitoring.Experience Center consolidates these management functions into a single interface with persona-driven workflows, role-based access control, and unified analytics, replacing the fragmented multi-console workflows that traditional point product environments require.For more details, check out our blog. Zscaler Internet Access (ZIA)Zscaler Internet Access (ZIA) is Zscaler's secure internet and SaaS access service, providing policy-based protection and visibility for users wherever they work. For many federal environments, ZIA is central to enforcing acceptable use, protecting sensitive data, and maintaining consistent security controls across a distributed workforce.This month's ZIA updates expand governance controls for generative AI applications, strengthen DLP capabilities with proximity matching and automated link expiration, and extend cloud app control for Google Gemini.HighlightsSupport for Claude in Tenant Profile: The Tenant Profiles feature now extends to the Claude application, allowing admins to provide access to specific workspace IDs for Claude. This helps agencies govern AI application usage at a tenant level. (FedRAMP Moderate and High)Support for External Link Expiration in Google Drive: Admins can now set periodic or custom expiration periods for Google Drive links (internal or external), after which file access is automatically revoked. Four new expiration-based actions are available in the Edit DLP rule window (Remove Collaborators, Remove External Sharing Links, Remove Internal Sharing Links, and Remove Sharing After Expiry), with manual expiration available under Remediation Actions on the SaaS Assets with Incidents page and matching fields added to the /casbDlpRules APIs. (FedRAMP Moderate)Support for New Match Type on Custom DLP Dictionaries: Custom DLP dictionaries now support near and not-near proximity matching, letting admins define how close (in bytes) phrases from phrase groups must be for a dictionary to detect and count them as a match. This adds precision to content detection without requiring additional dictionaries. (FedRAMP Moderate and High)Cloud App Control Policy: Upload Action for Google Gemini: The Cloud App Control policy now supports a granular Uploading action for the Google Gemini application and its instances, added under Allow application access in the Add/Edit AI &amp; ML Rule window. (FedRAMP Moderate and High)Expanded SSPM Controls for Box: Four new Advanced SaaS Security Posture Management controls were added for Box. (FedRAMP Moderate and High)For full release notes: https://help.zscaler.us/zia/release-upgrade-summary-2026 Zscaler Private Access (ZPA)Zscaler Private Access (ZPA) provides secure, zero trust connectivity between users and private applications without exposing those applications to the internet. It helps organizations reduce attack surface while improving access experience, which is especially important for distributed users, mission partners, and hybrid work environments common across federal agencies.This month's ZPA updates introduce AI-powered capabilities in Limited Availability that help teams optimize application segment configuration and gain visibility into segment usage patterns.HighlightsAI Recommendations for Application Segments (Limited Availability): ZPA now offers AI-powered recommendations for application segments. This feature analyzes user logs and suggests application segments based on application similarity or user behavior, helping teams refine their segmentation strategy and reduce manual configuration effort. (FedRAMP Moderate and High)Application Segments Usage (Limited Availability): Admins can now view or download Application Segments Usage reports from the Zscaler Admin Console to review which application segments are actively used and which user groups are accessing them. This provides visibility that supports access reviews and optimization. (FedRAMP Moderate and High)For full release notes: https://help.zscaler.us/zpa/release-upgrade-summary-2026 Zscaler Digital Experience (ZDX)Zscaler Digital Experience (ZDX) provides visibility into end-user device health, application performance, and network path quality. For federal teams managing distributed endpoints across agencies and field locations, ZDX helps identify and resolve experience issues before they impact productivity or mission delivery.This month's ZDX updates deliver Cloud Path probe enhancements and a refreshed filter design across the console.HighlightsTCP Type Enhancements: Admins can now select a specific TCP traceroute type when configuring a Cloud Path probe. Resilient TCP retries using the Conventional TCP type if the initial connection fails, while Strict TCP does not fall back if the connection fails. These options give teams more control over probe behavior in environments where firewalls may block SYN-based traceroutes. (FedRAMP Moderate and High)Design Update for Filters: Filters across ZDX have been updated with a new color palette and typography for improved readability and consistency. (FedRAMP Moderate and High)For full release notes: https://help.zscaler.us/zdx/release-upgrade-summary-2026 Zscaler Client ConnectorZscaler Client Connector is the unified endpoint agent that steers traffic to ZIA, ZPA, and ZDX services. It ensures consistent policy enforcement regardless of where users connect from, which is critical for agencies supporting remote and hybrid workforces.This month includes a significant Windows release, an Android/ChromeOS update addressing multiple security vulnerabilities, and Admin Console fixes.HighlightsZscaler Admin Console 4.5.5: Fixes a pagination issue affecting user search results on the Enrolled Devices page, a Device Details file download timeout, a blank Protocol dropdown when adding a custom IP-based application bypass in Experience Center, and a sync issue where users added to groups already entitled to Private Access did not receive access after Update Policy. (FedRAMP Moderate, August 14; FedRAMP High, August 7)Zscaler Client Connector 4.9.0.465 for Windows: Addresses a range of stability and connectivity issues, including a stuck Restarting service status, Internet Unreachable errors over machine tunnels in no-default-route environments with an explicit proxy, partner-tenant reauthentication failures, slow connections with many hostname-based trusted networks, Endpoint DLP detection when enabled pre-enrollment, disconnections with FIPS libraries, several VDI re-enrollment and AWS Windows Server issues, slow app loading from loopback proxy delays, and excessive memory use with unsupported certificates. Parallel maintenance releases 4.8.0.300 and 4.7.0.376 shipped the same day.Zscaler Client Connector 4.2.0.173 for Android and ChromeOS: Adds support for the ind.zscalertwo.net subcloud, fixes multiple Firebase-reported crashes, and addresses security vulnerabilities including a local denial-of-service vector (CVSS 7.0), remote code execution vulnerabilities (CVSS 7), and an authentication bypass for portal-only communications (CVSS 6.8). Also fixes a ChromeOS-only authentication failure with Google Workspace Always On VPN and improves Z-Tunnel 2.0 and Private Access reconnection after connectivity is restored. A follow-up release, 4.2.0.174, fixes a reauthentication failure introduced in 4.2.0.173.Additional Releases: Windows 4.9.0.455 and 4.8.0.291 include installer mitigation logic for a rare blue-screen upgrade condition, a Firewall posture check fix, and a captive-portal high-CPU fix.For full release notes: https://help.zscaler.us/client-connector/release-upgrade-summary-2026 Cloud &amp; Branch ConnectorZscaler Cloud &amp; Branch Connector helps extend Zscaler policy enforcement and traffic forwarding for workloads running in public cloud environments. It supports organizations that need consistent security controls for cloud-hosted services while enabling architectures aligned to modernization initiatives.This month introduces a fully managed, cloud-native security offering in AWS, available in Limited Availability.HighlightsZscaler Zero Trust Gateways in Amazon Web Services (Limited Availability): Zscaler has introduced a fully managed, cloud-native SaaS security offering in AWS that allows organizations to secure workload traffic and eliminate the need to manage security infrastructure in their AWS environment. It provides the same security controls for cloud-to-internet and cloud-to-cloud communication. Zscaler supports AWS commercial on the FedRAMP Moderate cloud. (FedRAMP Moderate)For full release notes: https://help.zscaler.us/cloud-branch-connector/release-upgrade-summary-2026 Authentication Service (Zidentity)The Zscaler Authentication Service (Zidentity) provides centralized identity and access management for the Zscaler platform. It supports authentication policies, MFA enforcement, and user lifecycle controls that help agencies meet identity-centric zero trust requirements.HighlightsCustomize Password Policy: Admins can configure the password policy to deactivate a user account after a specific number of unsuccessful authentication attempts and reject a specific number of previously used passwords. Both values are customizable from 3 to 10 in the Zscaler Admin Console. (FedRAMP Moderate and High)For full release notes: https://help.zscaler.us/zidentity/release-upgrade-summary-2026 ConclusionWant the full details? Use the links above to review the complete release summaries, and check back next month for the next GovCloud update roundup.Zscaler continues to invest in a robust GovCloud roadmap and remains committed to supporting the unique security, compliance, and operational requirements of the federal market. We'll keep delivering enhancements that help agencies and federal partners strengthen resilience, simplify operations, and advance mission success.]]></description>
            <dc:creator>Jose Arvelo Negron (Manager, Sales Engineer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[What’s New in Zscaler SSE]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-zscaler-sse</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/what-s-new-zscaler-sse</guid>
            <pubDate>Mon, 28 Sep 2026 19:30:00 GMT</pubDate>
            <description><![CDATA[IntroductionMore than half of the Fortune 500 and over 40% of the Global 2000 already run on Zscaler. They moved security to the cloud, inline and close to the user, sending their traffic through the world's largest inline security cloud.Enterprises running firewalls and VPN could argue they had time. AI has taken that argument away.Attackers now use AI to turn a disclosed CVE into a working exploit in hours, generate malware variants faster than signature pipelines can catalog them, and stand up phishing sites that vanish before reputation feeds notice them. Research shows defenders had roughly 63 days between disclosure and exploitation in 2018; today, exploitation routinely happens before a patch exists. At the same time, traffic is moving to WebSockets, QUIC, and HTTP/3 that appliance-era inspection was never built to parse. And the post-quantum shift isn’t coming; it’s here. Browsers already negotiate post-quantum key exchange by default, which means a growing share of encrypted traffic is invisible to any inspection layer that can’t keep up.&nbsp;Perimeter architectures cannot close either gap. A firewall that has to backhaul, decrypt and correlate after the fact is losing a race it was never designed to run, and it can’t inspect a handshake it can’t join. The only architecture built for machine-speed threats is one that inspects every transaction inline, in the cloud, at the moment it happens, including traffic that’s already post-quantum.That is the architecture the world's largest enterprises already chose.At&nbsp;ZenithLive 2026, we introduced major architectural advancements across both&nbsp;Zscaler Internet Access (ZIA) and&nbsp;Zscaler Private Access (ZPA). Together, they represent a unified philosophy: every transaction across the internet, SaaS, and private applications must be subjected to real-time Zero Trust verification without adding operational complexity.Here is a small but important subset of new capabilities across the platform.Part 1: What’s New in Zscaler Internet Access (ZIA)Inline security is only as effective as the traffic that receives an actual, real-time verdict. When inspection engines induce latency, teams resort to exceptions where breaches occur. The latest innovations in ZIA focus on closing inspection blind spots, eliminating latency tradeoffs, and equipping SOC teams with rich transactional context.1. Zscaler is Post-Quantum Ready.&nbsp;Enterprise traffic is moving to protocols designed for speed and future cryptographic resilience. Inspection engines must keep pace:Post-Quantum Cryptography (PQC) Readiness: Most post-quantum coverage focuses on "harvest now, decrypt later" – an adversary recording encrypted traffic today to break it once a sufficiently capable quantum computer exists. That risk is real, the timeline is genuinely unknown, and nobody who tells you they know the date does.But there's a nearer-term problem that gets far less attention, and it isn't hypothetical. Browsers already negotiate hybrid post-quantum key exchange by default. As server-side support spreads, more and more sessions will complete a handshake your inspection layer cannot participate in. At that point a middlebox has two options, and both are bad: fail open and lose visibility, or fail closed and break the connection. The question that matters in 2026 isn't, “am I quantum-safe?” It's “when both endpoints go post-quantum, do I go blind?”So we sequenced our work as visibility, then inspection, then forwarding:PQC visibility and analytics: Classical versus post-quantum cipher usage across your traffic, a crypto inventory to plan migration against, and six new Web Insight logging fields covering client and server key exchange algorithms, digital signature algorithms, and client-side proposals. You cannot plan a migration you cannot measure, and most organizations currently cannot measure this. This is available today to Zscaler customers.PQC traffic inspection at scale: TLS inspection with hybrid ML-KEM / DH key exchange, delivering real-time inspection and policy enforcement across every combination: PQC client to PQC server, classical client to PQC server, and PQC client to classical server. No configuration change is required to start seeing PQC traffic. In beta now, this feature will be in limited availability later this year.IPsec with post-quantum pre-shared keys: quantum-safe forwarding to Zscaler from PPK-capable VPN gateways on your premises, so the tunnel carrying the traffic is protected on the same terms as the traffic itself. This feature will be available to customers early next year.&nbsp;Alongside these, two controls for organizations with specific cryptographic obligations:&nbsp;custom crypto profiles, which let administrators configure, restrict or prioritize cipher suites during TLS inspection with per-profile minimum TLS versions, and&nbsp;custom certificate key lengths supporting RSA-4096 and ECDSA P-256 for intermediate certificates driven largely by German BSI requirements, though the applicability is broader.Modern AI Protocols (WebSockets, QUIC, HTTP/3): Because streaming AI interfaces rely heavily on WebSockets for real-time model interaction, ZIA delivers deep bidirectional text inspection across sanctioned applications (including Microsoft Copilot and Grammarly), alongside native enforcement for QUIC, HTTP/3, and WebTransport. In beta now; this feature will be in limited availability later this year.2. Eliminating Sandbox Latency: AI Instant Verdict and CDRThe historical dilemma of sandboxing has always been the tradeoff between accuracy and latency. Accurate remediation takes minutes; business moves in seconds. When employees need a file immediately, security teams face pressure to allow downloads before analysis completes.AI Instant Verdict: Powered by a model trained on more than 600 million file samples, ZIA now scores files inline. Anything scoring 91–100 is blocked immediately, before it reaches an endpoint. In production, about 91% of files receive an instant benign verdict and are delivered with no perceptible delay, some are escalated for deeper dynamic analysis, and about some are blocked outright. Throughput runs to 10,000+ files in 20 minutes.The point is not that the model replaces detonation. It doesn't – the 9% still goes to the sandbox, and that's where it belongs. The point is that the common case stops waiting on the uncommon one. This feature is available today.Content Disarm and Reconstruction (CDR): For workflows where a file is likely benign but immediate access is critical,&nbsp;CDR strips active macros and embedded scripts from Office documents and PDFs, reconstructing a sanitized version in real time. Rather than debating allow-versus-block, users get safe files instantly while eliminating file-based attack surfaces. This feature will be available to all current ZIA customers in Limited Availability starting early next year.Brand Phishing Defense: Modern credential harvesting pages stand up, harvest credentials for six hours, and vanish before URL reputation feeds catch up. ZIA’s brand phishing engine inspects visual layout cues, credential input forms, and page construction in real time, rendering verdicts on zero-hour phishing infrastructure independently of historical domain reputation.This feature will be available to all current&nbsp;ZIA customers in Limited Availability starting early next year.3. Securing the New Executable: Agentic AI and MCP ArchitectureFor thirty years, security stacks assumed malware meant compiled binaries (EXEs, DLLs, ELFs). Today, the definition of an executable has fundamentally changed.As developers and business units deploy agentic AI frameworks, these tools download instruction manifests, skill files, and connect to Model Context Protocol (MCP) servers. A skill file is a plaintext file, but functionally, it is an executable program instructing an autonomous agent to execute actions with user permissions. Conventional security controls overlook them completely.ZIA extends inline enforcement to agentic workflows:Rogue MCP Server Blocking:&nbsp;Prevents local systems, enterprise internal applications, and autonomous agents from establishing connections to unauthorized, vulnerable, or malicious Model Context Protocol (MCP) servers across the network layer. This feature will be available later this year.Agentic Tool Download Inspection:&nbsp;Identifies, inspects, and halts unauthorized agentic AI frameworks and tooling at download time rather than discovering them later at runtime. This feature will be available later this year.Skill File Sandbox Detonation:&nbsp;Inspects and behaviorally analyzes text-based skill manifests and tool instruction files within Cloud Sandbox upon download before they can be loaded by an agent. This automated dynamic analysis catches both known malicious skills and novel variants that lack signatures. This feature will be available later this year.&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4. Comprehensive Visibility: Offline Channels and JA4 FingerprintingInline coverage has a structural blind spot: files that never traverse the network. A contractor's USB stick, an AirDrop between two laptops in the same room, a Bluetooth transfer. These are just a meaningful fraction of ways malware actually arrives in offices.Cloud Sandbox now operates across three channels rather than one:Inline sandbox: real-time blocking of malicious content in traffic.Endpoint Sandbox: unknown EXE and DLL files arriving over offline channels are hashed and queried; if the file is unknown, it's sent to Cloud Sandbox for full analysis, with the client notifying the user while the check runs.API-driven file analysis: on-demand submission for investigation, supporting multiple API keys, so the SOC can push a suspect file through the same engine that makes inline decisions.We also widened what the sandbox can take: EXE and DLL analysis up to 200 MB, and macOS DMG support.JA4 Fingerprinting (Encrypted Traffic Analysis): Certain endpoints such as OT controllers, medical devices, or services with pinned certificates cannot be decrypted. Using&nbsp;JA4 fingerprinting of the TLS handshake, ZIA models baseline communications. When a device that has behaved like a camera for months suddenly negotiates a session characteristic of a command-and-control framework, alerts fire immediately without needing plaintext decryption. This feature is generally available for Zscaler customers.&nbsp;5. SOC Empowerment and ProvenanceThe standard architecture for SOC context is reassembly: EDR, firewall, SWG, NDR, identity and cloud each emit telemetry, and a SIEM correlates it after the fact. Correlation works, but it costs time and it's lossy, i.e. you're reconstructing a single event from artifacts several systems produced independently.Endpoint Context leverages Zscaler’s vantage point in the end-to-end network to change this. Application, process and vulnerability insight from the endpoint feeds directly into detection and enforcement, so the context is attached to the transaction rather than joined to it later. This isn't a reporting improvement; it produces detections that don't otherwise exist.A concrete case:&nbsp;chrome.exe running from a directory it has no business running from, unsigned, with an unknown version, opening a remote connection. No individual signal there is conclusive, and nothing in the packet stream is anomalous. Together they're enough to generate a new IPS signature and block it. A control that only sees the network cannot make that call, because the evidence isn't on the network.The same endpoint intelligence, drawn from 50 million-plus endpoints, has improved command-and-control detection. Our C2 model previously leaned on URL and domain reputation. It now incorporates endpoint-derived context, and we've moved to rate-based C2 detection rather than purely pattern-based, which has reduced false positives noticeably. Living-off-the-land techniques and commodity C2 frameworks such as Cobalt Strike are the primary beneficiaries.AI/ML Detection Attribution: Every alert explicitly identifies the specific underlying model, heuristic, or detection engine responsible for the verdict. Security teams gain transparent auditability rather than opaque "black-box" scores.Closed-Loop MDR &amp; NDR Enforcement: Continuous traffic capture from ZIA to NDR partners like Vectra, ExtraHop, and Corelight improves SOC maturity for incident hunting and early lateral movement detection using rate, anomaly, and heuristic algorithms, significantly enhancing SASE visibility when combined with ZPA traffic. Here is a quick status update on our core NDR integrations:Vectra : Generally Available for AWS S3 environmentsExtraHop :&nbsp; Generally Available for AWS S3 environmentsCorelight : Private preview is active, with public preview scheduled by the end of the yearPart 2: What’s New in Zscaler Private Access (ZPA)While ZIA secures outbound access to SaaS, the web, and external AI models, ZPA governs access to internal crown jewels: proprietary private applications, private AI clusters, and hosted environments.Legacy connectivity models rely on VPN tunnels that terminate external users directly onto internal networks. If an endpoint is compromised, attackers gain unfettered lateral traversal. ZPA fundamentally inverts this model: users and entities are connected strictly to authorized applications, never to the underlying network.At ZenithLive, we introduced key capabilities to automate segmentation, secure unmanaged endpoints, and virtually patch internal vulnerabilities.1. Zscaler Autonomous Application Shield: Machine-Speed Defense for Private ApplicationsFrontier AI models have fundamentally altered the economics of exploitation, compressing the window from CVE disclosure to weaponized, chained exploit from weeks to hours. Yet enterprise remediation remains trapped in human-speed patch cycles, testing windows, and change boards. Autonomous Application Shield is an AI-driven capability natively integrated into ZPA that shifts private application security from reactive ticketing to continuous, autonomous protection:Continuous Posture: App Connectors safely and continuously assess application exposure points, APIs, and runtime risk, replacing periodic scans with a living, real-time security posture.Context-Aware Reasoning: The Zscaler cloud evaluates each application's unique architecture and observed traffic, applying only relevant, targeted protections to preserve performance and eliminate false positives.Global Threat Intelligence: Zero-days and novel attack vectors observed across Zscaler’s global exchange instantly inform and sharpen protection policies worldwide without manual tuning.Pipeline-Speed Virtual Patching: Defenses adapt dynamically as developers push code, deploying automated virtual patches at the App Connector boundary in minutes—neutralizing exploits before a permanent code patch can even be scheduled.Autonomous Application Shield is now open for early access.&nbsp;&nbsp;2.&nbsp;Comprehensive Access Visibility with Autonomous User-to-App SegmentationMost organizations actively manage only their crown jewel applications, leaving the vast majority of internal services and dynamically provisioned cloud workloads unmapped, poorly documented, and dangerously exposed behind overly permissive wildcard application segments (*.internal, *.corp). Traditional network segmentation projects fail because manual traffic analysis and static firewall rules cannot keep pace with modern hybrid cloud velocity.Autonomous User-to-App Segmentation eliminates this blind spot by automating the entire policy lifecycle:1. AI-Driven Automation: Application Fingerprinting and ZPA AgentApplication Fingerprinting: Leveraging machine learning algorithms trained across global enterprise telemetry, ZPA now automatically identifies, categorizes, and labels internal applications based on operational behavior and traffic patterns.Interactive ZPA Agent: Administrators can query complex deployment telemetry using plain language to gain visibility into underlying data alongside interactive telemetry, streamlining audit readiness and troubleshooting workflows.&nbsp;&nbsp;2. See Every Application (Continuous Discovery &amp; Inventory)Passive, Agentless Workload Sensing: Continuously senses and catalogs all active private workloads across on-premises datacenters, public clouds (AWS, Azure, GCP), and OT/factory environments without requiring intrusive endpoint scanners or complex network re-architecting.Surface Hidden Shadow Services: Detects untracked microservices, legacy internal web tools, and uncataloged container endpoints that typically evade standard configuration management databases (CMDBs).Expose Wildcard Risk: Automatically flags overly broad application definitions and wildcard domains that grant excessive IP reachability, giving security teams an authoritative, real-time baseline of their actual attack surface.3. Segment with Intelligence (AI-Powered Policy Recommendations)Behavioral Traffic Analysis: Analyzes historical and real-time user-to-application communication patterns, user identity groups, and transaction behaviors using advanced machine learning models.Automated Least-Privilege Rules: Automatically generates discrete, application-specific segment definitions and context-aware access policies, systematically replacing flat network access with precise, 1:1 micro-tunnels.Frictionless, One-Click Deployment: Allows administrators to review, test, and apply recommended policy boundaries in minutes rather than months, eliminating the risk of business disruption or broken application dependencies.4. Strengthen Security Posture (Posture Governance &amp; Actionable Insights)Continuous Relationship &amp; Dependency Mapping: Visualizes real-time communication pathways between user groups, third-party contractors, and application workloads to detect anomalous access trends or permission drift.Quantifiable Maturity Tracking: Feeds directly into maturity metrics (such as the ZPA App Segmentation Index), evaluating discovery velocity, policy effectiveness, and operational hygiene so teams can track quarter-over-quarter progress.Proactive Attack Surface Reduction: Delivers ongoing, prioritized recommendations to retire dormant policies, tighten access entitlements, and eliminate emerging vulnerabilities before threat actors can exploit them.Ensuring users and compromised devices are connected exclusively to specific, authorized applications, never to the underlying corporate network. This drastically shrinks the breach blast radius. This approach halts lateral threat movement while automating the labor-intensive tasks of application mapping and firewall rule maintenance, which frees security and network engineering teams from endless manual triage. Ultimately, it compresses segmentation deployment schedules from multi-year infrastructure overhauls into a rapid, phased, data-driven rollout with measurable executive reporting, accelerating Zero Trust time-to-value.Autonomous User-to-App Segmentation is available now.&nbsp;&nbsp;&nbsp;&nbsp;3. Secure Cross-Company Collaboration: B2B FederationModern business depends on ecosystem partnerships, from joint ventures and supply chain relationships to mergers, acquisitions, and divestitures. Yet connecting partner users to private applications today means accepting network risk: site-to-site VPNs, shared credentials, and firewall rules that create exactly the lateral movement exposure Zero Trust is designed to eliminate. What makes it worse, this process typically takes months to set up.ZPA B2B Federation changes that. Enterprises can onboard a partner and provide Zero Trust access to private applications in under 30 minutes, without site-to-site VPN tunnels, complex routing tables, or cross-tenant network exposure.Core deployment scenarios include:External Partner Connectivity: Onboard third-party contractors, vendors, and distributors quickly and securely. Partner users get authenticated access only to the applications they need, with Zero Trust policies enforced end-to-end, no network connectivity, no lateral movement risk.M&amp;A Integration and Divestitures: Deliver immediate Day-1 access to essential ERP, HR, and productivity platforms without consolidating networks or merging identity infrastructures. Offboarding requires only a swift policy adjustment.Multi-Tenant Enterprise Deployments: Large enterprises with multiple ZPA tenants can use Federation to simplify app sharing across parent companies and OpCos, while each unit retains control of its infrastructure, applications, and access policies.Federal and Cross-Cloud Environments: Facilitate secure resource sharing across FedHigh, FedMod, and commercial instances without interconnecting physical networks or violating regulatory mandates.&nbsp;&nbsp;4. Securing the Unmanaged Endpoint with Zero Trust Browser Extension for ZPAThird-party contractors, supply chain partners, and BYOD employees frequently require access to sensitive internal systems without having full device management profiles installed:The Zero Trust Browser Extension establishes an isolated, enterprise-controlled workspace directly inside modern web browsers.It enforces deep runtime data-loss prevention, blocking keystroke loggers, screen capture utilities, and clipboard copying.Device posture checks are evaluated locally, ensuring unmanaged endpoints cannot be leveraged as attack vectors into corporate resources.Standalone and hardened Enterprise Browser is also available as an alternative form factor.Zero Trust Browser Extension is available now.&nbsp;The Strategic Path ForwardWhen reviewing your cybersecurity roadmap, the most critical metric is not the sheer count of point products deployed or how many firewall policies are active.The question every executive and security architect should ask is:What percentage of our traffic actually receives an inline, deterministic Zero Trust verdict?If your outbound inspection cannot parse modern streaming protocols, negotiate post-quantum handshakes, or render instant verdicts on files, critical traffic is silently failing open. And if your private applications remain reachable via public IPs and routable VPN connections, an attacker compromising a single user or contractor endpoint can traverse laterally to your data.By combining the real-time inline threat engines of Zscaler Internet Access with the cloaking and autonomous segmentation of Zscaler Private Access, organizations establish a unified Zero Trust fabric. Attacks are stopped cold inline, critical internal workloads remain entirely invisible to the outside world, and enterprises can safely adopt AI and modern cloud architectures at scale.&nbsp;Learn how you can protect your enterprise in this AI-era by visiting our&nbsp;ZenithLive 2026 on-demand event.]]></description>
            <dc:creator>Joby Menon (SVP, Product Management | Zscaler)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Fairlife Had Eleven Days of Runway. Most Food Plants Can’t Buy a Shift.]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/fairlife-had-eleven-days-runway-most-food-plants-can-t-buy-shift</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/fairlife-had-eleven-days-runway-most-food-plants-can-t-buy-shift</guid>
            <pubDate>Fri, 25 Sep 2026 21:18:08 GMT</pubDate>
            <description><![CDATA[Black Kite counted 1,183 publicly disclosed ransomware victims in manufacturing in the first seven months of 2026, up 39.7% on the same period last year and already more than in all of 2023 or 2024, and its manufacturing report has ranked the sector the most-attacked industry for five consecutive years. Nearly half of this year's victims were hit by groups absent from the data in 2023 and 2024, some of them rebrands, so newcomers are&nbsp;arriving with the playbook already learned.Black Kite's research chief describes that playbook plainly: one attack can stop production, and every hour of downtime strengthens the attacker's hand, which makes time the thing the attacker is really holding.In most manufacturing, the clock that matters is how long the business can absorb a stopped line. In food and beverage, the clock is printed on the product, and attackers have noticed: the Food and Ag-ISAC&nbsp;counted 227 ransomware incidents against food and agriculture through July, up 62% on the same period last year.This summer's Fairlife incident looked like a disaster in the headlines, and why it wasn't one tells food manufacturers more. What follows is a composite of how these events tend to run, not any one company's timeline, with the facts Coca-Cola disclosed about Fairlife as the bookends. T+0: the alert is in ITRansomware is confirmed on enterprise hosts, and nothing on the plant floor has changed. Lines are running, products are moving, and the first question on the incident bridge is the obvious one: what else did they touch?On July 16,&nbsp;Coca-Cola disclosed in an SEC filing that Fairlife had identified unauthorized access to a portion of its systems, "including its production-related systems," in connection with a ransomware event. Production was suspended at all four US plants, while Canadian production was not affected and product quality and safety were not impacted. Coca-Cola has not said whether anything on the plant floor was reached, which is the shape of most public disclosures. T+2 hours: the question nobody can answerBetween the office and the line sits a layer both sides trust: the MES, recipe management, batch records, quality and lab systems, label printing, and the warehouse system that decides what ships. Every one of them is a Windows or Linux host, and a decade of Industry 4.0 investment connected them to the plant network on purpose.So the bridge question becomes: from the compromised segment, what can actually open a connection to an HMI, a line-side server, a controller, or the systems that write the batch record?In most plants the honest answer at hour two is "we don't know." Oscar Calderon, IBM's OT cybersecurity GRC leader,&nbsp;told Industrial Cyber in September that he has seen production stop when teams could no longer trust control systems, batch records, or quality data, with the equipment itself working fine. If the systems that write batch records and release holds might be reachable, stopping the line is the right call, made with almost no information. T+1 shift: the ledger startsThis is where food and beverage separates from the rest of manufacturing, because everything in the plant was on a clock before the alert.What is waitingWhat it is waiting onHow long it hasRaw inputs in receiving and silosThe line to restart. Raw milk, livestock and crops keep arriving, so lost days become destroyed raw material (Stuart King of AnzenOT, speaking to Industrial Cyber)Hours to a dayProduct in processA sequenced restart. "There is no such thing as a short outage" (King): product stuck mid-line and spoiling, systems reset, trucks at the dockThe shiftFinished goods in cold storageA release decision that needs trusted records. If the HACCP records for a production window are unverifiable, everything made in that window is presumptively suspect (King)Every day offline is a day off the shelf life you sellRetail commitmentsTrucks and shelves. Large retailers now treat cybersecurity and traceability as conditions of doing business (Calderon)Days, and the shortfall is on a shelf in public viewTrust in the systems that feed the lineSomeone to prove the attacker never reached themIndefinite, until provenThe attacker is counting on that last row, and the four above it are why a food plant was chosen in the first place. T+3 days: the negotiation is about datesBy day three the encrypted files matter less than they seem, because backups exist for those. There is usually a data-theft claim too; in Fairlife's case the Anubis group&nbsp;claimed a terabyte, and Coca-Cola&nbsp;confirmed that certain data was taken. In a food plant, the leverage that compounds is whatever goes out of date while the plant proves a negative.Jaguar Land Rover's September 2025 attack halted UK production for about five weeks, and on September 7 this year&nbsp;JLR announced about 4,000 job cuts amid the fallout. That is brutal, but a car does not expire in five weeks, while fresh milk cannot sit anywhere for one. T+11 days: most production resumesOn July 27, Coca-Cola said Fairlife had&nbsp;resumed the majority of production at its four US facilities and that retail availability had been "largely unimpacted, due to the availability of existing inventory." It did not expect a material impact, and the next day CEO Henrique Braun&nbsp;told analysts supply and consumer service had not been affected.From the attacker's side, that is a strange result: eleven days between Coca-Cola's first disclosure and its restoration update, at a brand Coca-Cola says grew from&nbsp;about $10 million to nearly $4 billion in retail value, and the ledger never reached the shelf.That outcome was engineered into the product. Ultra-filtration and higher-temperature pasteurization give Fairlife's milk&nbsp;a far longer unopened shelf life than conventional milk, and its protein shakes are shelf-stable. Enough finished product already in the channel, and a product built to sit on a shelf, gave Fairlife what most food manufacturers lack, which is runway measured in days. It also shaped the response: by Anubis's own account, Fairlife reported the incident rather than follow the instructions left on its network, a choice that is far easier to make while the shelves are still full.Now run the same eleven days at a fresh-milk bottler, a protein plant, a produce packer, or a bakery, where no inventory outlasts the outage. King made the point to Industrial Cyber: a dairy or protein plant with a difficult, sequenced restart takes days to come back regardless of how sophisticated the attacker was. Those are plants that cannot buy a shift, let alone eleven days.In most of these incidents, the length of the outage is not set by the malware. It is set at hour two, when the honest answer to "what can the compromised segment reach?" is "we don't know."Same eleven days. The plant stops on the top clock and pays on the bottom one. Recovery phases are illustrative, not Fairlife's disclosed timeline. What would have to be true at T+2 hoursA plant that cannot buy runway with inventory has one lever left, which is to shorten the outage. The fastest restarts will come from plants that can answer three questions before the incident, whatever the state of their backups.Reach. From a compromised host in IT, or in a supplier's network, what on the plant floor can be connected to at all? If the answer is "most of it," the shutdown decision was made years ago when the network was designed, and the incident is only collecting on it. Food and Ag-ISAC's Jonathan Braley notes that many OT compromises start in corporate IT and move laterally through weak segmentation.Dependency. Which production systems actually need a path to enterprise IT to keep running, and which have one only because the network was built flat? And where do the systems that write batch records and release holds actually live?Proof. Can you show, from records you already keep, what a given host has talked to in the last 30 days, so "we don't know" becomes "we know it never reached the line"?Four controls make those answers short.Segment every device.&nbsp;Zscaler Zero Trust Device Segmentation puts every production asset - controller, HMI, line-side server, vision system, and the MES, batch, and historian servers the line depends on - in a network of one, with no agents to install, no upgrades, and no downtime. A compromised host in IT gets no route to the line, which gives the reach question a one-word answer.Broker access instead of extending the network. OEM technicians, integrators, and your own engineers reach a specific controller for a specific session through&nbsp;Zscaler Privileged Remote Access, with no open RDP, SSH, or VNC ports on the plant, no network path between user and asset, and every session recorded, so the supplier's network never becomes an extension of yours.Let the policy be the dependency map. When every allowed IT-to-plant flow is a policy rather than an accident of addressing, the dependency list is the policy itself, and it exists before the incident, which is when the bridge needs it. Eaton has taken this model across&nbsp;more than 100 manufacturing facilities.Keep the flow record. The same platform discovers and classifies every device on the plant network and records the flows between them, so the proof question is answered from data collected before the incident.Ransomware may still land, but when the plant's dependencies sit inside a boundary you can prove, it lands in IT, the line keeps running, and&nbsp;the restart conversation is about the office. If batch records and release systems still live on the enterprise side, the dependency question is telling you to bring them inside first. Once they are, the ledger does not have to start, whether or not you have eleven days of inventory in the cooler.If you want to know what your own plants would answer at hour two, we run OT architecture workshops that start from your line-side dependencies and work outward:&nbsp;request an OT architecture workshop. &nbsp;Or hear from our customers directly on how they are leveraging Zscaler OT Security solutions in their own environments.]]></description>
            <dc:creator>Bryan Ashley (Zero Trust Networking, Principal Architect)</dc:creator>
        </item>
        <item>
            <title><![CDATA[How to Secure Branch Networks Against Machine-Speed, AI-Driven Cyber Threats]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/how-secure-branch-networks-against-machine-speed-ai-driven-cyber-threats</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/how-secure-branch-networks-against-machine-speed-ai-driven-cyber-threats</guid>
            <pubDate>Wed, 23 Sep 2026 15:40:03 GMT</pubDate>
            <description><![CDATA[Anthropic’s&nbsp;Mythos disclosure in April confirmed what network security teams had been bracing for. A frontier model, without cybersecurity-specific training, autonomously discovered and wrote working exploits for thousands of zero-day vulnerabilities, including 181 against a single browser. Most importantly, AI was now able to assemble existing, individually unremarkable vulnerabilities into a working attack chain.That changed the meaning of the CVE backlog for network security teams.&nbsp;Firewalls, VPN concentrators, badge readers, OT controllers: each class of device has its own vendor, its own update process, and its own maintenance window. Some equipment cannot be patched at all — locked to vendor firmware, or running years beyond end of support. So teams triage by severity, fix what they consider critical, and let the rest pile up in the backlog.&nbsp;That way of triaging worked for as long as chaining those CVEs together required a skilled human attacker with plenty of time and patience. Mythos ended that era. The backlog has become the raw material of AI-composed attack chains that can assemble faster than a team can schedule a change window.The Cloud Security Alliance (CSA) has responded to this AI-based threat with their recommendations for getting "Mythos Ready", highlighting&nbsp;eleven priority actions. Most revolve around building the security program: governance, rebuilt risk models, a permanent VulnOps function. But several are about architecture, and those land squarely on the infrastructure that network security teams run every day: the edge devices, the site-to-site mesh, the branch inspection stack, and the change process.&nbsp;When the branch is&nbsp;built like a café, with every site connected to the internet and all connections proxied through the cloud-based Zscaler Zero Trust Exchange,&nbsp; AI attacks chains suddenly stop cold. There’s no attack surface to explore, and there’s no way&nbsp; for malware to move laterally.&nbsp; That model, built on Zero Trust principles, delivers on the architectural actions the CSA calls for. We can condense these into four core tenets:Hide,Contain,Inspect, andRespond.Hide: Remove the Chain’s Starting PointBy nature, legacy networks are inherently exposed to AI-based attack chains. Every branch firewall, VPN concentrator, and SD-WAN appliance with a public IP sits in scanning databases anyone can query, announcing what it is and what version it runs. That identifying detail (vendor, model, and software version) is the device's fingerprint, and it tells an AI attacker exactly which CVEs your team has not fixed yet. The attacker then lines them up one by one, starting with whatever gets it in the door. The next flaw lets it read something it should not, and then a third raises its permissions. Each can be a moderate vulnerability that typically belongs in the backlog, but by exploiting them in sequence, the AI attacker can gain control of the appliance and spread from there.What Zero Trust Branch changes: branch connectivity is outbound-only to the&nbsp;Zero Trust Exchange. No inbound listener, no DNS record resolving to the site, no port that answers a probe. A scan returns no fingerprint, and without one, the attacker has no starting point to build a chain from. All devices and their CVEs are hidden from public view, preventing an AI attacker from finding a foothold to start the chain from.This directly aligns with CSA Priority Action #7 (Inventory and Reduce Attack Surface) by eliminating public reachability. Enforcing an outbound-only footprint also supports CSA Priority Action #4 (Prepare for Continuous Patching). When a device can be fingerprinted from the internet, every unpatched CVE on it is a race against an external attacker. When there is no fingerprint, your team patches on its own change window, not the attacker's timeline.Contain: Collapse the Blast Radius the Chain Depends OnHiding the branch denies an AI attacker a starting point from the internet, but compromise can arrive other ways: a contractor laptop, a vulnerable badge reader, or a poisoned update to a site controller. Once the attacker is inside, traditional network-centric segmentation works in its favor. With access managed based on network subnets, a site-to-site VPN mesh allows every branch to reach every other branch's address space, making the routing table a map for the AI attacker. One compromised device can open a path to every other site and the data center behind them, putting unpatched devices across the estate within reach. At each site, the attacker bypasses legacy network boundaries to enumerate local devices, including the cameras, badge readers, and OT controllers your team cannot patch, testing each one at machine speed.What Zero Trust Branch changes:&nbsp;legacy network-centric segmentation is replaced with software-defined, agentless microsegmentation at the branch edge. The Zero Trust Exchange brokers every connection between users and devices to authorized applications. A compromise in one branch cannot spread to another location. Within the branch, agentless microsegmentation isolates every device into a software-defined "network of one" without requiring complex VLAN redesigns or endpoint agent installations. If an exposed IP camera is compromised, microsegmentation instantly collapses the blast radius—preventing lateral movement and leaving the attacker with nowhere to go.This is the approach CSA Priority Action #8 (Harden Your Environment) calls for, using deep segmentation to limit how far an intrusion spreads once it lands. When each device is isolated, a compromise stays a single-device incident, and the equipment your team cannot patch no longer puts the rest of the estate at risk.Inspect: See the Chain While It Is Still Being AssembledContainment limits where an attacker can go, but they still have to communicate to finish the chain. The attacker reaches out to the internet, pulls down tools, and establishes command-and-control channels, producing traffic with each step. At most branches today, this traffic is inspected by the same local hardware appliance that routes it, and performing full SSL/TLS decryption is a heavy computational burden. When traffic spikes during a backup window or a video-heavy afternoon, the appliance runs out of CPU headroom. To keep the site working, sessions get exempted from decryption which quietly narrows inspection coverage, enabling the attacker's traffic to hide inside ordinary encrypted web sessions. This can persist for weeks inside a branch that falsely believes it is inspecting everything.What Zero Trust Branch changes: inspection moves off the branch appliance and into the cloud-based Zero Trust Exchange. Every flow is inspected, whether it comes from a user or device, and is never scaled back when a site gets busy so attacker traffic cannot hide inside encrypted sessions. Because the Zero Trust Exchange also inspects traffic across thousands of organizations, a threat pattern detected at one branch is immediately shared and blocked across all of them. By forcing every outbound request through this global security fabric, you systematically dismantle the communication channels the attacker needs to complete their chain.This is the other half of CSA Priority Action #8 (Harden Your Environment): egress filtering, which inspects traffic leaving the site to catch a chaining attack before it completes. When inspection is offloaded to the cloud, threat protection holds no matter how busy a site gets, allowing your team to disrupt the attack chain while it is still assembling.Respond: Policy That Moves at Machine SpeedAs inspection uncovers clear signs of an ongoing intrusion, response must take over immediately to stop the attack where it lies. Unfortunately, legacy response remains bottlenecked by manual, human-speed workflows—generating tickets, waiting for emergency change approvals, and logging into individual appliances. This operational latency is outmatched by autonomous, machine-speed AI threats, making every second of delay an open window for the attacker. That time gap is why an organization can have direct visibility into an attack and still be breached by it.What Zero Trust Branch changes:&nbsp;an automated incident response loop eliminates human latency from the defensive path. Security teams pre-approve response playbooks in advance. A confirmed threat signal triggers immediate containment through the Ransomware Kill Switch, completely bypassing triage delays, change approval windows, and manual site-by-site logins. Also, microsegmentation automatically isolates the compromised asset from all other local devices and remote sites by default. By instantly collapsing the threat's blast radius to a single device, this surgical response merges detection and containment into a single, unified event and ensures branch operations continue uninterrupted.This aligns with CSA Priority Action #10 (Build an Automated Response Capability) by enabling systemic, autonomous defense at the edge. When incident response relies on manual tickets and approvals, an AI adversary dictates the pace of the breach. By pre-authorizing automated response playbooks, you shift change control from a frantic, mid-incident scramble to a strategic, pre-built defensive move. Change control still happens, just before an incident rather than in the middle of one.An AI-composed attack chain needs four things: somewhere to land, somewhere to go, somewhere to take cover, and time to work.&nbsp;Your backlog can't take those away. Your architecture can.Zero Trust Branch Puts You in ControlYour team's ongoing triage of the backlog was the right move when chaining CVEs took a skilled human attacker acting at human speed. AI has removed that constraint, and patching faster is now a losing race against a machine. An outdated legacy architecture inherently opens you up to attack by providing the network pathways an adversary needs to build an exploit chain.Zero Trust Branch neutralizes these chains through four tenets that work as a single cohesive set. Hide takes away somewhere to land. Contain takes away somewhere to go. Inspect takes away somewhere to take cover. Respond takes away time required to assemble. An attacker needs all four conditions to finish a chain, and losing even one disrupts their progress. Removing all four ensures that your CVE backlog no longer presents a systemic risk to your enterprise.Connect with our experts for a tailored architectural walkthrough and see how Zscaler secures your distributed branch locations against autonomous AI threats.]]></description>
            <dc:creator>Josh Pederson (Senior Product Marketing Manager - Zero Trust Branch)</dc:creator>
        </item>
        <item>
            <title><![CDATA[What OMB Memorandum M-26-15 Requires for Your Agency&#039;s PQC Migration Plan]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/what-omb-memorandum-m-26-15-requires-your-agency-pqc-migration-plan</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/what-omb-memorandum-m-26-15-requires-your-agency-pqc-migration-plan</guid>
            <pubDate>Mon, 21 Sep 2026 20:41:44 GMT</pubDate>
            <description><![CDATA[The clock is already running. Here's what compliance with EO 14412 actually demands and where agencies can't afford to miss a step.If you work in security or networking for a U.S. federal agency or a firm that holds federal contracts, Executive Order 14412 is no longer a future concern. It's a present operational mandate. And with OMB Memorandum M-26-15 now in effect, the transition from awareness to accountability is complete.This blog covers what you need to know about the OMB’s guidance so you can include the required information in your PQC transition plan, which is due to the OMB by October 22, 2026. Why EO 14412 Exists: The Threat Is Already ActiveBefore getting into compliance mechanics, it's worth understanding the driving threat model.EO 14412, "Securing the Nation Against Advanced Cryptographic Attacks," is built around one foundational problem: the cryptographic standards protecting federal data today will be broken by cryptographically relevant quantum computers (CRQCs). Some experts believe a viable CRQC could emerge by 2030.Adversaries are already executing "Harvest Now, Decrypt Later" (HNDL) campaigns. They're exfiltrating encrypted federal data today, stockpiling it with the intent to decrypt it once quantum hardware is available. Data with a long operational shelf life, including intelligence sources, health records, and financial instruments, is already compromised in this model. The deadline to act is not 2030. It's now.EO 14412 and the implementing guidance from OMB respond to this by shifting the federal government's posture from "we should plan to migrate" to "migration is policy, with named owners, hard deadlines, and enforceable consequences."Who Owns the Governance StructureEO 14412 establishes clear accountability at the top:OMB Director and the National Cyber Director jointly coordinate the government-wide migration.NIST, CISA, and NSA provide agencies technical implementation guidance.Each agency head was required to designate a PQC Migration Lead within 30 days of the order, a deadline that passed in July 2026.If your agency hasn't named a PQC Migration Lead yet, that is already a compliance gap.The Migration Lead isn't just a title. This individual owns accountability for the entire transition process and is responsible for coordinating across IT, cybersecurity, legal, procurement, and program offices. The cross-functional scope is intentional: PQC migration cannot be solved by the security team alone. OMB M-26-15: The Binding Implementation MemoIssued June 24, 2026, OMB Memorandum M-26-15 ("Execution of the Migration to Post-Quantum Cryptography") is the document that turns EO 14412 into operational requirements. It establishes expectations, timelines, and the structure of what agencies must produce.The first hard deadline it creates: every&nbsp;civilian agency must submit a comprehensive PQC Migration Plan to OMB and the Office of the National Cyber Director (ONCD) by October 22, 2026. That is 30 days from this blog’s publication date. (Note that M-26-15 does not apply to National Security Systems, which follow a separate migration track.) What Must Be in the Migration Plan: Nine Required ElementsM-26-15 defines what a compliant migration plan must contain. Based on the memo's requirements, here are the nine core components agencies must address:1. Governance and Named AccountabilityThe plan must document who is responsible for the transition. The designated PQC Migration Lead must be identified, with a clear governance structure that spans the CIO, CISO, program offices, and procurement. A plan that assigns cryptographic transition to a single team will not satisfy M-26-15's cross-functional governance requirement.&nbsp;&nbsp;2. A Complete Cryptographic InventoryYou cannot migrate what you haven't mapped. The plan must describe the methodology used to inventory every cryptographic algorithm, key, certificate, and protocol in use across the agency's systems and infrastructure. This inventory, often called a Cryptographic Bill of Materials (CBOM), must be:Comprehensive (covering applications, network infrastructure, SaaS, cloud services, and on-prem systems)Automated (not a one-time manual exercise)Continuously maintainedNote: CISA and NIST are expected to publish minimum-elements guidance for machine-readable CBOMs by March 2027. Agencies should build toward that standard now.3. Risk-Based System PrioritizationNot all systems carry equal urgency. The migration plan must include a risk-based prioritization framework that identifies which systems get migrated first. Mandatory first-priority categories include:High Value Assets (HVAs) as defined in OMB M-19-03High-Impact Systems (FIPS 199 "High" categorization)Any system storing or transmitting data with long-term sensitivity, the primary targets of HNDL attacks4. Phased Milestones Aligned to the Government-Wide ScheduleM-26-15 establishes a five-phase migration timeline. The October submission must map agency-specific milestones to the three migration phases within this five-phase schedule:PhasePeriodFocusPhase 12026–2027Strategy, planning, and discoveryPhase 22027–2028Pilots and early migrationPhase 32028–2030Prioritized migration (key establishment for HVAs and high-impact systems)Phase 42031Digital signature migrationPhase 52035Full migration of remaining systemsThe Phase 3 deadline is the one with the most regulatory weight: December 31, 2030 is the hard cutoff for PQC key establishment across HVAs and high-impact systems. M-26-15 also directs agencies to prioritize systems containing highly sensitive data and systems particularly vulnerable to CRQC-based attacks on that schedule.&nbsp;&nbsp;&nbsp;5. TLS 1.3 Deployment MilestonesAgencies must specifically address migration to TLS 1.3, consistent with existing mandates under EO 14306. The overall federal deadline for TLS 1.3 support is January 2, 2030. Your plan must include milestones for testing and deploying PQC-enabled TLS 1.3 within that window.6. A Cryptographic Agility ArchitectureThis is arguably the most technically demanding requirement. Agencies must describe an architecture designed so that cryptographic algorithms can be swapped with minimal operational disruption as standards evolve. Depending on the agency’s risk assessment and technical requirements, this can include:Supporting cryptographic modes that run PQC algorithms alongside classical ones during the transition period (so you don't break existing interoperability while hardening new sessions)Ensuring Hardware Security Modules (HSMs) and Key Management Systems are replaceableTreating crypto-agility as an architecture requirement, not a feature request7. Vendor and Supply Chain CoordinationFederal agencies don't operate in isolation — much of the cryptographic footprint runs on commercial software, cloud platforms, and contractor-managed systems. The plan must detail:How the agency will engage Cloud Service Providers (CSPs) under the shared-responsibility model1Contract language and procurement requirements that mandate vendor PQC readiness and cryptographic agilityHow the agency will assess and manage cryptographic vulnerabilities in the supply chainThe first FAR Council rulemaking, due December 19, 2026, is required to propose that covered contractors comply by December 31, 2030, with applicable NIST FIPSs, including PQC-compliant algorithms. A second FAR Council rulemaking, due March 19, 2027, is required to propose changes to contractor vulnerability disclosure program (VDP) requirements covering cryptographic vulnerabilities. Contracting officers and procurement leads should be tracking both of these closely.8. Resource and Funding EstimatesOMB expects agencies to connect PQC migration to budget realities. The plan must include estimates of funding and personnel required, integrated into existing IT modernization budgets and multi-year appropriations requests. Plans without resource estimates will not satisfy M-26-15’s minimum requirements.9. Risk Management During the Transition PeriodBecause full migration takes years, agencies must address how they'll manage security risk during the transition, specifically the period when some systems are migrated and others aren't. This includes interoperability between PQC and legacy systems, monitoring for exposure in hybrid environments, and defining acceptable risk posture throughout each phase. What's Happening on the GSA and DoW TracksThe civilian agency plan submission is the most immediate requirement, but two parallel tracks deserve attention:GSA has been directed to establish an inter-agency working group to modernize Federal Identity, Credential, and Access Management (FICAM) to support PQC. That group held its first meeting on August 12, 2026, with participation from 17 federal agencies and plans to meet on a bi-weekly basis. FICAM modernization has direct implications for how agencies manage identity verification, PKI, and digital signatures, all of which will require quantum-resistant cryptographic underpinning.The Department of War (DoW) is operating under its own PQC strategy, released June 23, 2026. All DoW systems must support PQC or be phased out by December 31, 2030. Solutions using CRQC-vulnerable algorithms, non-quantum-resistant symmetric key establishment, and non-NSA-KMI PSK solutions are all on the phaseout list by that date. Defense contractors face the most compressed timelines of any segment. What This Means for Contractors and SubcontractorsIf your firm holds federal contracts, EO 14412 reaches you through two mechanisms:The first FAR Council rulemaking (due December 19, 2026) must propose that covered contractors comply with applicable NIST FIPS, including PQC-compliant algorithms by&nbsp; December 31, 2030, matching the agency deadline for HVA key establishment.A second FAR Council rulemaking (due March 19, 2027) must propose amendments to FAR requirements and contract clauses for contractor Vulnerability Disclosure Programs, including coverage of cryptographic vulnerabilities,.lack of encryption, and non-FIPS-approved algorithms. This is a significant expansion: VDPs that don't address crypto will no longer satisfy requirements.The practical implication: start your own cryptographic inventory now, not when the FAR rule is finalized. Agencies will increasingly require vendors to demonstrate a clear PQC roadmap as part of procurement. Firms that can't show one will find themselves losing competitive ground on contract renewals and new awards, well before the 2030 deadline. The Practical Starting Point: Your First 90 DaysGiven that the migration plan submission deadline is October 22, any agency team, including its supporting contractors, that hasn't started needs a rapid on-ramp. The work breaks down into three phases:Days 1–30 — Foundations:&nbsp;Appoint your PQC Migration Lead and form a cross-functional team. Initiate a cryptographic inventory (automated tools are essential — this cannot be done by hand at scale). Begin vendor and supply chain assessment. Prepare and submit the initial migration plan by October 22. M-26-15 treats the plan as a dynamic document that will mature as the inventory and implementation strategy develop.Days 31–60 — Assessment and Prioritization:&nbsp;Complete the initial CBOM. Conduct a risk assessment and prioritize systems by sensitivity, internet exposure, and operational importance. Pay special attention to anything protecting long-lived data: these are the HNDL targets. Refine your migration strategy and roadmap.Days 61–90 — Strategy and Early Implementation: Update and socialize the migration plan with leadership. Begin a pilot project on a non-critical system to test PQC algorithms before touching HVAs. Start migrating to post-quantum key exchange (ML-KEM / FIPS 203) where feasible. Update procurement policies and contract language to require PQC readiness from vendors going forward. Conclusion: The Bottom LineEO 14412 and OMB M-26-15 represent the federal government's most concrete response yet to the quantum threat. For agencies, these are binding mandates with named owners, firm deadlines, and budget implications. For contractors, two FAR rulemakings will translate the policy into formal acquisition requirements.&nbsp;&nbsp;For security and networking practitioners, the critical action items are clear:If you haven't mapped your cryptographic assets, that is the first thing to fix.If your agency doesn't have a Migration Lead, identify one ASAP.If your firm holds federal contracts, assume FAR requirements are coming and get ahead of them.The threat actors running Harvest Now, Decrypt Later campaigns are not waiting for 2030. Your migration plan shouldn't wait for October 22 either.Sources:&nbsp;EO 14412 ("Securing the Nation Against Advanced Cryptographic Attacks")OMB Memorandum M-26-15: "Execution of the Migration to Post-Quantum Cryptography” June 24, 2026Zscaler Webinar — "EO 14412 Decoded: Your First 90 Days" (watch it now)Notes:1 M-26-15 assigns CISA and DoW, in coordination with GSA, to lead PQC migration efforts for FedRAMP-authorized CSPs and SaaS, PaaS, and IaaS solutions used by more than one agency.]]></description>
            <dc:creator>Brendon Macaraeg (Principal Product Marketing Manager)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Lessons from Recent Outages: How Smart Enterprises Stay Ready]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/lessons-recent-outages-how-smart-enterprises-stay-ready</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/lessons-recent-outages-how-smart-enterprises-stay-ready</guid>
            <pubDate>Mon, 21 Sep 2026 12:05:29 GMT</pubDate>
            <description><![CDATA[Unforeseen outages aren't a matter of if. They're a matter of when. The question is whether you're ready.In the past few weeks, Microsoft, Google Cloud, and Salesforce, all experienced significant disruptions, leaving work interrupted, revenue lost, and reputations tested.&nbsp;During the&nbsp;Salesforce disruption on September 16, an authentication infrastructure failure cascaded into a full platform outage, bringing down the CRM, APIs, and support portal and affecting hundreds of customer instances across six countries for nearly three hours.&nbsp;For IT teams managing incidents like this one, visibility is everything: knowing what’s wrong, where, and why, before users start calling the helpdesk.&nbsp;Zscaler Digital Experience (ZDX) gives IT teams exactly that: end-to-end visibility from user devices, across any network, to the apps they depend on.ZDX detected a sharp decline in Salesforce Lightning experience scores and alerted IT teams. Network latency held steady throughout, which told teams exactly what they were dealing with: the problem wasn't the network. It was the application. Using the&nbsp;ZDX Agent, teams identified the root cause within minutes and had a specific next step, rather than just an alert that Salesforce was slow. Here’s what that looked like:ZDX score trend showing VIP user experience on Salesforce Lightning drop from Good to Poor in the early hours of September 16.&nbsp;ZDX probe data showing response times spiking to 9-11 seconds and synthetic scores dropping sharply during the September 16 outage window.That data, captured in real time, tells you what's wrong before anyone has to ask. In the Salesforce example, the network was clean. The problem was upstream at the application layer. That diagnosis, the kind that used to take hours of manual investigation, took minutes. Observe, diagnose, act. That is the loop that separates resilient enterprises from reactive ones. ZDX isn't just useful during incidents. It's how enterprises maintain uptime confidence every day. That’s visibility. But what happens when the disruption hits your own security infrastructure?Your Security Infrastructure Needs a Plan TooZscaler runs the world's largest inline security cloud,&nbsp;backed by a 99.999% industry-leading uptime SLA with built-in resilience for all common failure scenarios. That's not a footnote, it's the foundation. But, even the most resilient infrastructure doesn't eliminate the need for a plan.Just like you plan for redundancy in your data centers with multiple ISPs, or for hyperscaler workloads with multi-region backups, your most critical security services need a DR and business continuity plan (BCP) too.When disruptions hit, the instinct to route around security is dangerous. Bad actors actively exploit these moments, knowing the safeguards are down.This Is What a Real Continuity Plan Looks LikeWhen it comes to DR/BCP for the Zero Trust Exchange, organizations typically consider two approaches:Scramble unprepared. Look for workarounds with no guarantee of continuity, leaving users without secure access when it matters most.Buy Business Continuity Cloud and avoid disruption. Zscaler provides both the primary and an isolated backup cloud. That's exactly what Zscaler Business Continuity Cloud is built for.&nbsp;In normal operations, all users, branches, and workloads transact securely through the Zero Trust Exchange. The Business Continuity Cloud sits fate-separated in the background, fully managed and ready, so when a critical failure hits, the infrastructure is ready to respond.Zscaler Business Continuity Cloud is a dedicated, per-customer read-only private cloud with an isolated data plane and control plane, completely independent of the primary Zscaler cloud, running in a last-known good state and continuously syncing policy.&nbsp;When the Zero Trust Exchange becomes unreachable, Zscaler Client Connector automatically reroutes to the backup cloud.&nbsp;For your users, it's seamless: no manual intervention, no re-logins, no help desk tickets.For your security team, it's not a degraded fallback: same policies, same inspection engines, logs still streaming. Consistent Zero Trust posture maintained through the disruption.&nbsp;For IT,&nbsp;deployment is a natural extension of your existing Zscaler environment with flexible deployment options: a Zscaler-managed service across 9+ global data centers , customer-hosted, or hybrid. Further, you can run fire drills in peacetime, so the first time you activate it isn't during an actual incident.The Time to Build Your Continuity Plan Is NowMany of Zscaler's largest global organizations have already adopted and deployed Business Continuity Cloud successfully. And for organizations subject to mandatory operational resilience regulations like DORA, CPS 230, or ISO 22301, Business Continuity Cloud is also a concrete, auditable step toward meeting mandatory resilience requirements, with serious financial penalties increasingly on the line.Start with visibility. Build in continuity.&nbsp;ZDX and&nbsp;Zscaler Business Continuity Cloud give you both.]]></description>
            <dc:creator>Lidor Pergament (Director, Product Management)</dc:creator>
        </item>
        <item>
            <title><![CDATA[When AI Agents Go Rogue- What the OpenAI–Hugging Face Incident Teaches Us About Workload Zero Trust]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/when-ai-agents-go-rogue-what-openai-hugging-face-incident-teaches-us-about</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/when-ai-agents-go-rogue-what-openai-hugging-face-incident-teaches-us-about</guid>
            <pubDate>Fri, 18 Sep 2026 18:19:45 GMT</pubDate>
            <description><![CDATA[The Attacker Was New. The Security Gaps Were Not.In August 2026, OpenAI described an unprecedented internal cybersecurity incident: autonomous AI agents running in an evaluation environment escaped their intended boundaries and compromised systems at&nbsp;OpenAI and Hugging Face — with no human directing the attack.The agents abused limited internet access through Artifactory, OpenAI’s internal package manager, then chained vulnerabilities, harvested exposed credentials, and expanded access across Hugging Face infrastructure. The incident shows how quickly an autonomous system can turn a narrow weakness into a cross-environment intrusion.Yet the underlying architecture problems are familiar: a trusted workload could reach more of the internet than it needed, and a compromised workload could reach too much of the internal environment. For security teams, the lesson is straightforward — AI agents are workloads, and workloads should never be trusted simply because they run inside the cloud. Zero Trust: Give Every Workload Access to Only What It NeedsExtending Zero Trust architecture to workloads can be simplified using the following best practices:1. Control workload egress by destination and purpose.Artifactory needed legitimate access to software repositories. The problem was treating that requirement as general internet access. The agents used server-side request forgery (SSRF) — a technique that tricks a server into making network requests on an attacker’s behalf — to turn an approved service into an outbound proxy.Instead of letting workloads connect to the entire internet, a Zero Trust approach restricts access using precise rules based on who is connecting, what app they are using, and where they are going. A Zero Trust architecture restricts a service like Artifactory to sanctioned package registries and required protocols — requests to arbitrary destinations are denied at an inline enforcement point instead of quietly succeeding. Inspection and logging turn a slow-moving compromise into an early signal.Broad trustArtifactory → internetLeast privilegeArtifactory → approved package registries onlyCompromise attemptArtifactory → unapproved destination → blocked by egress policyThe agents reportedly experimented with outbound communication before establishing a persistent channel. TLS inspection and egress telemetry give defenders visibility into unusual destinations, request patterns, and protocols as they emerge — turning weeks of undetected probing into actionable evidence much earlier in the sequence, well before a channel becomes persistent.2. A compromised workload should not inherit reachability.&nbsp;After the agents obtained valid credentials, the incident expanded from a single worker pod to broader Hugging Face infrastructure. This is the critical Zero Trust distinction: identity is not reachability. A stolen credential may satisfy one part of an access decision, but it should not automatically create a network path to a control plane, database, messaging system, or code repository.See the entire east-west path, from the pod up to the region.A Zero Trust approach treats east-west traffic as a single, layered problem rather than two separate ones. Microsegmentation covers what happens inside a VPC or VNET — mapping workload-to-workload communication and surfacing exactly how pods and hosts are actually talking to one another within that boundary. Macrosegmentation picks up where a VPC or VNET ends: any traffic that crosses into another VPC/VNET, cluster, or region gets the same visibility, plus policy-driven control over whether that crossing is allowed at all.Together, that’s full end-to-end visibility across the whole path this incident actually took — from a single compromised worker inside its VPC, out across a boundary into another cluster, and again into a different region entirely. In an incident built on exactly that kind of expanding lateral reach, having both layers mapped is what turns “we don’t know how far this could spread” into a concrete picture of every hop involved, and a clear boundary at which to enforce.Enforce at the boundary.Macrosegmentation is deployed at exactly that boundary turning cross-boundary visibility into a live control point. Traffic crossing between VPCs/VNETs, clusters, or regions is policy-defined by default: a workload in one zone has no path into another until that path is explicitly authorized and enforced inline. It’s the same architecture end to end — Microsegmentation and Macrosegmentation aren’t two separate tools stitched together after the fact, but one layered view of east-west traffic that adds control at the point where it matters most: the boundary a compromise would otherwise cross unnoticed.3. Make stolen credentials insufficient.&nbsp;Credential protection remains essential, but architecture should assume that credentials can be exposed. The practical questions become whether the holder can reach the target service, and whether the attempted connection matches policy.Kubernetes credential: Can the workload reach the Kubernetes API from this zone?Database credential: Is the database reachable from this workload identity and application path?Repository credential: Can the workload establish the required connection to the repository service?Pairing identity with explicit connectivity policy strips a stolen secret of most of its value and limits the blast radius even when prevention fails.4. Turn credential probing into an early warning.&nbsp;Place decoy credentials, canary tokens, and lookalike resources throughout the environment. Interaction with a decoy produces a high-confidence alert with none of the false-positive noise of traditional monitoring — exactly the kind of signal a systematic credential-harvesting campaign like this one would trip.That signal gives a security team the one thing this incident lacked for nearly six weeks: an early, credible reason to look. Acting on that signal today runs through existing manual or integrated response workflows; closing the loop from alert straight to automated containment is where this architecture is headed next, not where it stands today. OpenAI’s Own Roadmap Is Describing This ArchitectureStronger isolation and tighter network controls — OpenAI’s stated fix — is workload Zero Trust in different words.&nbsp;OpenAI’s stated direction is more isolation for workloads executing untrusted code, plus network controls that prevent one compromised workload from gaining unauthorized access to the internet or internal networks. In plain language, that’s workload-to-internet and east-west VPC/VNET control, deployed without agents on every host. That capability is available today as Zero Trust Gateway for Cloud Workloads — the architecture OpenAI is now building from scratch already exists as a packaged offering.The agents didn’t stop at Hugging Face.&nbsp;They pivoted to Modal, a third AI cloud platform, compromising an unrelated customer application there while hunting for a way past their evaluation. It’s a useful reminder of why allowlisting beats blocklisting: policy built on where a workload is permitted to go stops a pivot to Modal the same way it stops a pivot to Hugging Face — it doesn’t need to already know the next destination an attacker will try. What Security Teams Should Do NowInventory workload egress. Find workloads with broad internet access and replace it with destination-, application-, and protocol-specific policy.Map the full east-west path. Use Microsegmentation for intra-VPC/VNET visibility and Macrosegmentation for cross-boundary visibility and control, together, to baseline expected flows and spot risky lateral-movement paths before an attacker finds them first.Enforce boundaries. Deploy Macrosegmentation via Zero Trust Gateway and Cloud Connector to control traffic across applications, clusters, VPCs/VNETs, and regions.Assume credentials will be stolen. Require both valid identity and an approved network path to sensitive services.Inspect encrypted workload traffic. Look for unusual destinations, protocols, and communication patterns while accounting for privacy and operational requirements.Treat AI agents as untrusted workloads. Grant only the connectivity needed for the task, and design response processes for machine-speed activity.The attacker may move at machine speed. Your blast radius should not.Agentic AI can discover vulnerabilities, chain techniques, and move across infrastructure faster than human-led attacks. OpenAI’s own incident-response roadmap points the same direction as the rest of this piece: toward fully autonomous shutdown procedures, because manual, human-paced response is already understood internally as too slow against agent-speed threats. That’s the same reasoning behind pairing workload Zero Trust with high-fidelity, signal-driven containment — closing the gap between detection and action as that automation matures.No single control can be assumed to prevent every step of an attack like this one. The durable answer is an architecture that assumes any workload can be compromised, gives every workload only what it needs, and makes sure a single foothold never becomes free rein. THREE TAKEAWAYSAI changes attack speed — not Zero Trust fundamentals.End-to-end east-west visibility, with control at the boundary, closes the gap between compromise and containment.Machine-speed threats call for machine-speed response.This post is part of Zscaler's Zero Trust in Action series, analyzing current security incidents through the lens of Zero Trust Cloud capabilities. Learn more about how Zscaler helps implement Zero Trust architecture with microsegmentation across cloud workloads,&nbsp;here.&nbsp;]]></description>
            <dc:creator>Brian Pavane (Senior Director, Specialist Solution Architect)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Securing AWS Private Lambda with Zscaler Zero Trust Cloud]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/securing-aws-private-lambda-zscaler-zero-trust-cloud</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/securing-aws-private-lambda-zscaler-zero-trust-cloud</guid>
            <pubDate>Wed, 16 Sep 2026 05:14:00 GMT</pubDate>
            <description><![CDATA[Modern cloud architectures increasingly rely on&nbsp;AWS Lambda for event-driven processing, data ingestion, and microservice integration. While Lambda functions often run within private Virtual Private Clouds (VPCs) to keep data isolated, many serverless workloads still require outbound internet access to interact with third-party APIs, SaaS applications, or external data feeds.Without deep visibility into this outbound traffic, security teams face a critical blind spot. Attackers can leverage encrypted channels (HTTPS) to exfiltrate sensitive data or communicate with command-and-control (C2) servers. To combat these risks, organizations turn to&nbsp;Zscaler Zero Trust Cloud and Zscaler Internet Access (ZIA) for inline&nbsp;SSL/TLS Inspection.To seamlessly extend zero trust security to public cloud environments, Zscaler provides the Zscaler Zero Trust Gateway (ZTGW). ZTGW securely brokers outbound traffic originating from cloud workloads and private subnets, funneling it safely over encrypted DTLS tunnels into ZIA for policy enforcement and threat prevention.However, introducing SSL inspection into serverless environments presents a unique operational challenge:&nbsp;How do you distribute custom Root CA certificates to short-lived, ephemeral Lambda execution containers without breaking application code or requiring manual maintenance?In this blog, we’ll explore why SSL inspection is essential for serverless workloads, how to fully automate custom certificate distribution using AWS CloudFormation and S3, how to configure granular SSL inspection policies in ZIA, and how to verify everything in action. The Challenge: SSL Inspection vs. Ephemeral ExecutionWhen ZIA inspects outbound HTTPS traffic, it acts as a man-in-the-middle proxy. It terminates the TLS session from the client, inspects the payload for threats or Data Loss Prevention (DLP) violations, and establishes a new TLS session to the destination server. To accomplish this, ZIA re-signs the destination’s SSL certificate using a custom Zscaler Root or Intermediate CA.&nbsp;If the client runtime does not explicitly trust the Zscaler Root CA, the TLS handshake fails immediately with an error like:[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificateIn traditional virtual machines (like EC2), administrators deploy custom certificates via configuration management tools (Ansible, Chef) or golden AMI images. But AWS Lambda containers are&nbsp;ephemeral and managed entirely by AWS. Standard Linux system trust stores cannot be modified permanently at the OS image level.&nbsp; The Solution: Cold-Start Bootstrap &amp; Auto-Discovery PatternTo solve this challenge, we can implement an&nbsp;Automated Cold-Start Bootstrap Pattern.By storing our Zscaler Root CA certificate in an isolated Amazon S3 bucket within the VPC, the Lambda function can fetch the certificate during container cold boot, dynamically merge it with native Amazon Linux root CAs into /tmp/custom-ca-bundle.pem, and bind it to the Python SSL context. Architecture Overview Automating Certificate Distribution Step-by-StepLet's look at how the execution environment handles the certificate lifecycle automatically in the following steps.1.&nbsp;Zero-Trust Storage in Amazon S3The certificate resides in a dedicated S3 bucket protected with:Gateway VPC Endpoint: All traffic between Lambda and S3 remains on the AWS internal backbone without traversing NAT Gateways or the public internet.Restricted Bucket Policy: Blocks all access unless the request originates from the specific VPC Endpoint or authorized IAM roles in your AWS account.2.&nbsp;Smart Certificate Auto-Discovery &amp; NormalizationDuring cold start, the Lambda handler searches the S3 bucket for any certificate ending in .crt, .pem, or .cer (such as ZscalerRootCertificate-2048-SHA256-Feb2025.crt).Certificates uploaded by security teams often vary in encoding (ASCII PEM vs. Binary DER) or contain UTF-8 Byte Order Marks (BOM headers) from Windows text editors. The bootstrap code automatically cleans and normalizes these files:import sslimport reimport boto3&nbsp;def extract_pem_certificates(raw_bytes):&nbsp;&nbsp;&nbsp;&nbsp;"""Parses, cleans, and converts raw bytes into valid PEM certificate blocks."""&nbsp;&nbsp;&nbsp;&nbsp;pem_blocks = []&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# Strip UTF-8 BOM headers (\xef\xbb\xbf) and decode&nbsp;&nbsp;&nbsp;&nbsp;text_content = raw_bytes.decode('utf-8-sig', errors='ignore')&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# Regex search for ASCII PEM certificate blocks&nbsp;&nbsp;&nbsp;&nbsp;matches = re.findall(r'-----BEGIN CERTIFICATE-----[\s\S]*?-----END CERTIFICATE-----', text_content)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if matches:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return [m.strip() + '\n' for m in matches]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# Fallback for Binary DER encoded certificates&nbsp;&nbsp;&nbsp;&nbsp;try:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;pem_cert = ssl.DER_cert_to_PEM_cert(raw_bytes)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return [pem_cert.strip() + '\n']&nbsp;&nbsp;&nbsp;&nbsp;except Exception as e:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;print(f"Failed to parse DER certificate: {e}")&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return []&nbsp;3.&nbsp;Merging with Native System CAsTo ensure the Lambda function trusts both public internet sites and Zscaler re-signed sessions, the handler merges native Amazon Linux system CAs (/etc/pki/tls/cert.pem) with the extracted Zscaler Root CA into a single /tmp/custom-ca-bundle.pem file.def build_trust_store(bucket_name):&nbsp;&nbsp;&nbsp;&nbsp;bundle_path = "/tmp/custom-ca-bundle.pem"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# 1. Copy standard Amazon Linux system CAs&nbsp;&nbsp;&nbsp;&nbsp;with open("/etc/pki/tls/cert.pem", "r") as sys_in, open(bundle_path, "w") as bundle_out:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bundle_out.write(sys_in.read() + "\n")&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# 2. Download and append Zscaler Root CA from S3&nbsp;&nbsp;&nbsp;&nbsp;s3 = boto3.client('s3')&nbsp;&nbsp;&nbsp;&nbsp;objects = s3.list_objects_v2(Bucket=bucket_name).get('Contents', [])&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;for obj in objects:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if obj['Key'].endswith(('.crt', '.pem', '.cer')):&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;response = s3.get_object(Bucket=bucket_name, Key=obj['Key'])&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cert_bytes = response['Body'].read()&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;pem_blocks = extract_pem_certificates(cert_bytes)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with open(bundle_path, "a") as bundle_out:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;for pem in pem_blocks:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bundle_out.write(pem + "\n")&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;print(f"Appended {len(pem_blocks)} certificate block(s) from {obj['Key']}")&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return bundle_path&nbsp;4. Binding the Trust Store to Python RuntimeFinally, during outbound calls, the Lambda handler configures ssl.create_default_context pointing directly to /tmp/custom-ca-bundle.pem:import urllib.request&nbsp;# Create SSL context using the combined trust storessl_context = ssl.create_default_context(cafile="/tmp/custom-ca-bundle.pem")&nbsp;# Outbound HTTPS request now seamlessly trusts Zscaler re-signed certificatesreq = urllib.request.Request("https://ipinfo.io", headers={"User-Agent": "AWS-Lambda-URL-Checker"})with urllib.request.urlopen(req, context=ssl_context, timeout=10) as response:&nbsp;&nbsp;&nbsp;&nbsp;body = response.read().decode('utf-8')&nbsp; Crafting SSL Inspection Policies in Zscaler Internet Access (ZIA)With the Lambda trust store in place, we can configure ZIA to inspect outbound HTTPS traffic. ZIA offers two powerful methods for scoping SSL inspection rules to AWS serverless workloads.Option 1: Scoping Policy via Sub-Locations (IP / Subnet Based)If your Lambda functions are deployed into dedicated private subnets, you can scope policies based on subnet CIDRs.1. Create a Sub-Location in ZIA:In the&nbsp;ZIA Admin Portal, navigate to&nbsp;Administration &gt;&nbsp;Location Management.Locate your AWS location and click&nbsp;Add Sub-Location.Define the IP range corresponding to your private Lambda subnet (e.g., 10.0.2.0/24).2. Build the SSL Inspection Rule:Navigate to&nbsp;Policy &gt;&nbsp;SSL Inspection &gt;&nbsp;Add SSL Inspection Rule.Under&nbsp;Criteria, select your newly created Sub-Location.Under&nbsp;Action, select&nbsp;Inspect and assign your Zscaler Intermediate CA.Option 2: Scoping Policy via Workload Groups (Leveraging AWS Native Metadata)For modern cloud environments where IP addresses are dynamic, ZIA supports&nbsp;Workload Groups. This approach maps AWS-native attributes—such as Security Groups, Account IDs, or VPC IDs—directly into ZIA policy context without maintaining static IP ranges.Prerequisite: Ensure AWS Workload Discovery is enabled between your AWS Account and Zscaler. For setup details, see the official&nbsp;Zscaler Documentation on Adding an AWS Account.1. Define a Workload Group in ZIA:In ZIA, go to&nbsp;Administration &gt;&nbsp;Workload Groups &gt;&nbsp;Add Workload Group.Name the group (e.g., AWS-Lambda-Workloads).Add criteria matching your AWS infrastructure:VPC ID: vpc-xxxxxxxSecurity Group ID: sg-0123456789abcdef02. Apply Workload Group to SSL Inspection:Under&nbsp;Policy &gt;&nbsp;SSL Inspection, create a new rule.Under&nbsp;Criteria &gt;&nbsp;Workload Groups, select AWS-Lambda-Workloads.Set&nbsp;Action to&nbsp;Inspect.Benefits of Workload Group Scoping:Zero IP Management: Eliminates hardcoded subnet CIDRs or static NAT mappings.Auto-Scaling Protection: Any new Lambda function attached to the Security Group instantly inherits the correct SSL inspection policy. Demonstrating Verification &amp; TestingTo test the deployment, we invoke the URLStatusChecker Lambda function with a payload targeting https://ipinfo.io:Test Event Payload{&nbsp;"url": "https://ip.zscaler.com/?json"}&nbsp;Lambda Response Payload{&nbsp;"statusCode": 200,&nbsp;"url": "https://ip.zscaler.com/?json",&nbsp;"message": "Successfully connected to https://ip.zscaler.com/?json",&nbsp;"trustStoreUsed": "/tmp/custom-ca-bundle.pem",&nbsp;"responseBody": {&nbsp; &nbsp;"srcip": "n.n.n.n",&nbsp; &nbsp;"vip": "null",&nbsp; &nbsp;"nodename": "zs3-nnn-nnn-nnn",&nbsp; &nbsp;"cloud": "zscalerthree.net",&nbsp; &nbsp;"datacenter": "Washington DC IV",&nbsp; &nbsp;"xff": "n.n.n.n",&nbsp; &nbsp;"clientip": "n.n.n.n"&nbsp;},&nbsp;"responseHeaders": {&nbsp; &nbsp;"Date": "Wed, 16 Sep 2026 11:21:26 GMT",&nbsp; &nbsp;"Content-Type": "text/html;charset=UTF-8",&nbsp; &nbsp;"Transfer-Encoding": "chunked",&nbsp; &nbsp;"Connection": "close",&nbsp; &nbsp;"Server": "nginx",&nbsp; &nbsp;"X-Powered-By": "PHP/8.0.30",&nbsp; &nbsp;"Access-Control-Allow-Origin": "*",&nbsp; &nbsp;"Access-Control-Allow-Methods": "GET, OPTIONS, HEAD",&nbsp; &nbsp;"Strict-Transport-Security": "max-age=63072000; includeSubDomains",&nbsp; &nbsp;"X-Frame-Options": "SAMEORIGIN"&nbsp;}}&nbsp; Conclusion &amp; Key TakeawaysSecuring serverless egress traffic does not require sacrificing security visibility or burdening developers with complex certificate management code.By combining&nbsp;AWS CloudFormation, an&nbsp;isolated S3 bucket, and&nbsp;Zscaler Internet Access (ZIA):Security is Automated: Lambda functions dynamically discover and inject the Zscaler Root CA during cold start without modifying base images.Traffic is Fully Inspected: ZIA performs deep content inspection and threat analysis on encrypted outbound HTTPS sessions.Policy is Identity-Centric: Workload Groups tie ZIA policies directly to AWS Security Groups and cloud metadata, creating a scalable, zero-trust serverless architecture.&nbsp; Ready to Learn More?Check out the full CloudFormation deployment template (lambda-ssl-demo.yaml) and step-by-step setup guide in our GitHub repository to implement automated SSL inspection for your serverless workloads today!While this blog focuses on AWS Lamba, a similar approach can be leveraged for Serverless workloads in other cloud providers. E.g. Azure Functions &amp; Cloud Run in GCP.To learn more about Zscaler Zero Trust Gateway, click here.&nbsp;]]></description>
            <dc:creator>David Glading (Principal Specialist Sales Engineer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Extending Zero Trust to AI: What Federal Civilian Agencies Can Do Now]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/extending-zero-trust-ai-what-federal-civilian-agencies-can-do-now</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/extending-zero-trust-ai-what-federal-civilian-agencies-can-do-now</guid>
            <pubDate>Wed, 16 Sep 2026 03:28:29 GMT</pubDate>
            <description><![CDATA[This is the final post in a three-part series on AI security and governance for Federal Civilian agencies. The first post covered why M-25-21 changes the operating landscape. The second post introduced a six-part framework for secure AI adoption.Bottom line up front: Federal Civilian agencies have spent years moving toward Zero Trust. AI should be part of that strategy. Zscaler helps agencies extend Zero Trust principles into AI interactions across employee use, agency-built applications, and cloud environments. The practical starting point is visibility, followed by data protection, guardrails, testing, and governance evidence.&nbsp; AI creates new interaction points that Zero Trust must coverFederal agencies have spent years moving toward Zero Trust. AI should be part of that strategy.AI introduces new interaction points: prompts, responses, models, agents, AI APIs, embedded AI, AI-enabled SaaS, coding assistants, RAG pipelines, vector databases, MCP servers, tool-calling workflows, and agency-built AI applications.Each one can become a path for data exposure, unauthorized access, manipulation, or mission risk.A Zero Trust approach to AI asks practical questions. Who is using the AI system? What application or model are they accessing? What data is being shared? Is the user authorized? Is the tool approved? Is the destination trusted? Is sensitive data involved? Is the AI response safe and appropriate? Is the AI system acting within its mission scope? Is the interaction logged and governed? Can policy be enforced in real time?Zscaler helps agencies extend Zero Trust from users, devices, applications, branches, and workloads into AI interactions. This includes securing employee AI use, discovering AI assets, protecting sensitive data, applying guardrails, testing agency-built AI applications, and monitoring AI behavior over time. Where Zscaler fitsZscaler's role is to help Federal Civilian agencies make secure AI adoption operational. The platform supports three main areas.AI asset management helps discover and inventory AI use across endpoints, traffic, SaaS, code, and cloud environments. This supports governance, inventory, visibility, and risk prioritization.Secure access to AI applications helps protect employee use of public GenAI and embedded AI applications through access control, DLP, browser isolation, prompt inspection, response inspection, and AI Guard. This supports acceptable-use policy enforcement and sensitive data protection.Secure AI applications and infrastructure helps protect agency-built AI applications, agents, and model interactions through proxy or API-based guardrails, AI red teaming, model benchmarking, prompt hardening, and continuous monitoring. This supports public trust, mission alignment, and risk management for higher-impact AI systems.These capabilities help agencies answer the questions at the center of M-25-21 compliance: What AI is being used? What data does it touch? Who is using it? What risks exist? What controls are applied? What systems have been tested? What evidence can we provide? And how do we enable AI safely at mission speed? What this looks like across missionsSecure AI adoption will look different depending on the agency's mission.A&nbsp;benefits agency may want to use AI to help employees summarize case information, while preventing exposure of PII or unauthorized eligibility guidance.A&nbsp;public health agency may want to use AI to synthesize research, but needs responses grounded in authoritative sources.A&nbsp;regulatory agency may want to use AI to assist with inspections, investigations, or compliance reviews, while protecting sensitive regulated-entity information and avoiding unsupported conclusions.A&nbsp;grants-making agency may want to improve application processing, but must protect applicant data, procurement-sensitive information, and pre-decisional materials.A&nbsp;citizen services agency may want to deploy a public-facing AI assistant, but needs to ensure the assistant provides accurate information, avoids unauthorized determinations, and escalates to a human when appropriate.A&nbsp;software development organization may want to use AI coding assistants to accelerate modernization, while preventing source code leakage, secrets exposure, and unapproved model use.A&nbsp;security operations team may want to use AI to improve triage, detection, and response, while maintaining human oversight and protecting sensitive incident data.These are the kinds of use cases where AI security, Zero Trust, and governance need to work in concert. A practical path forwardA good starting point is visibility.Federal Civilian agencies can begin by identifying the AI already in use across public GenAI, embedded AI, desktop tools, developer environments, cloud services, models, agents, and AI-enabled applications.From there, agencies can map AI usage to data sensitivity and mission risk. This means understanding where AI interactions involve sensitive mission data, including PII, CUI, source code, benefits data, health data, financial data, law enforcement data, regulatory data, or procurement-sensitive information.Once agencies understand the risk, they can enforce acceptable-use and data protection policies. This may include access controls, DLP, browser isolation, prompt inspection, response inspection, and user coaching.For agency-built AI applications, agencies should apply guardrails, proxy or API-based inspection, and red teaming before deployment. After deployment, they should continuously monitor usage, policy violations, data exposure attempts, red team findings, model behavior, and emerging AI assets.Finally, agencies need to report what they learn to governance stakeholders, including the CAIO, AI Governance Board, CIO, CISO, privacy, legal, data, acquisition, and mission leaders.This approach supports the intent of M-25-21: move faster with AI while maintaining governance and public trust. Where this leaves usAI is becoming part of how Federal Civilian agencies deliver their missions.But responsible adoption requires more than enthusiasm and policy statements. Agencies need visibility, data protection, security controls, testing, monitoring, and governance evidence.M-25-21 sets the direction: accelerate AI adoption, remove barriers, establish governance, manage risk, and preserve public trust.Zscaler helps agencies put that direction into practice by extending Zero Trust into AI interactions. This means helping agencies discover AI use across the enterprise, reduce shadow AI risk, protect sensitive government data, enable approved GenAI tools, govern embedded AI in SaaS, secure developer use of AI, identify AI assets in cloud environments, protect agency-built AI applications and agents, red team AI systems before deployment, apply guardrails for prompts and responses, monitor AI usage continuously, and provide evidence to AI governance stakeholders.The goal is AI adoption with the visibility, control, and governance needed to manage risk in real time, at mission speed.To learn more about how Zscaler extends Zero Trust to AI for Federal Civilian agencies, reach out to your Zscaler account team for a detailed overview of our AI Security capabilities.Read the full series: Part 1: M-25-21 Changes the AI Conversation | Part 2: A Practical Framework for Secure AI Adoption]]></description>
            <dc:creator>Jose Arvelo Negron (Manager, Sales Engineer)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Countermeasures for AI-Enabled Attacks Start with Deception]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/countermeasures-ai-enabled-attacks-start-deception</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/countermeasures-ai-enabled-attacks-start-deception</guid>
            <pubDate>Tue, 15 Sep 2026 20:40:52 GMT</pubDate>
            <description><![CDATA[Anthropic’s September 2026 threat intelligence report provides one of the clearest public views to date into how threat actors are using frontier AI systems across real cyber operations. Not surprisingly, the attacks rely on familiar weaknesses – stolen credentials, exposed applications, vulnerable services, insecure code, SaaS abuse, cloud misconfigurations, and poor secret hygiene.So if attack tactics haven’t changed with AI, what has? The speed, scale, and economics of execution.Anthropic is stressing the improvements in adversarial speed and economics – something we raised the alarm on in Nov 2025 when everyone else was focused on AI’s ability to exploit at scale.“Many commentators focus on the risk of AI developing exploits at scale. While this is a danger, the risk from AI adoption is more pronounced across the cyber kill chain, where adversaries can operate faster, across a broader and deeper surface area, with fewer resources.”&nbsp;– Detecting and countering misuse of AI: September 2026, AnthropicAI allows attackers to automate reconnaissance, credential validation, exploit development, phishing infrastructure, post-compromise enumeration, and data processing. Those capabilities compress the time defenders have to detect and respond. Controls that were acceptable when attackers moved at human speed will not be sufficient when attackers operate with agentic workflows, persistent memory, and parallel task execution.But that same automation creates an advantage for defenders.AI-enabled attackers depend on discovery. They enumerate exposed assets. They classify systems. They validate credentials. They test access paths. They search for sensitive data, privileged accounts, internal applications, cloud resources, repositories, and AI infrastructure. In other words, they interact with the environment to decide where to go next.Deception exploits that dependency. That is why deception is especially relevant in the age of agentic attacks and why the Cloud Security Alliance has consistently cited deploying deception as a key priority response to AI attacks. The more automated the attacker becomes, the more opportunities defenders have to misdirect, observe, and contain them before real systems are impacted.At its core, deception is a capability, not a product. This post looks at five of Anthropic’s cyber operation case studies where deception can serve as a primary early-detection and containment mechanism. The goal is to show how defenders can use decoys, honeytokens, synthetic assets, and canaries to turn attacker discovery into detection.&nbsp; GTG-20006 / Midnight Blizzard — Russian EspionageGTG-20006 is a Russian state-linked espionage actor whose attribution is consistent with public reporting on Midnight Blizzard. This entity has been targeting Ukrainian, European, diplomatic, defense, and foreign-policy organizations.How AI was usedAI was used to automate operations, notably in the following areas:Develop and maintain malwareAcquire and configure infrastructureResearch and register phishing domainsSend phishing emailsMonitor C2 channelsManage compromised accountsSupport persistence and exfiltrationProcess stolen dataRebuild malware when security products detected itAI UpliftSpeed: Faster phishing, infrastructure setup, and malware modificationScale: More victims and campaigns handled in parallelDepth: Better post-compromise processing and data organizationResilience: Faster evasion when defenders created detectionsDeception as countermeasure for GTG-20006&nbsp;Attack stepType of Deception for each applicable stepWhy Deception will be effectivePhishing domain and lure testingDecoy login portals (M365/vendor portals available via custom clone)If the actor tests phishing flows against decoy users or decoy portals, defenders get early evidence of campaign preparation.Credential harvestingDecoy browser credentials, decoy VPN credentials, decoy M365 credentials and SSO-recovery credential files (via credential-file decoy)No legitimate workflow should use these credentials. Any attempted use is high-confidence evidence of credential theft.Browser password theftEndpoint-planted decoy credentials in browser storesInfostealers will collect decoy credentials along with real ones. Use of those credentials reveals the compromised endpoint or user.Malware delivery and stagingDecoy endpoints, decoy update servers, decoy software-distribution portalsMalware or scripted access to decoy infrastructure provides behavior-based detection independent of signatures.Lateral movementDecoy admin credentials, decoy RDP/SSH/VPN paths, decoy internal bookmarksAttackers following stolen credentials or bookmarks are redirected into instrumented systems.SaaS and cloud data harvestingDecoy SaaS login portals, decoy cloud buckets, planted SaaS credentialsAttackers using stolen tokens to discover data will touch decoy high-value locations, creating early alerts.Hotel Wi-Fi or vendor compromiseDecoy vendor-management portals, decoy Wi-Fi admin consoles, decoy hospitality systemsAttackers abusing hospitality infrastructure can be detected when they interact with convincing decoy management surfaces.&nbsp; GTG-50014 — ShinyHunters-Style Smash-and-Grab Data TheftGTG-50014 is described as financially motivated activity associated with ShinyHunters-like operators.Anthropic identified an opportunistic data-theft and extortion pattern. The threat actor searched for exposed credentials, API keys, SaaS tokens, GitHub tokens, cloud credentials, container secrets, and mobile app secrets.Targets included technology providers, airlines, energy companies, nonprofits, retail chains, web3 platforms, SaaS providers, GitHub repos, containers, and Internet-facing APIs.How AI was usedAI helped the actor move quickly across many unrelated environments.Instead of manually understanding every mobile app, API, SaaS product, or cloud service, the threat actor could use AI to:Analyze decompiled mobile appsClassify discovered secretsUnderstand APIsGenerate validation workflowsSummarize stolen datasetsWrite scripts for harvesting and exfiltrationOrganize credentials by source typeSupport extortion preparationAI UpliftScale and speed. The attack techniques were not novel. The novelty was that AI made mass opportunistic exploitation easier and faster.Deception as countermeasure for GTG-50014&nbsp;Attack stepType of Deception for each applicable stepWhy Deception will be effectivePublic repo scanningDecoy cloud keys (IAM/ECR/SA) and tokens planted on endpoints and in the customer's cloudSecret scanners will find and validate the decoys. Any use of those tokens is high-confidence malicious activity.API key validationDecoy cloud keys (AWS IAM/ECR, Azure, GCP SA) planted on endpoints&nbsp;Secret validation is a strong attacker behavior. Decoy keys convert validation into immediate detection.Cloud storage discoveryDecoy S3 buckets, Azure Blob containers and GCS pathsAttackers searching for exposed data will browse fake stores, giving defenders visibility into data-theft intent.SaaS compromiseDecoy Salesforce, ServiceNow, or SharePoint credentialsIf stolen SaaS credentials are tested, the decoy login attempt becomes a high-confidence alert.Downstream customer data theftSynthetic customer records, decoy CRM exports, beaconed decoy documents (HTML/Office)&nbsp;Attackers exfiltrating or opening fake customer data reveal themselves without exposing real customers.Data stagingDecoy database decoys (MariaDB/Mongo/Postgres) and beaconed decoy documentsWhen stolen-looking data is opened, moved, or uploaded, defenders get telemetry on attacker infrastructure.Extortion preparationDecoy documents (HTML/Office)Deception helps determine whether stolen data was accessed, staged, or prepared for publication.&nbsp; GTG-10007 — Exploit Foundries and Autonomous Attack FrameworksGTG-10007 is a sustained espionage operation by Chinese-speaking operators likely based in Changsha, Hunan.This case is important because it shows the concept of an AI-enabled exploit foundry.The threat actor used AI-first workflows to conduct intrusion attempts, recon foreign-government networks, reverse engineer security products, analyze firmware and binaries, develop and test exploits, maintain malware, build intelligence-collection infrastructure, and run parallel workstreams with persistent campaign memory.Targets included 50 organizations across retail, education, energy, tech, healthcare, finance, manufacturing, and government agencies.The threat actor compromised an education-technology company and extracted student data, accessed a retail company’s production systems, and retrieved citizen records from a Southeast Asian government agency.&nbsp;A major part of the operation involved autonomous vulnerability research against network appliances and security products. The report says one workflow produced more than a dozen possible zero-day findings in a single month.How AI was usedThe threat actor used AI to:Build a fleet of agent swarmsRun parallel subagentsBuild persistent campaign memoryAutomate firmware analysisCreate decompiler workflowsGenerate vulnerability hypotheses and exploit-code&nbsp;Perform lab testing and iterationSchedule intelligence collectionAI UpliftFaster vulnerability discovery and exploit iterationMultiple workstreams running in parallelAbility to inspect code paths, binaries, and firmware at volumeAbility for campaign memory stored targets, credentials, state, and instructionsThis sort of attack class is where Deception is particularly valuable, because defenders likely do not know the exploit in advance. Deception detects attacker interaction and intent, regardless of whether the CVEs, malware, or signatures are known.Deception as countermeasure for GTG-10007&nbsp;Attack stepType of Deception for each applicable stepWhy Deception will be effectiveInternet-facing reconnaissanceDecoy VPN portals, appliance banners, admin consoles and identity portalsAutonomous recon agents will enumerate and interact with exposed-looking decoys, creating early detection.Appliance targetingDecoy security-appliance interfaces, firmware download portals and management APIsExploit researchers looking for appliance weaknesses may spend effort on instrumented fake assets.Version fingerprintingDecoy banners, vulnerable version strings and headersAI scanners rely on classification. Fake fingerprints can attract scanning and reveal targeting logic.Exploit testingHigh-interaction decoys that safely accept probes and payload attemptsNovel exploit attempts can be captured without needing prior signatures.Post-exploitation enumerationDecoy internal hosts, shares, AD objects and service accountsOnce inside, attackers often enumerate. Decoys turn enumeration into high-confidence detection.Credential reuseDecoy SSH keys, admin passwords, kubeconfigs, and API tokensCredential reuse against decoys reveals compromise before real privileged assets are reached.Lateral movementDecoy jump hosts, RDP systems, and database serversAttackers following internal paths are diverted into monitored infrastructure.Collection infrastructureDecoy document repositories, policy files, and defense-related contentIntelligence collectors may harvest synthetic material, exposing automated collection behavior.Malware testingDecoy endpoints and EDR/security-tool artifactsMalware or exploit tooling interacting with decoy endpoints gives behavior-based signals.Target prioritizationDecoy crown-jewel systems, admin paths and sensitive labelsAI agents prioritize attractive assets. Deception uses that prioritization against the attacker.&nbsp; GTG-50020 — From Hotel Bookings to the AI Supply ChainGTG-50020 is a Russian-speaking, financially motivated threat actor.The threat actor historically targeted hotel booking and fintech platforms, then pivoted toward AI vendors and AI supply-chain targets.The actor attempted to access a pre-release Claude model but did not succeed.Targets included hotel booking platforms, fintech platforms, AI companies, AI vendors, AI evaluation sandboxes, production AI API keys, KYC and identity-verification systems, and exchange and marketplace systems.One key attack involved injecting malicious instructions into an AI vendor’s automated evaluation sandbox. This caused credential disclosure. The actor then abused stolen production AI API keys from multiple providers.The actor also attacked about 30 AI companies in four days.How AI was usedAI was used in two ways:Targeted AI infrastructure directly by attacking AI evaluation workflows and stealing production AI API keys.Used AI-assisted offensive workflows to run reconnaissance and exploitation at scale.The AI tooling used by the threat actor constituted parallel reconnaissance agents, exploitation agents, target-specific scope files, automated finding retesting, containerized pentest tooling, local model gateways, and worker agents operating with limited human supervision.AI UpliftFaster web-app testingMore parallel attacksBetter target-specific exploitationRapid pivoting across many AI companiesAbuse of stolen AI keys for further operationsDeception as countermeasure for GTG-50020&nbsp;Attack stepType of Deception for each applicable stepWhy Deception will be effectiveAI vendor reconnaissanceDecoy AI company assets, model registry entries and documentation portalsAttackers scanning AI companies may interact with fake high-value AI assets first.API key theftDecoy AI-provider / LLM-gateway keys (via cloud gen-ai decoy + credential files and decoy cloud keys)Stolen-key validation creates immediate high-confidence detection.AI evaluation abuseDecoy evaluation jobs, benchmark datasets and pre-release model referencesAttackers seeking sensitive model access can be diverted into monitored workflows.Web-app exploitationDecoy web apps with fake SSRF, XSS, and auth-bypass surfacesAutomated exploitation agents will probe decoys, revealing attack behavior.SSRF testingDecoy metadata endpoints and internal service URLsSSRF attempts against decoys expose exploitation attempts without risking real infrastructure.KYC workflow abuseDecoy KYC admin portals, identity-verification records and synthetic applicant dataAttackers targeting fraud or identity workflows can be detected before real records are abused.Fraud account creationDecoy onboarding flows and synthetic high-risk accountsAutomated account factories can be identified through interaction with controlled flows.AI supply-chain compromiseFake CI/CD secretsAttackers looking for AI pipeline access will validate decoys and reveal compromise paths.Extortion preparationBeaconed decoy documents (HTML/Office)Shows whether attackers reached data-theft or extortion stages while protecting real data.&nbsp; GTG-50029 — Hacktivists Targeting European Political EntitiesGTG-50029 was a politically motivated French-speaking hacktivist operation.They have targeted European political parties, media organizations, think tanks, SaaS providers, campaign-management platforms, political affiliates, readers and editorial staff.The actor used stolen API keys and AI-assisted tooling to scale attacks.Techniques used included public-container API key theft, custom Rust scanner for exposed keys, API key rotation through proxies, WordPress exploitation, admin account creation, webshell deployment, credential-harvesting, backup poisoning, browser C2 against a media site, credential interception, and Tor leak-site staging.The actor gained internal access to at least 14 of 42 tracked entities. The operation exfiltrated political, donor, member, student, mailbox, and payment-provider data.How AI was usedAI was primarily used to build and debug offensive tooling. The threat actors used AI to:&nbsp;&nbsp;Develop a WordPress exploitBuild a lab harnessDebug codeManage reconnaissanceReview codeValidate findingsBuild a doxxing/search platformCreate ingestion pipelinesNormalize and rank dataContainerize deploymentAI UpliftFaster exploit developmentFaster weaponization of public-facing web systemsBetter data processing for doxxingAbility for a single actor to run a campaign that looked more like a team effortDeception as countermeasure for GTG-50029&nbsp;Attack stepType of Deception for each applicable stepWhy Deception will be effectivePublic-container scanningDecoy cloud keys/tokens planted on endpoints and in the customer's cloudScanners will harvest decoys. Validation attempts reveal attacker infrastructure.API key rotationHoneytokens tied to monitored API endpointsEven if attackers rotate keys through proxies, decoy-key use remains abnormal and high-confidence.CMS targetingDecoy WordPress/CMS instances, plugin directories and admin panelsHacktivists looking for exposed CMS weaknesses can be pulled into monitored systems.WordPress exploitationDecoy vulnerable CMS versions and instrumented login/reinstall flowsExploit attempts against decoys can be captured before real sites are affected.Rogue admin creationDecoy admin accounts&nbsp;Unauthorized admin creation is a strong signal of compromise.Webshell deploymentDecoy upload directories and writable plugin/theme pathsWebshell upload attempts against decoys reveal active exploitation.Credential-harvesting plugin deploymentDecoy CMS users and admin credentialsThe attacker’s harvesting tooling collects credentials that lead only to monitored assets.Backup poisoningDecoy backup archives and restoration pathsAttempts to alter decoy backups reveal persistence behavior.Doxxing data aggregationSynthetic donor lists, member records and political-affiliation dataProtects real users while revealing data-theft and publication intent.Leak-site stagingBeaconed decoy documents (HTML/Office)If staged or opened, defenders gain telemetry about attacker infrastructure and timing.As is evident from the five threat actors, AI-enabled attackers are automating the discovery of users, credentials, applications, APIs, cloud data, and exposed services. Deception gives defenders a way to pre-position false but believable assets in those discovery paths. When attackers or their AI agents touch those assets, you get early, high-confidence alerts before real systems are damaged.&nbsp; Recommended Deception control categories mapped to threat actorsTo consolidate what type of deception works best in different situations, we’ve mapped them to the threat actors documented in Anthropic’s report.Deception typeExamplesBest-fit attacksIdentity deceptionDecoy users, admin accounts, SSO credentials and OAuth tokensGTG-20006, GTG-50020, GTG-50029Endpoint deceptionDecoy browser passwords, SSH keys and credential filesGTG-20006, GTG-50014, GTG-50021Developer deceptionDecoy GitHub PATs, CI/CD secrets, cloud keys and package tokens on internal endpoints/cloudGTG-50014, GTG-50020, GTG-50029SaaS deceptionDecoy Salesforce / ServiceNow / SharePoint login portals + planted SaaS credentialsGTG-20006, GTG-50014, GTG-50029Cloud deceptionDecoy S3 buckets, database strings, IAM users and cloud consolesGTG-50014, GTG-50020Network deceptionDecoy VPNs, RDP/SSH hosts, databases and file sharesGTG-10007, GTG-20006Web-app deceptionDecoy CMS, admin panels and SSRF/XSS surfacesGTG-50020, GTG-50029AI-stack deceptionDecoy AI API keys, LLM gateways and MCPGTG-50020, GTG-50021, GTG-50014Data deceptionSynthetic customer records, decoy donor lists, beaconed decoy documents (HTML/Office)GTG-20006, GTG-50014, GTG-50029Note: We’ve included GTG-50021 and GTG-30005 in the table above as secondary or specialized deception opportunities, but these attacks are not discussed in this analysis because deception is not the primary front-line control for those scenarios.For the attacks described in Anthropic’s report, deception is not a replacement for patching, identity hardening, ZTNA, DLP, SaaS control, or threat prevention. It is a preemptive detection layer that changes the attacker’s operating environment. By placing decoy credentials, applications, APIs, data, and services in the paths that AI agents are likely to enumerate, you can increase attacker uncertainty, pollute automated decision-making, and generate high-confidence alerts before real systems are damaged.Learn more about Zscaler Deception&nbsp;here.&nbsp;If you’re already a Zscaler customer and would like to deploy Zscaler Deception, please reach out to your account manager.]]></description>
            <dc:creator>Amir Moin (Principal Product Manager)</dc:creator>
        </item>
        <item>
            <title><![CDATA[Enhancing Application and Threat Detection in Zero Trust Firewall]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/enhancing-application-and-threat-detection-zero-trust-firewall</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/enhancing-application-and-threat-detection-zero-trust-firewall</guid>
            <pubDate>Tue, 15 Sep 2026 16:02:25 GMT</pubDate>
            <description><![CDATA[Modern enterprises don’t run on a defined perimeter anymore. Users connect from everywhere, applications live across SaaS and public cloud, and attackers ever increasingly hide in encrypted traffic. In this environment, security teams need more than “IP + port” controls—they need&nbsp;application-aware enforcement&nbsp;and&nbsp;always-on threat inspection&nbsp;that follows users and traffic wherever it goes.Zscaler Zero Trust Firewall&nbsp;is designed for exactly that: cloud-delivered protection for&nbsp;web and non-web traffic, centralized policy, and deep visibility—without the operational drag of appliance sprawl. Two new capabilities that significantly improve this security outcomes are:Custom Application Service Groups (Custom App Services)&nbsp;for precise, reusable application/service controlsCustom IPS Signature Rules (Cloud Custom IPS)&nbsp;for organization-specific threat detections enforced through IPS ControlThis post focuses on what they do, why they matter, and how customers can put them into practice quickly.Why application and threat detection needs a zero trust approachLegacy firewalls were built for a world where:applications stayed in the data center,“Inside the perimeter” was trusted,and deep inspection (especially SSL/TLS) was optional.Today, that model breaks down:SSL/TLS is the default, and turning on TLS inspection at scale can be painful in appliance architectures.Attackers don’t just attack servers—they target&nbsp;users, endpoints, and “normal” protocols.Policy sprawl grows fast when you try to emulate zero trust through endless network segments and distributed rulebases.A&nbsp;Zero Trust Firewall&nbsp;addresses these challenges by enforcing in the cloud and adding richer context for decisions such as identity, application/service constructs, and integrated IPS.What Zero Trust Firewall (ZTFW) deliversCustomer outcomes typically map to three capabilities:Consistent protection everywhere: The same security posture for users at HQ, branches, and remote.Better precision than “network-only” controls: Policies can incorporate user context and (where licensed) process-level awareness via Endpoint App Control.Inline inspection + visibility: Built-in security services (including IPS) and centralized logging/insights so security teams can investigate and respond faster.That foundation is what makes Custom App Services and Custom IPS signatures so impactful: they become building blocks you can reuse and scale across your environment. Custom Application Service Groups: enforce policy on application services, not just IPsApplication Service Groups&nbsp;are policy objects you can use as criteria in&nbsp;Firewall Filtering and Forwarding&nbsp;rules. They’re defined using service metadata such as:IP addresses (single IP, subnet, or range)FQDNs and wildcard FQDNs (e.g.,&nbsp;*.example.com)TCP/UDP destination portsZscaler provides both:Predefined application service groups (AU / “Authoritative”): These are application&nbsp;service groups for popular SaaS and cloud providers based on their metadata; broadly applicable; updated over time.Custom application service groups (CU)&nbsp;: Created by&nbsp;you, in your tenant, for&nbsp;your&nbsp;specific service definitions and policy needs.&nbsp;Predefined Application Service GroupsZscaler maintains and updates a list of predefined application services based on information published by the respective providers. These predefined services help customers:Reduce operational overhead: less manual IP-list maintenance as providers evolve.Write cleaner firewall policy: rules read like business intent (“Allow Microsoft 365”) rather than brittle networking trivia.Improve accuracy: service identification is built to reflect provider-published metadata. Zscaler also continuously updates provider-published metadata for many predefined groups, reducing the effort of tracking SaaS IP changes over time. Custom Application Service Groups: add flexibility when predefined isn’t enoughPredefined services are intentionally generalized and provider-driven. But real customer environments often need something more specific, such as:a privately hosted API with known FQDNs and portsa partner integration endpoint seta SaaS app that isn’t in the predefined cataloga subset of destinations within a larger provider footprintThat’s where&nbsp;Custom Application Service Groups&nbsp;come in.A custom application service group can be built using combinations of:IP addresses&nbsp;(single IP / subnet / range)FQDN / wildcard FQDN&nbsp;(e.g.,&nbsp;api.example.com&nbsp;or&nbsp;*.example.com)TCP/UDP destination portsThis gives you&nbsp;service-aware control for apps that are unique to your business, not just what’s common among all customers.Where custom services deliver the most valueModel your own apps like “first-class services” in firewall policy:&nbsp;Instead of falling back to generic destination IP groups and ports.Limit a large, predefined service footprint to only what you intend:&nbsp;Example: define a custom group representing only a narrow set of AWS-hosted endpoints your engineering org should reach.Create reusable objects:&nbsp;Use the same custom service group across Firewall Filtering, Forwarding rules, and (where applicable) IPS control targeting.Custom Application Service Groups help you:Reduce rule fragility: Instead of chasing shifting IPs and endpoints, define the service once and reuse it.Improve least privilege: Narrow access to&nbsp;exactly&nbsp;the destinations and ports that matter.Simplify operations: Build cleaner policies using reusable objects rather than repeating the same destinations in many rules.A key advantage: first-packet identificationA key benefit of application service groups is they can be used to identify applications&nbsp;on the first packet, which can allow policy action to apply immediately. Operationally, this also influences rule design: application service-based policies often belong higher in a higher priority rule than similar “network application” rules to ensure deterministic matching.Example use cases:Tight SaaS allowlisting: Allow Microsoft 365 or Zoom-related service traffic only for intended users and conditions.Controlled cloud access: Allow AWS/GCP service traffic, but only for specific departments (and ideally with multiple conditions).Partner/API segmentation: Create a custom service group for partner API hosts and required ports, then enforce strict allow + logging. IPS Control&nbsp; with Cloud Custom IPS: always-on threat prevention, inlineEven the “right” application traffic can carry threats. That’s why Zero Trust Firewall pairs application control with inline intrusion prevention.IPS Control&nbsp;in ZIA provides signature-based detection across&nbsp;web and non-web traffic&nbsp;(including HTTP/HTTPS/FTP/DNS/TCP/UDP and IP-based traffic) and supports granular policy conditions such as users/groups/departments/locations and more. It also supports actions such as:AllowBlock/DropBlock/ResetBypass IPSDefault threat signatures vs. Custom IPS signatures (what’s included vs. what you add)IPS Control policies can be configured to enforce signatures from two sources:Signatures available with IPS Control by default:&nbsp;Zscaler’s IPS Control uses IPS signature rules&nbsp;built and updated by Zscaler’s security research team (ThreatLabz), as well as&nbsp;signatures from industry-leading vendors. These signatures provide broad baseline coverage and are maintained by Zscaler.Custom IPS Signature Rules (customer-defined):&nbsp;In addition to the default signatures, you can&nbsp;create and deploy custom IPS signatures&nbsp;that are specific to your organization’s requirements&nbsp;without requiring any additional infrastructure, and inspect your traffic using these signatures. These custom signatures are authored by your team and remain specific to your tenant.In either scenario, with Zscaler Cloud IPS Control, you no longer have to hairpin the traffic back to the DC via VPNs. Instead, the traffic can go directly to the cloud, no matter where the user, device, or workload is globally. Custom IPS Signature Rules: tailor threat detection to your environmentCustom IPS Signature Rules&nbsp;let your security team define organization-specific detections using&nbsp;Snort-like syntax, deploy them in the Zscaler cloud (no additional infrastructure), and enforce them through&nbsp;IPS Control&nbsp;via an assigned&nbsp;Threat Category. Additionally, the signature only stays in your tenant, enabling you to comply with TLP:amber/red guidelines.This is especially valuable when:You have a&nbsp;unique internal application&nbsp;or API surfaceYou receive new threat intel and want to&nbsp;respond independent of Zscaler's ThreatLabz.You need&nbsp;custom detections for compliance&nbsp;or for telemetry/signals into your SOC via Zscaler logging. Quick example: why you’d use a custom signature even when defaults existScenario:&nbsp;Your SecOps team receives threat intel about a pattern targeting&nbsp;your&nbsp;environment. That pattern may not exist in the default global signature set (yet), and you can’t wait for a broader industry signature release cycle.What you do:Keep&nbsp;default IPS signatures&nbsp;enabled (so you retain broad protection immediately).Create a&nbsp;Custom IPS signature&nbsp;that matches the environment-specific pattern.Assign it to a threat category and enforce it via an&nbsp;IPS Control&nbsp;rule scoped to the relevant users/locations/services (for example, the Application Service Group representing that app/service).Choose the IPS Control action (e.g., block/drop for high-confidence attempts) and activate the policy.Outcome:&nbsp;You get the best of both:continuously updated default coverage&nbsp;from Zscaler, andfast, precise, tenant-specific detection&nbsp;when your environment needs something unique—without deploying additional IPS infrastructure.In practice: write signatures that are&nbsp;specific,&nbsp;testable, and&nbsp;scoped&nbsp;(then monitor hits and adjust). ConclusionA Zero Trust Firewall isn’t just “a firewall in the cloud.” The real advantage comes from&nbsp;higher-fidelity policy objects&nbsp;and&nbsp;embedded threat prevention&nbsp;that move at the speed of modern environments.Custom Application Service Groups&nbsp;reduce policy fragility and increase enforcement precision by modeling services the way the business uses them.Custom IPS Signature Rules&nbsp;close detection gaps by letting you encode organization-specific threat intelligence and enforce it through IPS Control—without deploying separate IPS infrastructure.Together, they turn firewall policy from a static ruleset into a living control plane for application-aware access and threat detection in a zero trust architecture.&nbsp;Join an upcoming hands-on Zero Trust Firewall workshop where Zscaler experts walk you through building real policies for non-web traffic including IPS rules, DNS controls, and application-aware enforcement in a live, interactive environment.Reserve your spotSeats are limited and sessions fill quickly so register early.]]></description>
            <dc:creator>Siddhartha Aggarwal (Staff Technical Product Specialist - Firewall)</dc:creator>
        </item>
        <item>
            <title><![CDATA[The Latest in Risk360: Agentic AI and Integration Support]]></title>
            <link>https://www.zscaler.com/tw/blogs/product-insights/latest-risk360-agentic-ai-and-integration-support</link>
            <guid>https://www.zscaler.com/tw/blogs/product-insights/latest-risk360-agentic-ai-and-integration-support</guid>
            <pubDate>Tue, 15 Sep 2026 12:15:07 GMT</pubDate>
            <description><![CDATA[Security and risk teams are under pressure to do more than just identify issues—they need to understand what matters most, explain business impact clearly, and act more quickly across a growing set of tools and stakeholders. That’s the challenge&nbsp;Risk360 is built to solve. By helping organizations quantify cyber risk, prioritize remediation, and communicate posture in business-relevant terms, Risk360 gives customers a clearer view of where they stand and what they should do next.As part of this mission, Zscaler now has two new ways to help customers get even more value from Risk360: a Risk360 agent and support for Risk360 in&nbsp;OneAPI.The Risk360 AgentAs security environments become more complex, admins need more than dashboards and static workflows. They need a faster, more intuitive way to investigate issues, understand what is driving risk, make the best choices possible, and take the next right action. That’s where agentic AI can make a real difference. It can reduce the time it takes to navigate tools, interpret data, and translate technical findings into decisions that the business can act on.&nbsp;Zscaler’s new Risk360 agent brings the above benefits to risk analysis for each customer’s Zscaler environment. It helps admins quickly understand their overall risk posture, identify the most important issues that need to be addressed, and assess the financial exposure tied to those risks. Through natural-language interactions, customers can drill into specific categories and risk factors, investigate what is driving change, and uncover root causes. The result is faster analysis, more confident prioritization, and clearer communication with executives, compliance teams, and other stakeholders.The Risk360 agent is part of Zero Trust Exchange Agentic Operations, which enables agentic AI to manage Zscaler—whether that’s the Zscaler platform’s built-in agent (ZAgent) or, in the near-term future, third-party AI agents. Either way, the service allows agentic AI to leverage specialized product agents so that customers can interact with Zscaler services in a more cohesive, streamlined, and intelligent fashion. In other words, Risk360 can now be managed alongside other Zscaler solutions in a single conversational chat with an AI agent.Risk360 OneAPI SupportCustomers need the data from their security solutions to work beyond the boundaries of each individual tool. As such, application programming interfaces (APIs) are essential. They enable practitioners to integrate insights from their solutions into other tools for broader operational, reporting, and partner workflows—without relying on manual exports or disconnected processes.With Risk360 support now available for OneAPI, customers can leverage the same unified API endpoint that is used across the rest of the Zscaler platform for Risk360. Conceptually, this makes it easier to bring Risk360 into the systems and processes you already have in place. Practically, it supports workflows such as pulling historical risk scores and peer comparisons into internal dashboards, retrieving risk factor and financial exposure data for analysis, and automating report generation and access for downstream use. It creates a cleaner path for integration with GRC tools, SIEM workflows, service providers, and cyber insurance ecosystems that depend on timely risk data.By extending Risk360 through OneAPI, we’re helping customers turn risk insights into action far more efficiently—whether that means building custom workflows, feeding external systems, or scaling automation across teams.Wrap-UpTo learn more about our in-product AI experience and how it connects users to specialized product agents, read our&nbsp;ZAgent blog. To explore how OneAPI helps customers automate and integrate across the Zero Trust Exchange, visit our&nbsp;OneAPI webpage.]]></description>
            <dc:creator>Jacob Serpa (Sr. Product Marketing Manager)</dc:creator>
        </item>
    </channel>
</rss>