Operations | Monitoring | ITSM | DevOps | Cloud

At.conf25, we announced our vision for Cisco Data Fabric, an architecture designed to help organizations unlock the value of machine data, fuel AI with trusted context, and support more intelligent and resilient operations. Today, that vision has become reality. Key Splunk Platform innovations including Machine Data Lake, Catalog, and Agent Launchpad, together with expanded Federated Search and Data Management capabilities, are now generally available.

If you have watched the incident channels light up over the past few weeks, you already sense the theme of 2026: cloud outages are no longer rare, dramatic once a year events. They are a steady drumbeat, and most of them trace back to the same root cause. Not a data center fire, not a rogue backhoe severing a fiber line, but a routine configuration change that went out, behaved differently than expected, and cascaded.

The biggest outages of 2026 are not being caused by a single server dying or one bad deploy. They are being caused by cascading failures, where healthy systems interact in ways nobody planned for and take each other down. That shift changes what good on-call looks like. If your incident response still assumes that "something broke" and one team owns the fix, you are going to be slow exactly when speed matters most.

A Session Border Controller (SBC) is the gatekeeper for modern real-time communications. It's not just a network device. It is a core component of your security, interoperability, and service quality strategy. An SBC secures the boundary between your enterprise network and the outside world, protecting against threats, enabling connectivity between disparate systems, and managing traffic to deliver a high-quality user experience. Think of it as a firewall optimized for voice communications.

Today, we rolled out AlloyScan 26.7, bringing centralized visibility into critical Windows issues, stronger control over site access, simpler macOS agent deployment, and more efficient network communication. Here are the details.

Summary Physical AI—machines and industrial systems that sense conditions, reason, and act in the real world—needs two things from operational data: detailed history for training, and real-time telemetry for inference. Traditional data historians weren’t built for either at the speed Physical AI requires. Four gaps result: limited real-time access, compression that strips model-relevant signal, IT/OT fragmentation, and site-by-site architectures.

Much of what the Microsoft 365 audit log records as user activity is the platform itself. Twelve patterns that look like exfiltration, password spray or privilege escalation, and what each one really is.