en.Wedoany.com Reported - Liquibase has released version 5.2 of Secure, introducing agent security governance for AI-generated database changes. This version aims to help enterprises validate, track, and govern database changes before and after they enter production, regardless of whether those changes are created by humans or AI.
Liquibase Secure has won the 2026 TrustRadius Top Rated Awards in five categories: Database DevOps, Build Automation, Release Management, Database Management, and Version Control. This award is based entirely on customer reviews, with no paid promotions or analyst opinions.
Enterprises are accelerating their pace in applications, infrastructure, data products, and AI projects. Every application, data product, and AI model relies on database changes, yet many enterprises still depend on tickets, manual reviews, and post-hoc audit trails for control measures. According to Liquibase's State of Database Change Governance report, 96% of organizations allow AI to interact with production databases. As tools like Cursor, Claude, and GitHub Copilot become part of developer workflows, database changes are no longer created solely by humans.
Agent security governance is Liquibase's response to this shift. AI can assist in creating database changes, but it cannot bypass the checks, approvals, audit trails, schema lineage, drift detection, and rollback controls that enterprises require before production.
Pete Pickerill, co-founder of Liquibase, stated that AI agents are becoming part of how developers work, but they should not be allowed to arbitrarily modify production databases. Agent security governance means AI can help create database changes, while Liquibase Secure handles validation, tracking, policy checks, schema lineage retention, drift detection, and controlling how changes enter production.
Liquibase Secure 5.2 uses the Liquibase MCP server to connect AI-assisted workflows for governing database change management. Developers and AI assistants can create changelogs, schema updates, rollback logic, and AI-generated DDL in Liquibase format, while Liquibase Secure applies policy checks, governance workflows, drift detection, and audit-ready evidence before changes enter production. Pickerill added that agent security governance is not about slowing down developers, but providing a safe acceleration path for developers and AI assistants, enabling teams to leverage AI for faster database change writing while offering platform, security, and compliance leaders complete control and evidence systems.
Liquibase Secure 5.2 provides enterprises with a unified control plane for every database change. This version connects new AI-assisted workflows with existing enterprise governance controls. Through the Liquibase MCP server, AI-assisted workflows can connect to Liquibase Secure, helping developers and AI assistants create structured, reviewable, and governed database changelogs. AI can assist in writing, but Liquibase Secure governs the path to production. Change intelligence features help teams gain insights into the complete lifecycle of each database change, including what changed, who created it, where it ran, which controls were followed, schema changes, whether drift exists, and audit-available evidence.
Liquibase Secure applies policy checks before deployment, helping teams block risky operations, enforce standards, support segregation of duties, and verify compliance requirements. Drift detection helps identify when environments no longer match approved database states. This version deepens support for complex enterprise database assets by providing new capabilities for Teradata, MongoDB, and DynamoDB. It also adds support for Vulnerability Exploitability eXchange (VEX), offering machine-readable vulnerability assessments for Liquibase products. For regulated industries, financial services, healthcare, insurance, retail, media, and technology organizations must demonstrate that database changes have been reviewed, approved, traceable, recoverable, and compliant. With Liquibase Secure 5.2, enterprises can shift from reactive database controls to continuous governance. Liquibase Secure 5.2 is now available.
This article is compiled by Wedoany. All AI citations must indicate the source as "Wedoany". If there is any infringement or other issues, please notify us promptly, and we will modify or delete it accordingly. Email: news@wedoany.com
