JupiterOne launches Continuous Controls Monitoring

JupiterOne unveiled JupiterOne Continuous Controls Monitoring (CCM) as a way to test whether controls operated as intended, using a current view of controls rather than point-in-time checks. The update targets security and compliance teams that need ongoing evidence of control effectiveness.

The company said that compliance automation shortened audit preparation, but many tools still did not demonstrate whether controls worked in practice. It added that scaling efforts often required combining evidence from multiple systems, reviewing configurations by hand, and verifying whether controls stayed effective after implementation.

CCM used a graph data model to evaluate controls across relationships involving assets, identity, and configuration. Tests were fully transparent, with exact query, integration source, and test logic visible to security teams and auditors. The approach tested controls against live asset data to identify control drift and maintain supporting evidence as the environment state changed.

JupiterOne CCM was built on JupiterOne’s graph-native platform and used more than 200 integrations. JupiterOne AI supported natural-language questions about control status, evidence, drift, and framework alignment. “Most organizations can show that a policy exists. Far fewer can prove, at any moment, that the control behind that policy is actually working,” said Kevin Tonkin, Chief Product Officer at JupiterOne. “GRC tools were built to manage compliance workflow. Security teams need something different — a way to prove that the technical controls behind every policy are actually working, in environments that change by the hour. JupiterOne CCM brings a security lens to GRC.”