Skip to main content
Probo
Get compliant

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Document Management Draft, approve, and sign your policies Employee Portal Your whole team’s compliance, in one portal Access Review Monitor user access across all your systems AI Agents Run compliance from the tools you use Cookie Banner Consent that follows every visitor's law Device Agent Continuous security posture for every device Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Device Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools
Changelog
Governance

CMMI maturity levels on controls

Controls now carry a real CMMI maturity score instead of a binary implemented flag, showing how mature each control actually is.

CMMI maturity levels on controls screenshot

Controls used to be implemented or not. A checkbox. Useful for a compliance binary, useless for tracking where a control actually is.

That boolean is gone. Controls now use a CMMI maturity level. You can tell the difference between a control that someone documented last week and one that’s been running and measured for a year. Auditors see it, your team sees it, and you stop pretending ad hoc work counts as mature.