Create a free account
The same account you'd use for the platform. Sign up, verify your email and you land in Drova Labs.
This is a Drova Labs prototype. Still taking shape, but ready to try today. Explore Labs for free
A control libraryfor risk and compliance
Keep each control in one place, and prove it once for the frameworks that ask for it.
The same control often lives in several places, with a different status in each. The controls library keeps every control in one place, with its owner and last test, so you know where each one stands. Sheila AI points out which controls to fix first.
Why we're building this
The same control, kept in three places
We hear it a lot: a control gets written up wherever it was first needed. An access review appears under a cyber risk, again under ISO 27001, and again in a testing spreadsheet. The copies drift apart until one says effective, another says never tested, and nobody is sure who owns it. Then the same evidence gets gathered again for each framework.
In Drova, risk, compliance and resilience share one platform, so a control shouldn't have to live in three places. We're building the controls library to give every control one home that your risks and frameworks all link to, mapped once and reused wherever a framework asks for it.
One place for every control
See every control and where it stands
Every control across risk, compliance and resilience sits in one library. Each one shows its owner, when it was last tested, the risks it protects and whether it works. Filter by framework or risk to find the ones you need. In the sample, you can see at a glance that 10 of the 25 controls have never been tested.
Know where to start
Fix the controls that matter most first
Sheila AI points out which controls to look at first, such as two key controls in the sample that have never been tested, one of them with no owner. Each control also shows the effort it takes against the protection it gives, so you can see which controls earn their keep and which need rethinking.
Prove it once
Test a control once, reuse the evidence
Link a control to the risks, requirements and incidents it covers, and prove it once for all of them. Adding a control starts with one sentence. Describe what you need and Sheila AI drafts it, with a suggested owner and the risks it protects, ready for you to check.
Three steps to try it
A few minutes gets you inside the prototype, and a say in it.
Open Centralised controls library
Take the short tour, then open the control Sheila AI flags first and see what it protects.
Tell us what would make it work for you
Share feedback from inside the prototype. It goes straight to the people building it, and we report back what changed.
The controls library is open in Drova Labs now. Tell us how many places your controls live today.
Try it before it ships
Centralised controls library
Questions and answers
Is this in the product today?
Not yet. It's a working prototype in Drova Labs, built on a sample tenant, so you can try the model while it's still taking shape. We say so in Labs and in New Frontier when it ships.
What can I try right now?
A sample library of 25 controls for a fictional software business. You can see which controls work and which have been tested, where Sheila AI would start, a full control record, and adding a control from one sentence.
Does Sheila AI create controls on her own?
No. She drafts a control from your description and points to the ones that need attention. A person checks the draft, gives the control an owner and runs its tests.
What happens to my feedback?
It goes straight to the person building the prototype. We report back what changed, in Labs and by email.
Does it use my data?
No. The prototype runs on a sample tenant, and you're never asked to upload anything to try it.
