Controls that hold
Separation of duties
The author never approves their own change. People who committed to it can be refused or flagged, and an approver who merges it can be flagged or recorded as non-compliant.
Read the docsFour-eyes configuration
With Review control changes on, changes to policies, approver pools, risk settings, change freezes and sign-in wait for a second person.
Read the docsEmergencies stay visible
Who declared an emergency and when is recorded, audited and announced; the company can limit who may declare one.
Read the docsDirect pushes are caught
Changes that reach a gated branch without an approved merge request are reported as violations.
Read the docsEvidence for change management controls
Merge Pilot does not make you compliant on its own. It keeps the records that the change management controls of these frameworks ask for, and the compliance report puts a period's records in one CSV or PDF file for the auditor.
SOX IT general controls
Change management over the systems behind financial reporting: each change to a gated branch is approved by someone other than its author before it merges, and the report lists every change of a period with its policy, approval, scans and merge.
Read the docsSOC 2, CC8.1
Changes are authorized, tested and approved before they are put in place: the policy's checks and the change approval apply to the latest commit, and each merge request keeps its record.
Read the docsPCI DSS v4.0, requirement 6.5.1
Changes follow a procedure with documented approval by authorized parties and testing: the change approval in Jira or the built-in tracker, with the CI and scan results of the change.
Read the docsISO/IEC 27001:2022, control 8.32
Changes are subject to change management procedures: change policies decide, per kind of change, which checks it must pass and who must approve it, enforced at the merge button.
Read the docsEU DORA, article 9(4)(e)
Documented ICT change management: every policy save is a new version, each merge request records the version that decided it, and changes made outside change management are reported.
Read the docsNot the DORA metrics
The EU Digital Operational Resilience Act is a regulation. The DORA metrics (deploy frequency, lead time, change failure rate and MTTR) measure delivery; Merge Pilot reports those too, from merges into production branches.
Read the docsAccess
Roles
Platform admins run the instance; in each company, people are company admin, policy manager, auditor (read-only) or user.
Read the docsSingle sign-on
OIDC and SAML 2.0 per company with roles from groups, and the company's LDAP directory; each can be limited to chosen groups. Platform admins keep a password sign-in; when passwords are turned off on the platform, it is recorded as break-glass.
Read the docsAPI tokens
Only a hash is stored and the token is shown once; tokens live at most 365 days.
Read the docsSign-in protection
Repeated failed sign-ins slow down further attempts and lock the guessing address out of the account, for 15 minutes by default (a company can set a longer lockout and fewer attempts), so an attacker cannot lock the real user out.
Read the docsData
Encrypted secrets
Connection tokens and other secrets are stored encrypted with AES-256-GCM.
Signed webhooks
Incoming VCS and tracker webhooks are verified, and outgoing ones are signed.
Read the docsAudit log
Decisions, votes, setting changes and sign-ins, with who, when and what changed.
Read the docsYour infrastructure
Merge Pilot is self-hosted: its data stays in your environment.
See it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.
