Field Notes — Week of June 17, 2026
A short, opinionated digest of what actually mattered this week across cloud, security, AI, and automation — and what it means if you run real systems.
Security: a VPN zero-day that skipped straight to ransomware
The week’s drop-everything item is CVE-2026-50751, a critical authentication-bypass zero-day in Check Point Remote Access VPN, Mobile Access, and Spark Firewall products. It was being exploited in the wild before the hotfix shipped, and at least one intrusion has already been tied to a Qilin ransomware affiliate — so this isn’t a theoretical proof-of-concept, it’s an active initial-access route. The flaw lives in the deprecated IKEv1 VPN path, which many shops left enabled simply because nobody turned it off.
It didn’t land alone. CVE-2026-45657, a wormable Windows Kernel RCE (CVSS 9.8) allowing unauthenticated SYSTEM-level code execution, and a Check Point–era Exchange spoofing bug (CVE-2026-42897, CVSS 8.1) being exploited in real-world attacks, both made the same week’s rounds.
The take: Edge appliances are the soft underbelly right now — VPNs and firewalls sit at the perimeter, run vendor code you don’t audit, and are exactly what ransomware crews scan for first. Two practical moves: kill deprecated protocol paths like IKEv1 by default instead of leaving them on “just in case,” and treat your security gateways as first-class patch targets with the same urgency as a domain controller. The gap between “hotfix released” and “ransomware affiliate exploiting it” is now measured in days, not months.
Cloud: the providers are finally coming for egress fees
The interesting cloud story this week wasn’t a new instance type — it was the quiet erosion of the egress tax. Google’s cross-cloud caching, detailed in the Next ‘26 wrap-up, stores AWS and Azure data on first read so follow-on queries hit a local cache instead of re-paying egress every time. Pair that with the maturing AWS Interconnect – Multicloud and Google Cross-Cloud Interconnect standard (Azure expected to join later this year), and the plumbing for genuinely multicloud data access is arriving.
The take: Egress pricing has been the invisible fence keeping workloads pinned to whichever cloud holds the data. Caching and standardized interconnect don’t demolish that fence, but they lower it enough to change architecture decisions. The leverage here is real at renewal time — but only if your data layer is designed to span clouds in the first place. If everything assumes single-provider data gravity, you can’t cash in the optionality these features create. Build for portability now; retrofitting it under a renewal deadline is the expensive path.
AI: governance is becoming the actual product
KPMG and Microsoft expanded their global partnership this week, with KPMG deploying Microsoft Agent 365 to manage, monitor, and secure client AI agents under its Trusted AI framework. The framing is telling: the pitch isn’t “deploy agents,” it’s “deploy agents you can govern, audit, and control.” NVIDIA and ServiceNow extended their own collaboration at Knowledge 2026 in the same direction — governed autonomous agents from the employee desktop outward.
Meanwhile the production gap remains stark: industry figures still put deployed-to-production agents in the low-to-mid teens by organization, even as 60%+ plan to ship within two years.
The take: When the Big Four and the hyperscalers all lead with governance instead of capability, that’s the market telling you where the bottleneck actually is. Agents don’t fail in the demo; they fail on identity for non-human actors, auditability, and a clean pilot-to-prod path. The teams shipping aren’t the ones with the cleverest prompts — they’re the ones who solved access control and observability for agents before scaling them. Buy or build for the guardrails, not the magic.
Automation: OpenTofu drops the DynamoDB lock table
OpenTofu v1.12.2 landed June 12. The 1.12 series is a quietly significant operational release: native S3 state locking without DynamoDB, OCI registry support for modules and providers, and experimental OpenTelemetry tracing for runs. CI/CD support is now table stakes — GitHub Actions, GitLab CI, CircleCI, and Jenkins all run tofu cleanly, and migrating a pipeline is largely swapping the setup action and the terraform→tofu binary reference.
The take: Native S3 locking is the unglamorous win here. The DynamoDB lock table was always extra IAM surface, extra cost, and extra Terraform state to manage just to prevent concurrent applies — dropping it simplifies every backend you stand up. If you’re greenfield, OpenTofu’s trajectory keeps getting easier to justify; if you’re on Terraform, this is one more data point for making the stay-or-switch call deliberately rather than by inertia. Owned, encrypted, traceable infrastructure is the whole point — pick the tool that gets you there with the least ceremony.
ZelMor LLC helps organizations and consultancies with cloud architecture, AI enablement, security & IAM, and automation. If any of the above is a live question for your team, start a conversation.