Operations | Monitoring | ITSM | DevOps | Cloud

Dog-walk thoughts on vulnerabilities at scale More CVEs are being found, disclosed and weaponised faster than ever. For a small team with one product, that's manageable: a CVE lands, you fix it. But if you're running thousands of applications across tens of thousands of repos, "the teams will handle it" stops working. It becomes a governance problem.

Linux security is built for environments where resilience matters. From vulnerability management to long-term maintenance, securing open source at enterprise scale requires a robust approach across the software lifecycle. Robustness comes from how those practices work together and hold up over time.

As companies adopt AI coding tools, code review processes are breaking down. Traditional compliance methods are slowing teams down, but human engineers aren't going to spend hours reading AI-generated low-level code forever. How will SOC 2 adapt to the era of AI-driven development? Drop your thoughts in the comments and subscribe for more tech insights! Learn more: speedscale.com.

Curation plays an important role in enterprise Linux security. Knowing what enters your environment, how it's maintained and what you can rely on over time helps manage open source securely at scale. Understanding these considerations helps inform a deliberate approach to Linux security.

Think of an SBOM as your ingredient list. A common language describing everything that goes into a piece of software, every dependency and version, in one place. This video covers why SBOMs have gone from niche to mandatory, and why they're harder to pull off than the concept suggests: The concept is simple. Operationalizing it across a large, diverse tech stack is where it gets hard.

Linux security benefits from transparency. Open source makes code available for scrutiny, allowing vulnerabilities to be identified, understood and addressed. At enterprise scale, that transparency plays an important role in how Linux security is managed.

Microsoft finally patched a critical Copilot vulnerability nearly eight months after researchers first disclosed it — and the way the attack worked raises some unsettling questions about AI memory. The vulnerability chained together multiple flaws that could allow a malicious prompt hidden inside a webpage to be pulled into Copilot simply by asking it to summarize the page. From there, the attack could potentially access connected data from services like Gmail, Google Drive, and Google Calendar and exfiltrate that information using Copilot’s own capabilities. But the most concerning part may have been persistence.

Our Megaport technical expert, Steve Tu explains what IPsec is, how it secures network traffic, and where it’s used across VPN and cloud connectivity. About Megaport Deploying infrastructure should be fast and simple. Megaport’s software-defined platform provides private compute, network, and storage — so you can build secure, scalable infrastructure for cloud, enterprise, and global AI inference workloads. Trusted by the world’s leading enterprises, Megaport operates across 1,200+ enabled locations globally.

The gap between vulnerability disclosure and active exploitation is shrinking—often from weeks to mere hours. Traditional patching cycles no longer cut it. In this session, discover how AI-accelerated solutions can help you: Identify exposed assets faster Prioritize vulnerabilities by real-world risk Remediate across Windows, macOS, Linux, and hundreds of apps Verify success with a connected workflow Learn how our approach, powered by AI-driven insights and automation, can help you close the gap before attackers strike. Watch now and take control of your patch management.