Did you know that DMTF has a Security Response Task Force (SRTF) and a reporting system for security issues? The Task Force is responsible for coordinating and managing reported security issues or vulnerabilities related to DMTF standards and its open-source sample implementations.

DMTF recently published the latest release of the Common Information Model (CIM) Schema, version 2.56. The fifty-sixth update to CIM since the launch of 2.0, this widely used standard provides a common definition of management information for systems, networks, applications, and services.

DMTF’s Redfish Forum would like to invite anyone interested in learning about the Redfish 2025.4 release to join a live webinar, hosted on Zoom, on Thursday, February 5th, at 9:00 a.m. PT.

The Forum chairs will present the contents of the release. A Round Table discussion will be held immediately following the webinar.

DMTF’s Redfish^®, Release 2025.4 is now available for public download. Designed to deliver simple and secure management for hybrid IT and the Software Defined Data Center (SDDC), the latest release of the Redfish standard includes 28 schema updates and new additions to the Message Registry.

Key highlights of the Redfish 2025.4 release are the additions of:

As we reflect on another remarkable year, I’m proud to share DMTF’s continued progress in advancing open standards that shape the future of AI and traditional infrastructure management. 2025 has been a year of collaboration, innovation, and engagement — from key updates to our Redfish® standard to growing partnerships across the industry. None of this would be possible without the dedication of our members, working groups, and alliance partners who continue to drive interoperability and efficiency across the ecosystem.

DMTF’s Security Protocols and Data Models (SPDM) Working Group has recently released a new Authorization Specification (DSP0289). This specification adds authorization capabilities to the existing suite of SPDM specifications. Authorization allows a device to verify that a requester has permission to access protected functions.