Security
Security and control, by design
Lanestep sits on the path to Prod. Each customer gets an instance of its own, and Lanestep is designed so that each person is known, each action is recorded and credentials stay out of its records.
Security measures in Lanestep
A dedicated instance for each customer
Each customer gets an instance of Lanestep of its own, with its own database, secrets and identities, isolated from every other customer. We host it for you, or it runs in your own Azure subscription.
- Hosted by Lanestep, its records are in a database of its own that Lanestep runs. In your own Azure, they are in a PostgreSQL database you control.
- Either way, deployments run with the identities you give each environment, under your own policies.
- An environment Lanestep only observes is read, not deployed to.
Sign-in with Microsoft Entra ID
People sign in with their accounts in your own Microsoft Entra ID directory.
- Sign-in uses the OpenID Connect authorization code flow, with PKCE.
- Sessions are kept on the server. The browser holds only a random, HTTP-only cookie.
- From a browser, requests that change something are accepted only from Lanestep’s own address.
- Every record names the person who made it.
Roles and separation of duties
Six roles decide what a person can change: Admin, Release manager, Maker, Tester, Approver and Viewer. A person can hold several.
- An approval counts only from someone who built none of the changes in the release.
- Passing a finding needs a role the policy names, and a written reason.
- A refused action says which role would allow it.
An append-only audit trail
Each write adds an entry to the audit trail: when, who, what and which record. Entries can be added, but not changed or removed.
- A change to a person’s roles records the roles before and after.
- A booking of Stage records when it started and when it ended.
- The database is set to refuse any change to an entry, or its removal.
An evidence pack for the change board
Each release has one document that a change board can read without a meeting.
- The approval policy, the decisions, and every guard finding and pass as they stood when the deployment to Prod started.
- Each change, with where it was deployed, when and by whom, and its solutions and their versions.
- The syncs, any freezes the deployment met, and the audit trail with the names of the people.
- Print it, save it as a PDF or download it as JSON.
Identities and secrets
Lanestep deploys to each environment with the identity you give it: an application in your Microsoft Entra ID or, when Lanestep runs in your own Azure, a managed identity.
- The workspace file says where each credential is, not the credential itself. Lanestep is designed to keep secrets out of its database, its logs, the audit trail and the browser.
- With a managed identity, there is no secret to keep.
- Lanestep shows which identity each environment uses, not its credential.
Report a security concern
If you think you have found a security issue in Lanestep or this website, write to [email protected]. Please include enough detail for us to reproduce it. Give us reasonable time to look into it before you share it.
Bring your security review to the demo
Walk through your dedicated instance, sign-in, roles, identities and the audit trail with the team building Lanestep, and bring your questions.