Launching today
CRML

CRML

CRML is a declaritive language for writing cyberrisk as code

184 followers

We have infrastructure as a code, network as a code but dont have anything as Risk As a Code. CRML is an open, declarative, engine-agnostic and Control / Attack framework–agnostic Cyber Risk Modeling Language. It provides a YAML/JSON format for describing cyber risk models, telemetry mappings, simulation pipelines, dependencies, and output requirements — without forcing you into a specific quantification method, simulation engine, or security-control / threat catalog.
CRML gallery image
CRML gallery image
CRML gallery image
CRML gallery image
Free
Launch tags:Open SourceLanguagesGitHub
Launch Team / Built With
Anima Playground
AI with an Eye for Design
Promoted

What do you think? …

SANKET SARKAR

I was looking for a cyber risk engine to incorporate in our platform. I was surprised to see that there does not exist one in the entire internet. I went deep to understand, why it does not exist. Then I figured out its because, there is no way someone can write the cyber risks in a machine readable format. There is no declaritive language for this. Thats when I thought of creating this.

CRML started from dozens of messy, real conversations with security leaders, risk teams, and CISOs who kept telling us the same thing:

“We have frameworks… but when the board asks a decision question, we still scramble.”
CRML is our attempt to change that.

It turns scattered assumptions, spreadsheets, and narratives into structured, executable cyber-risk models — so teams can reason about scenarios, trade-offs, and investments with actual clarity instead of gut feel.

We’re launching CRML first because modeling is the foundation. Before dashboards, or automation… organizations need a clean way to think about risk.

We’d genuinely love your feedback:
• What’s broken today in cyber risk analysis?
• Where do models fall apart in practice?
• What would make this actually useful in your day-to-day work?

We’re here in the comments all day — fire away.

soubangi rajkhowa
💡 Bright idea

@faux16 Great initiative. The hardest part of risk is usually the 'human factor.' If CRML can help us structure behavioral risk as clearly as technical vulnerabilities, it will be a massive win for the industry.

SANKET SARKAR

@soubangi_rajkhowa Thats a good suggestion. We will work on it.

Jens Attenberger

@soubangi_rajkhowa 
Hey, I'm the co-author of the project. Just wanted to say that CRML can already do this today.
We have a control and scenario centric approach, which means you can easily create a behavior based (or behavior + technical vuln) scenario and then specify which controls are in place, which could mitigate this scenario. And the best is that scenarios are interchangeable. So researchers could publish scenarios everyone can then calibrate with the controls they have in place and their specific attack surface. :)

SANKET SARKAR

@soubangi_rajkhowa  @jens_attenberger I think the angle that she is trying to put here is the emotional, and mental state of things. As we speak, this thing is becoming an important factor on how people make decisions now

Catherine Cormier

Congrats on your launch guys!

SANKET SARKAR

@cathcorm Thank You So much

Piroune Balachandran
💎 Pixel perfection

Risk models living in spreadsheets means every assumption is implicit and nobody can diff them. CRML putting FAIR Monte Carlo and Bayesian modeling into the same YAML spec makes those assumptions versioned and reviewable, which is what most GRC tools still don't do. The real test is whether security teams adopt the spec or keep building bespoke models in Python notebooks.

SANKET SARKAR

@piroune_balachandran Absolutely on point. Its on all of us in the community to spread it and help them adopt it maybe. The initial adaoption will be a friction for sure but once they get the hang of it, I feel they would love it.

Piroune Balachandran

@faux16 Any example CRML specs in the repo to fork? That'd lower the adoption curve fast.

SANKET SARKAR
@piroune_balachandran Absolutely, we have kept a bunch of examples in the repo
Adam Lababidi

The "Risk as Code" approach is brilliant - moving from spreadsheets to Git-versioned YAML/JSON solves so many problems with audit trails and collaboration. CISOs struggle to give boards concrete answers because risk models are scattered across different tools and people's heads. Making it declarative and engine-agnostic means you're not locked into one framework. How does CRML handle sensitivity analysis? When boards ask "what if X happens", can you fork the model and compare scenarios side by side?

SANKET SARKAR

@adam_lab  Thank you for the appreciation. To answer the query, yes that can absolutely be done.

Jay Dev

This is so good. Exactly what I needed.

SANKET SARKAR

@jaydev13 Glad to know that. Would be great if you could share, how this will help you?