Operations | Monitoring | ITSM | DevOps | Cloud

The rate at which vulnerabilities are being exploited is on the rise. The VulnCheck company, which specializes in vulnerability intelligence, found that in Q1 2025, 28.3% of vulnerabilities were exploited within 1 day of CVE disclosure. Keeping your systems up to date is more important than ever. The reality is that many security teams are running scans and then exporting to giant spreadsheets, which are “tossed over the wall” to the Operations team with little context.

The gap between security operations and IT operations poses significant risk. It’s increasingly clear that DevOps leaders, IT managers, and enterprise teams face an uphill battle to manage growing threat complexity, endless patches, and compliance requirements while operating in silos. Bridging this gap is essential to effectively manage risks and enhance operational efficiency.

You can infer from Jensen’s keynote speech that moving forward, AI will need to be evaluated by operational outcomes, rather than by speed or accuracy KPIs, such as resolution rates or proactive service restorations in ITSM. ITSM was designed to make complexity manageable by modifying user interfaces, workflows, and playbooks for automation across sprawling operational environments. Automation has improved speed, but never changed the fundamental model: humans being the decision engines.

Since announcing changes to our OSS plans as well as introducing the new licensing starting with PDK 3.5.0, the team has received questions from the community around how the changes will affect them. In this article, we’ll highlight some helpful resources about how you can develop and contribute to modules on the Forge and ensure compatibility with Puppet Core and Puppet Enterprise.