CRE:OS compliance, automated for SOC 2, ISO 27001 & Cyber Essentials
OneClickComply connects to CRE:OS through the OneClickComply Companion, our AI browser agent, and checks how it is configured against SOC 2, ISO 27001, Cyber Essentials and NIST CSF. Checks include: default branch requires pull-request review, MFA required for all organisation members and secret scanning enabled on all repositories. Every result is stored as audit evidence, so there are no screenshots to collect.
SOC 2 · ISO 27001 · Cyber Essentials · NIST CSF
- Set up in minutes
- No API keys or extra logins
- Evidence collected continuously
- Built for UK teams
Continuous control checks
What OneClickComply checks in CRE:OS
Source control is where change management lives. Branch protection, code review and secret scanning are standard SOC 2 and ISO 27001 asks.
Default branch requires pull-request review
MFA required for all organisation members
Secret scanning enabled on all repositories
See it work
Watch OneClickComply check CRE:OS
The Companion, our AI browser agent, opens CRE:OS with the access you already have, reads the settings that matter, tests them against your controls and files the result as evidence.
CRE:OS admin
Security settings
- Default branch requires pull-request review
- MFA required for all organisation members
- Secret scanning enabled on all repositories
OneClickComply Companion
- Opened CRE:OS with your existing session
- Reading repositories, branch protection, members
- Default branch requires pull-request review
- MFA required for all organisation membersGap found, fix it in one click with OneClickFix
- Secret scanning enabled on all repositories
Evidence saved and mapped
CRE:OS evidence, collected automatically
The CRE:OS evidence auditors ask for, captured on a schedule and stored against the right requirement. No more screenshots the week before the audit.
- Repositories
- Branch protection
- Members
- MFA status
- Secret scanning
- Audit log
Mapped to your frameworks
Every CRE:OS check is mapped to the controls it satisfies, so one piece of evidence counts everywhere it applies.
Set up in minutes
How to connect CRE:OS to OneClickComply
- 1
Add the browser extension
Install the OneClickComply Companion, our AI browser agent. There's no API key to create and nothing to change in your stack.
- 2
Open CRE:OS as normal
The Companion reads CRE:OS's admin settings that matter for compliance, using the access you already have. No extra logins.
- 3
Fix it in one click
Settings are checked against your controls and the evidence is stored. When something fails, OneClickFix can correct it in CRE:OS for you, with the change logged as evidence.
See CRE:OS checked live against your controls.
CRE:OS security & compliance FAQs
How does OneClickComply connect to CRE:OS?
Through the OneClickComply Companion, our AI browser agent. It reads CRE:OS's admin settings using the access you already have, so there's no API key to create and no extra login. When a setting fails a check, OneClickFix can correct it for you.
What does OneClickComply check in CRE:OS?
Its checks for CRE:OS include: default branch requires pull-request review, MFA required for all organisation members and secret scanning enabled on all repositories. Each result is stored as evidence against the requirement it satisfies.
What CRE:OS evidence do auditors ask for?
For developer tools and code tools, auditors usually want repositories, branch protection, members and MFA status. OneClickComply captures it on a schedule, so it's ready before they ask.
Which frameworks does the CRE:OS integration cover?
CRE:OS evidence is mapped to SOC 2, ISO 27001, Cyber Essentials and NIST CSF.
Also connects with
Other developer tools and code tools we connect to
Using more than one developer tools and code tool? OneClickComply connects to these too, so your evidence stays in one place.
Get CRE:OS audit-ready this week
OneClickComply connects to CRE:OS and the rest of your stack, collects the evidence and tells you exactly what to fix. If it has a web admin console, we can work with it.
Logos provided by Logo.dev. All product names and logos are trademarks of their respective owners.