# Canonical MAAS v3.7.4 adds FIPS mode support for bare metal control planes

> **Key takeaway:** MAAS v3.7.4 introduces FIPS 140-3 compliant cryptographic controls for managing physical server infrastructure.

**Published:** 2026-11-18T22:26:26+00:00 
**Source:** Canonical / Ubuntu Server &amp; Kernel Blog 
**Category:** distro-news 
**Canonical URL:** https://fosswire.org/news/canonical-maas-v374-adds-fips-mode-support-for-bare-metal-co.html 

## Summary
Canonical has released MAAS (Metal as a Service) version 3.7.4, which introduces native FIPS mode support for its bare metal management control plane. This update is specifically designed for organizations in highly regulated sectors, such as government, defense, and finance, that must adhere to FIPS 140-3 security standards.

The update allows the MAAS control plane to enforce strict cryptographic policies during the discovery, provisioning, and management of physical hardware. Beyond securing the controller itself, MAAS can also automate the deployment of Ubuntu machines equipped with FIPS-enabled kernels via cloud-init workflows.

## Technical implementation of FIPS mode in MAAS
- **Cryptographic Enforcement:** When FIPS mode is active, the system restricts TLS and SSH connections to approved algorithms and validates specific key types and sizes.
- **Hardware Management Security:** The update mandates secure power management protocols, such as requiring IPMI connections to utilize cipher suite 17, and rejects any unsupported or insecure power drivers.
- **Controller Hardening:** MAAS automatically enforces security hardening upon startup if it detects a FIPS-enabled Ubuntu host, providing visibility into the compliance status via the MAAS API.
- **Provisioning Workflow:** The platform supports the deployment of FIPS-enabled kernels on managed nodes by utilizing Ubuntu Pro and cloud-init to install and reboot into compliant kernels after initial deployment.

## Why it matters
This release enables enterprise sysadmins to maintain automated, cloud-like workflows for bare metal hardware while meeting strict federal compliance mandates. It reduces the manual overhead of security auditing by integrating cryptographic validation directly into the infrastructure-as-code lifecycle.