Evidence as an Input
Scan results aren’t the end — they’re the input to the next control. Evidence must be tied to fingerprints so it’s reusable.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
Why Release Control Takes Weeks
The industry standard for release control is painfully manual: long-form policy documents, ServiceNow forms, human approvals, meetings, and tickets that take days or even weeks to close. In this video, Mike Long (CEO & Co-founder, Kosli) explains the difference between manual release control and an automated, zero-trust model where evidence is collected automatically, provenance identifies the artifact, and approvals can be fully codified.
Evidence as an Input
Evidence isn’t something you produce at the end — it’s something every control generates for the next one. In this video, Mike Long (CEO & Co-founder, Kosli) explains how vulnerability scans produce evidence tied to the artifact fingerprint and the policy file used, and how that evidence becomes an input to downstream controls like release approvals. This is the core of reusable, continuous compliance.
How Do We Trust the Evidence?
Evidence only matters if you can trust it. And you can only trust it if the artifact behind that evidence has a verifiable, untamperable origin. In this video, Mike Long (CEO & Co-founder, Kosli) explains why artifact binary provenance is the foundation of trustworthy evidence, and why zero-trust delivery collapses without it. Video Timeline.
Faster Code, Slower Delivery: The Agentic Coding Paradox in Regulated Enterprises
Imagine for a moment that agentic coding tools really do deliver on their promise. Code is written faster, tests are generated automatically, and refactors that once took days now take minutes. On paper, software delivery should accelerate dramatically. Now imagine you work in a regulated enterprise. The code is ready, but production is still days or weeks away.
The Last Mile - Why Banks Must Automate Trust to Gain Velocity
The financial service industry has spent years modernising their software delivery pipelines. Build and test cycles are fast, infrastructure is automated, and engineering capability is no longer the bottleneck. The slowdown now occurs at the end of the process: the last mile, where a change must prove it is safe before it can enter production. This final step is governed by a trust layer with people in it.
Enhanced Environment Compliance with Environment Policies
We're excited to announce an important enhancement to Kosli that will improve how environment compliance is managed across your organization. Starting with our next release, all compliance evaluation for Kosli environments will be consolidated through our powerful Environment Policies feature.
Enhanced Environment Compliance with Environment Policies
We’re excited to announce an important enhancement to Kosli that will improve how environment compliance is managed across your organization. Starting with our next release, all compliance evaluation for Kosli environments will be consolidated through our powerful Environment Policies feature.
Building the Future of Software Delivery Controls: Inside the FINOS SDLC Governance Working Group
In October, technologists from across the financial industry gathered in New York for OSFF 2025 where the general theme was clear: open collaboration has moved from promises to proof. Projects like Fluxnova and OpenGris showed how institutions can build shared, production-grade infrastructure. The Common Cloud Controls and AI Governance Framework demonstrated that regulatory assurance can be achieved collaboratively, not competitively.
An Open SDLC Controls Framework for Financial Services
How can financial institutions align on software delivery governance without slowing down innovation? At FINOS OSFF New York 2025, Deutsche Bank and Morgan Stanley introduced the new SDLC Governance Working Group — an open collaboration under FINOS to create a Common Controls Catalogue for software delivery. Kosli's Mike Long helped form and participates this group, contributing expertise in continuous compliance automation and controls engineering to connect the engineering and policy communities.