Work package
Fixed scope
Days to weeks. One control, one platform, or one tool integration.
- Concept, implementation, documentation, handover
- Accepted before the next package starts
- Evidence pack included
For engineering leaders at software organizations that answer to SOX.
Lars Artmann configures the controls inside GitLab, GitHub, Azure DevOps, and Jenkins. He wires the security tools. He hands over the evidence trail. Not an auditor. The engineer on your side of the four-eyes principle.
One email starts it: lars@artmann.tech. Or call +49 173 155 9729. Replies within one business day.
One engineer, accountable by name. Tech consultant for over a decade. CEO of Artmann Holding GmbH and Artmann Technologies GmbH. No juniors, no bench, no handoffs.
Your auditors read the development platform now. Sound familiar?
“I certify that this report fully complies with the requirements of the Securities Exchange Act of 1934, and that the information fairly presents, in all material respects, the financial condition and results of operations of the issuer.”Section 302, Public Law 107-204, signed July 30, 2002
SOX makes officers sign what the pipeline produces. That is satisfied in one place: the platform where your engineers work. That is where the implementation belongs.
Five minutes of context, so the rest of this page needs no translation.
Companies listed on US exchanges, foreign issuers trading in the US, and their subsidiaries. Size does not exempt. Public listing decides.
Section 302: officers certify every quarterly report, personally. Section 404: management assesses internal control over financial reporting each year, and the external auditor tests it. Section 906: false certification is a crime.
ITGC, the IT general controls: who can reach which system, and when reviews happen. How changes reach production, and who approves them. Whether operations run reliably, and can prove it.
The big picture is one chain: your officers sign at the top, your auditors sample the middle, your engineers work at the bottom. Controls fail where the three fail to meet. That meeting point is the development platform, and that is where Lars builds.
Auditors do not accept binders. They accept controls that run and logs that prove they ran. Every control gets built in the platform itself.
Your controls, mapped to platforms: which control lives in branch protection, which in the IdP, which in a pipeline gate. The matrix names the system for every requirement.
Branch protection, merge-request approvals, signed commits, protected runners, joiner-mover-leaver in the IdP. Changes land only inside the access and change-management authorizations you define.
The scanners on your shortlist, wired as gates: which findings block a release, which warn, who signs off. SonarQube, Snyk, Checkmarx, Black Duck, Fortify, or the open-source stack.
Evidence exports on schedule: immutable CI/CD logs, approval records, access review sign-offs, the findings trail. Your auditors sample the trail, not your engineers.
Every work package runs the same arc: concept, build, document, handover. When it ends, your team owns the controls, and the runbooks prove it.
Each requirement mapped to the system that enforces it: SOX section, control, platform, owner.
Auditors find their answer in one document.Branch protection, merge approvals, signed commits, secrets scanning, SAST and dependency gates: enforced where merges happen.
The main branch becomes the control, not a policy PDF.SonarQube, Snyk, Checkmarx, Black Duck, Fortify, or the open-source stack: Semgrep, Gitleaks, Trivy, OSV-Scanner. Configured, tuned, and reported into CI/CD.
Findings gate releases instead of decorating dashboards.Immutable CI/CD logs, approval records, access reviews: exported on schedule, in the shape auditors sample. Runbooks hand each control to your team.
Handover means your engineers run it without Lars.Lars Artmann is an engineer who runs his own compliance program.
Tech consultant for over a decade. CEO of Artmann Holding GmbH and Artmann Technologies GmbH. He has spent those years building the systems controls are written about: deployment pipelines, access systems, event-sourced ledgers.
Proof you can check. His own CRM journals every call, email, and sent document, event-sourced, with actor and timestamp. A readiness review of that audit trail ran this month. Every claim in it is machine-checkable. His standing SOX research report maps ICFR requirements to platform controls, clause by clause. Both are working papers, and the readiness review has a public summary: read the case study.
You are not hiring a firm or a bench. You are hiring one named engineer for the work packages.
Current opening: 50% capacity from 23 November 2026 (latest start 1 January 2027), six months plus, mostly remote, on-site days by arrangement.
Fixed scope
Days to weeks. One control, one platform, or one tool integration.
50% capacity
One engineer embedded in your platform team.
1 day per week
Steady state after the program, or a light footprint from day one.
Rates are quoted per project, once the scope is named, and they compete with agency rate cards that bill a bench. Here, one named engineer owns the work packages. Terms, NDA, and procurement format follow your process.
No, and requests like this one are explicit about it. The implementer and the approver must be different people, so Lars never signs off controls he built. Risk acceptances, regulatory approvals, and independent reviews stay with your responsible bodies. He builds until those bodies have something clean to approve.
Development platforms: GitLab, GitHub, Azure DevOps, Jenkins. Security tooling: SonarQube, Snyk, Checkmarx, Black Duck, Fortify, plus the open-source options: Semgrep, Gitleaks, Trivy, OSV-Scanner. The stack follows your estate, not a resale agreement.
The ITGC layer your auditors test: access management (joiner-mover-leaver, quarterly reviews, privileged access), change management (branch protection, approvals, signed commits, deployment gates), and operations (monitoring, backup and recovery evidence, incident records). The control matrix names the SOX section for every line.
Yes. ICFR scope reaches into subsidiaries, and your auditors will sample your systems, not just headquarters. The controls get built in your platforms, and the evidence exports speak to both your auditors and the parent's.
Mostly remote, with individual on-site days where they help. Working language English, German on top.
One call or video meeting about your estate and timeline. Then a written plan per work package before any change lands. NDA by default, and changes only inside the access and change-management rights you set.
The platform mapped to controls, the first gates live in your real build, and evidence pack version one. You see working controls, not a slide deck.
They do not have to trust it. They sample it: the export pairs every control with the immutable log that proves it ran, in the period they test. That is the same standard your team already meets for builds. Now it meets theirs.
One email starts the conversation: lars@artmann.tech. Or call +49 173 155 9729. Replies within one business day.
P.S. Not an auditor, not a compliance department, not a tool vendor. If you need an attestation engagement or a managed service, that is someone else's door. If you need the controls themselves, built in the platform your engineers live in, this is the door.