--- title: How One Infected Workstation Can Expose Your Cloud and AI description: Wiz research shows how stolen endpoint credentials expose cloud and AI systems. Learn how to limit access, prevent theft and respond. image: https://prevent-ransomware.com/hubfs/10-3-26.png --- [![CHIPS Cyber Defense Solutions, LLC](https://prevent-ransomware.com/hubfs/chips_blue_logo_higher_res-20210817212617.png) Cyber Defense Solutions, LLC](https://prevent-ransomware.com) ☰ [About](https://prevent-ransomware.com/about) [Solutions](https://prevent-ransomware.com/solutions) [Industries](https://prevent-ransomware.com/industries) [Resources](https://prevent-ransomware.com/resources) [Partner With Us](https://prevent-ransomware.com/meetings/tony-chiappetta/30-minute-initial-meeting) [About](https://prevent-ransomware.com/about) [Solutions](https://prevent-ransomware.com/solutions) [Industries](https://prevent-ransomware.com/industries) [Resources](https://prevent-ransomware.com/resources) [Partner With Us](https://prevent-ransomware.com/meetings/tony-chiappetta/30-minute-initial-meeting) # How One Infected Workstation Can Expose Your Cloud and AI ![Tony Chiappetta](https://prevent-ransomware.com/hubfs/Tony%20LinkedIn.jpg) by [Tony Chiappetta](https://prevent-ransomware.com/blog/author/tony-chiappetta) October 04, 2026 Could one employee’s infected computer expose systems your business keeps in the cloud? A [September 25, 2026 report from Wiz Research](https://www.wiz.io/blog/infostealer-incursion-cloud-ai-credentials) shows how infostealers target credentials for cloud services, development platforms and AI tools. The business concern extends beyond cleaning up a laptop: stolen access can create exposure elsewhere, even after the original infection is removed. **Key Takeaway:** A workstation can hold access to systems far beyond itself. Businesses need to prevent credential theft at the endpoint, limit what those credentials can unlock, and prepare to revoke exposed access across connected services. ## So what exactly did Wiz find? Wiz analyzed infostealer data through its NordStellar integration to examine the secrets attackers collect. Its findings describe an analyzed dataset, not the prevalence of every infostealer or every cloud breach. AWS credentials accounted for **46% of compromised secrets** in that analysis. AI platforms represented **5%**, predominantly OpenAI API keys. The report builds on the issue we explored in [Infostealers Aren’t Just Stealing Passwords Anymore](https://prevent-ransomware.com/blog/infostealers-aren-t-just-stealing-passwords-anymore): attackers want usable access, including keys and authenticated sessions, rather than passwords alone. Wiz also describes targeting of cloud, code and AI environments. Our CHIPS analysis is that endpoint security and cloud security should be reviewed together. Protecting the destination does not eliminate risk at the device holding its credentials. ## What can one stolen credential actually unlock? It can unlock whatever the associated identity is permitted to access. The practical impact depends on permissions, credential validity and the service’s additional controls. Consider a hypothetical employee who maintains a customer portal. Their workstation contains a cloud credential for deployment and access to a source-code repository. If that access is stolen and usable, the business may face investigation of application changes, exposed data or interrupted deployments. A different employee’s AI key might primarily create unauthorized usage charges and disrupt legitimate work. For an MSP, the same review should include credentials for customer administration. One technician’s access may span multiple organizations, making separate accounts and narrowly scoped permissions especially valuable. These are possible consequences, not evidence that every stolen credential produces a breach. The leadership question is concrete: **Which business systems could this workstation’s access reach?** ## Does MFA prevent attackers from using stolen access? MFA remains essential, but some stolen session artifacts can be reused without a fresh MFA challenge. API credentials also need protections appropriate to how applications authenticate. A session token is like a pass issued after successful authentication. If a service accepts a copied pass from another device, the attacker may exploit access the legitimate user already established. That is why token theft needs its own controls. [Microsoft’s Token Protection guidance](https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-token-protection) describes binding supported sign-in session tokens to devices to reduce replay attacks. Coverage depends on the application, resource and device configuration, so leaders should have their IT team verify support before rollout. Similarly, [Google Cloud recommends avoiding user-managed service account keys](https://docs.cloud.google.com/iam/docs/best-practices-for-managing-service-account-keys) where alternatives are available. Reducing portable, long-lived secrets reduces opportunities for theft and later misuse. ## Could EDR detect the infection before credentials are stolen? EDR can detect and interrupt infostealer activity, but businesses should not assume every theft attempt will be stopped before data leaves the device. Detection, investigation and response remain important across both endpoints and cloud services. An alert can initiate containment and help establish which identities were exposed. Cloud logs can then help investigators assess whether stolen access was used elsewhere. The limitation is timing. Removing malware does not retrieve a copied credential or automatically invalidate it at every service. A useful incident exercise therefore asks two questions: “Can we isolate this device?” and “Can we identify and revoke the access it contained?” ## What if you did not have to detect the attack in order to stop it? Some attack paths can be interrupted by restricting required endpoint actions before identifying the code as malicious. Isolation and Containment add guardrails around what applications can launch, access or change. In business terms, an application should have enough freedom to perform its job while being constrained from reaching protected memory, files and system resources outside that job. **Changing the attack does not necessarily change the endpoint actions the attacker ultimately needs in order to succeed.** Unknown, polymorphic or AI-generated code may still need to launch a process, abuse a trusted application or access sensitive memory. AppGuard is a proven endpoint protection solution with more than a decade of production history focused on prevention through Isolation and Containment. Its approach restricts out-of-bounds actions without requiring the attack to first be identified as malicious. That can reduce usable Windows endpoint attack surface and complement EDR. Protection depends on the covered behavior and configuration; it does not establish that every credential file or attack path is protected. Once access has been stolen, cloud-side revocation and investigation are still necessary. ## What Should Businesses Do Next? Review endpoint prevention and cloud access as one connected risk. Start with the devices and identities that can affect the most important business systems. - **Map stored access.** Inventory cloud keys, AI credentials, browser sessions and administrative tools on developer and technician devices. - **Reduce credential reach.** Separate routine and privileged accounts, narrow permissions, and use short-lived credentials or managed identities where supported. - **Protect the collection point.** Maintain EDR and patching, reduce unnecessary execution freedom, and evaluate Isolation and Containment for Windows systems. - **Test revocation.** Practice disabling exposed keys and sessions, reviewing connected services, and restoring access from a trusted device. - **Watch downstream activity.** Review cloud audit events, repository changes and unexpected AI usage. Check that alerts reach someone who can act. The objective is not to predict every attack. It is to restrict the actions an attacker needs and limit what stolen access can accomplish. For the related discussion on AI sessions and credential theft, [listen to the September 23 episode of the CHIPS Cybersecurity Podcast](https://open.spotify.com/episode/6djVhUK8QxB8vKouuehk2h). Then ask your IT team: if one workstation were compromised tomorrow, how far could its access carry an attacker? ###### Tags: [AppGuard,](https://prevent-ransomware.com/blog/tag/appguard) [0-day,](https://prevent-ransomware.com/blog/tag/0-day) [Ransomware,](https://prevent-ransomware.com/blog/tag/ransomware) [AI](https://prevent-ransomware.com/blog/tag/ai) ![Tony Chiappetta](https://prevent-ransomware.com/hubfs/Tony%20LinkedIn.jpg) Post by [Tony Chiappetta](https://prevent-ransomware.com/blog/author/tony-chiappetta) October 4, 2026 [![CHIPS Cyber Defense Solutions, LLC](https://prevent-ransomware.com/hubfs/chips_blue_logo_higher_res-20210817212617.png)](https://prevent-ransomware.com) AppGuard Commercial Distributor for the Americas. Mt. Juliet, Tennessee. [Follow us on LinkedIn](https://www.linkedin.com/company/chips-cyber-defense-solutions-llc) #### The Stack - [AppGuard](https://prevent-ransomware.com/AppGuard) - [Zimperium](https://prevent-ransomware.com/Zimperium) - [CyberCloak](https://prevent-ransomware.com/CyberCloak) #### Company - [About Us](https://prevent-ransomware.com/about) - [The MSP 3.0 Story](https://prevent-ransomware.com/MSP3) - [Become a Partner](https://prevent-ransomware.com/meetings/tony-chiappetta/30-minute-initial-meeting) © 2026 CHIPS Cyber Defense Solutions, LLC. All rights reserved. Built for the Best. ```json { "@context" : "http://schema.org/", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Tony Chiappetta", "url" : "https://prevent-ransomware.com/blog/author/tony-chiappetta" }, "dateModified" : "2026-10-04T9:00:00 AM", "datePublished" : "2026-10-04 09:00:00", "description" : "Wiz research shows how stolen endpoint credentials expose cloud and AI systems. Learn how to limit access, prevent theft and respond.", "headline" : "How One Infected Workstation Can Expose Your Cloud and AI", "image" : { "@type" : "ImageObject", "url" : "https://20916912.fs1.hubspotusercontent-na1.net/hubfs/20916912/10-3-26.png" }, "mainEntityOfPage" : { "@id" : "https://prevent-ransomware.com/blog/how-one-infected-workstation-can-expose-your-cloud-and-ai", "@type" : "WebPage" }, "name" : "How One Infected Workstation Can Expose Your Cloud and AI", "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://prevent-ransomware.com/hubfs/chips_blue_logo_higher_res-20210817212617.png" }, "name" : "CHIPS Cyber Defense Solutions, LLC" } } ``` ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Tony Chiappetta", "url" : "https://prevent-ransomware.com/blog/author/tony-chiappetta" }, "dateModified" : "2026-10-04T09:00:00.302Z", "datePublished" : "2026-10-04T09:00:00.000Z", "headline" : "How One Infected Workstation Can Expose Your Cloud and AI", "image" : [ "https://prevent-ransomware.com/hubfs/10-3-26.png" ], "mainEntityOfPage" : { "@id" : "https://prevent-ransomware.com/blog/how-one-infected-workstation-can-expose-your-cloud-and-ai", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://prevent-ransomware.com/hubfs/CHIPS%20&%3B%20AppGuard%20logos.png" }, "name" : "CHIPS Cyber Defense Solutions, LLC" } } ```