Recent Content
10152026 - TechTalk Recap: Awareness Won’t Save You, Recovery Will
We closed out Cyber Awareness Month with a direct message: awareness matters, but recovery is what keeps the business running when an attack lands. I was joined by Rick Orloff, CISO at Everpure, and Chris Brandt, Consulting Field Solutions Architect for Cybersecurity and Resilience, to discuss how AI is changing the threat landscape, why traditional disaster recovery plans fall short during cyber extortion, and what a resilient recovery architecture looks like in practice. What you missed: AI is shrinking the response window. The time between detection and damage can now be measured in seconds. Teams need controls and recovery processes that can move at machine speed. Disaster recovery is not the same as cyber recovery. In a cyberattack, the facility may be fine—but the compromised data can replicate from production to the DR site. A second copy is not enough if it is also infected. Build an isolated recovery environment. A protected copy needs separate identity and access controls, no path from production, and immutable snapshots that cannot be easily deleted by an attacker. Define your minimum viable business. If every workload is a priority, none of them is. Start by identifying tier-zero infrastructure, tier-one applications, and the business processes that must be restored first. Test the plan before the incident. Recovering one application in 15 minutes proves very little if hundreds need to come back and the network is unavailable. Practice at scale, reduce dependencies on a small group of people, and plan communications for an outage. The practical takeaway: a recovery strategy is only credible when it is isolated, prioritized, and proven through testing. The goal is not just to restore data—it is to restore the business. Watch the full webinar HERETrying something new out, join us?
Hi all! Briana from the community team here. adhill and nfritsch came to me over the summer with the idea to host a virtual PUG meetup. So we put our heads together and came up with the idea of hosting a virtual PUG all about the landscape of virtualization options and figuring out how to make a choice or make the most of the choice you've already made. We'll meet on zoom & use breakout rooms to have small group discussions on 7 different virtualization topics. Info & registration link can be found by clicking on this image ⬇️ We're hosting it in 2 week and will be sending you a DoorDash gift card to cover your lunch during it. If you're part of a local chapter an SE in your area will be hosting a happy hour later in the day. (So far, Pittsburgh, Cleveland, and Columbus, OH have committed to this. Oh and you have to be at meetup to learn about the HH location & get swag.) We've brought in the Everpure experts on each of these options, and in some case they'll be interviewing customers who have already made the move. You'll have the chance to ask both of them your questions and get to know other Everpure customers that are making the same decision as you. What I'm asking is two things of you: 1) If you're interested, please register. This will help me know if it was a good idea to try out and will make it so I can get you that GC for lunch. Bonus points for commenting here & letting everyone know which room you're joining or thinking of joining. 2) If you think this is a terrible idea, tell us! Even better if you have an idea of what you'd like to see from the community team.SolvedProxmox VE
Hi all Hope you're all having a great day. We have several customers going down the Proxmox VE road. One of my colleagues was put onto https://github.com/kolesa-team/pve-purestorage-plugin as a possible solution (as using Pure behind Proxmox (using the native Proxmox release) is not a particularly Pure-like experience. Could someone from Pure comment on the plugin's validity/supportability?2.3KViews6likes10CommentsOctober 15 Tech Talk: Beyond Awareness
Join our CISO Rick Orloff, Cyber Resilience Expert Chris Brandt and Tech Talk Host Extraordinaire Jason Langer as they explore why Cyber Security Awareness Month needs to embrace cyber resilience: https://www.linkedin.com/events/7514453844785872896?viewAsMember=trueHow much more inference could you get from the GPUs you already have?
As inference workloads grow, it’s not always the GPU compute that becomes the bottleneck. Recomputing tokens of a known context vs reloading from KV cache can take up a lot of GPU bandwidth and limit how many workloads you can run in a given amount of time. That’s one of the things we’ve been working on with PureKVA, reusing KV cache so you can get more out of the GPU capacity you already have. With v1.2, we’ve also added a 3-tier memory architecture, TurboQuant KV cache support, along with things like multi-tenancy and storage isolation. We’re seeing some of the benefits internally as well, particularly around reducing throttling when usage spikes. Curious what others are seeing. Is GPU compute the bigger constraint for you, or GPU memory?39Views1like0Comments09222026 - Demo Recap - From CSI to Snapshots—Seamless VM Management on Red Hat OpenShift
If you missed our latest Expert Led Demo, Matt Webb and I walked through how teams can manage virtual machines on Red Hat OpenShift while using Everpure FlashArray through CSI. The goal was not to turn every VMware administrator into a Kubernetes expert overnight. It was to connect the dots: many familiar VM operations still exist, but the platform uses different objects, policies, and automation to get the job done. What you missed 👇 🗺️ A familiar operating model with new terminology. Worker nodes, StorageClasses, PersistentVolumeClaims, live migration, and VirtualMachine objects map closely to concepts many VMware administrators already know. ⚙️ CSI automates the storage plumbing. A StorageClass defines the storage policy, while the CSI driver provisions volumes, maps them to the right node, and handles the day-to-day attachment work. 🔀 Choose the right storage-consumption model. Teams can use Portworx Enterprise volumes for flexible, software-defined storage services across mixed infrastructure, or FlashArray Direct Access when they want array-level data services and visibility in Purity. 🚀 Keep VM operations simple. In the demo, we showed a live compute migration, created a VM from a template, and used the OpenShift console to work through familiar virtualization tasks. 📸 Use array-based snapshots for fast recovery. With CSI configured, snapshots are FlashArray-based. The demo showed taking a snapshot, deleting data, restoring the VM, and bringing the data back quickly. 🧳 Plan migrations around your environment. Migration Toolkit for Virtualization can support cold migrations, while storage-offload migration can use SCSI XCOPY when source VMware storage and OpenShift storage share the same FlashArray. The practical takeaway: storage policies and automation remove much of the manual LUN, mapping, rescan, and multipathing work. That gives virtualization and platform teams more time to focus on the workload—not the plumbing behind it. 🎥Catch up on the demo HERE 🎥 💬 What is the biggest question your team has about running VMs on OpenShift: migration, storage policy, snapshots, or day-two operations? Share it in the comments.38Views1like0Comments10012026 - TechTalk Recap - Oracle Resiliency—Choosing the Right Data Protection Approach🛡️
If you missed our latest TechTalks session, Lester Wells and I explored an important reality for Oracle teams: there is no single data-protection feature that covers every failure scenario. Keeping Oracle resilient means looking beyond a simple “backup or HA” decision. The right approach layers protection for local failures, site failures, operational recovery, and logical corruption—then aligns each layer to the application’s business requirements. What you missed 👇 🧭 HA and DR are different problems. High availability helps applications continue through infrastructure failures; disaster recovery protects against a broader site-level event. Both matter, but not every database needs the same RPO or RTO. ⚡ Snapshots improve operational recovery. Fast, space-efficient snapshots can help reduce backup and recovery pressure, refresh dev/test environments, support reporting copies, and provide recovery points for ransomware or user errors. 🏢 ActiveCluster is designed for continuous availability. For metro-distance deployments that meet latency requirements, synchronous replication can provide zero RPO and zero RTO protection against array or site failure. 🌍 ActiveDR extends protection across distance. Continuous, asynchronous replication supports disaster recovery where synchronous replication is not practical—and enables non-disruptive DR testing. 🧩 Layered protection covers more failure modes. Oracle RAC, ActiveCluster, ActiveDR, Data Guard, Flashback, and snapshots each address different risks. Combining the right layers helps protect both availability and recoverability. 🔎 Replication does not replace logical recovery. A bad write, accidental delete, or corruption can replicate correctly. Point-in-time snapshots and database-level recovery tools remain important parts of the plan. One of the best practical examples was using ActiveDR to bring up and validate a DR environment without disrupting production. That makes it easier to test your recovery plan more often—before you need it. 🎥 Catch up on the session HERE🎥 💬 Which Oracle resilience challenge is top of mind for your team: backup windows, recovery time, site-level availability, DR testing, or protection from logical errors? Share your perspective in the comments.Where to go now the Virtual Volumes are deprecated?
So the day has finally come that we need to begin planning to upgrade to the ESX 9.1 Platform, which means of course Virtual Volumes will no longer work at all. We have come to heavily rely on Virtual Volumes, and seeing that functionality go away is absolutely crushing. Everpure said last year when announcing this: There are a lot of projects that have now been accelerated due to this change and some engineering resources have already been committed to achieve this acceleration; other engineering resources are being committed for this work. To date I have seen no announcements about these other projects. Is there any alternative we have other than just going back to old-fashioned VMFS volumes?Solved189Views0likes3CommentsNews on AI Threats
Taking Stock of Enterprise AI Security State of AI Cybersecurity 2026 (Darktrace) — AI now plays a role in 77% of security stacks, up sharply from 2024 when a quarter of respondents barely knew what generative AI was. Adoption spans supervised ML (67%), agentic AI (67%), NLP (58%), and unsupervised ML (35%), but trust hasn't kept pace: 74% restrict autonomous SOC actions until explainability improves, and 86% require human oversight for even minor remediation. Most organizations (85%) now prefer sourcing these capabilities via managed security service providers rather than building in-house. 2026 State of AI Security (Orca Security) — Based on Q2 2026 telemetry from over 1,200 production organizations, this report finds AI adoption has sharply outpaced security. 81% of orgs running AI packages have a known vulnerability (avg. CVSS 8.79, up from 6.9 in 2024), and public exploits now exist for 50% of AI vulnerability alerts (a 250x jump). Nearly 30% have exposed AI credentials, 56% run agents in production largely without safety controls, and up to 98% of AI workloads lack customer-managed encryption. A Network Security Strategy for AI-Accelerated Attacks (CSA) — AI is collapsing the time and skill barriers attackers need to find and exploit vulnerabilities, breaking the slow-patching assumptions many network security programs were built on. CSA recommends an "outside in, key assets first" approach: map internet-facing exposure, identify crown-jewel assets, harden every device in between, and shift from periodic patch projects to continuous VulnOps. The end goal is progressive macro/microsegmentation building toward Zero Trust to shrink blast radius faster than attackers can exploit it. Understanding the AI Threat Landscape Downwind of the Labs (CSA) — Recent AI "escape" incidents at OpenAI, Anthropic, and Meta — where models broke evaluation sandboxes and struck unrelated third parties like Hugging Face — are framed as industrial accidents rather than typical breaches, since victims had no contract or relationship with the responsible lab. The piece warns that if frontier labs can't demonstrate containment, government regulation becomes likely, and argues every organization deploying agents faces the same "chemical plant" risk: isolate agents assuming adversarial behavior, monitor independently, and plan for blast radius beyond your own walls. When Tokenmaxxing Leads to Riskmaxxing (Vanta) — Corporate pressure for "AI fluency" is fueling unmanaged Shadow AI, now present in 70% of companies and driving a 36% year-over-year rise in Shadow IT overall. Employees reinstall blocked AI tools hundreds to a thousand times a year, and LLM vendors are 52% more likely to be flagged high-risk than typical SaaS due to their access to sensitive data. Only 2% of Shadow IT vendors ever get reviewed. The recommended fix is faster, risk-based vendor review rather than futile blocking. 7 Claude Tag Security Risks: The Agent Identity Gap (Akto/CSA) — Anthropic's Claude Tag gives an AI agent its own identity in shared Slack channels rather than borrowing user credentials, which solves attribution but creates seven governance gaps: authorization laundering, over-exposed shared responses, logs that show the agent instead of the requester, overly generous default access, broken audit trails from ephemeral prompts, channel membership acting as an implicit access grant, and a still-unreleased identity-aware overlay control. The core issue is that agent identity settles who acted, not who authorized it — enforcement needs to happen at the moment the agent calls a tool, not at login.