Lars ArtmannSOX implementation

SOX controls, built where your code ships.

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.

evidence-pack, 2026-Q4 ✓ passed
export.auditor_sample.zip, 4.2 MB. Immutable CI/CD logs, approval records, sign-offs.
Your auditor samples the trail, not your engineers.
SOX 302 / 404 implemented Platforms: GitLab, GitHub, Azure DevOps, Jenkins Tools: SonarQube, Snyk, Checkmarx, Black Duck, Fortify Remote-first, English and German

The requirements are written. The pipeline cannot prove them.

Your auditors read the development platform now. Sound familiar?

  • The evidence request arrives. The pipeline cannot produce it. The control lives on paper, not in the platform.
  • Security tools run somewhere. Nobody can show which build they gated, or who approved the merge.
  • The quarterly access review is due. Nobody can say who had what, when, and who approved it.
Section 302 makes the certification quarterly and personal. Your CEO and CFO sign, every quarter:
“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
Section 906 makes a false certification a crime. Willful certification of a false report carries a fine of up to $5,000,000 and up to 20 years in prison. The CEOs and CFOs of Enron and WorldCom did not go to jail over a bad quarter. They went to jail over a certification. 18 U.S.C. § 1350, added by Pub. L. 107-204 (Sarbanes-Oxley Act of 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.

SOX, in plain words.

Five minutes of context, so the rest of this page needs no translation.

Who SOX applies to

Companies listed on US exchanges, foreign issuers trading in the US, and their subsidiaries. Size does not exempt. Public listing decides.

What it demands

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.

What auditors test

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.

Map, configure, wire, prove.

Auditors do not accept binders. They accept controls that run and logs that prove they ran. Every control gets built in the platform itself.

  1. Map

    Week 1

    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.

  2. Configure

    Weeks 2 to 3

    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.

  3. Wire

    Weeks 3 to 6

    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.

  4. Prove

    Steady state

    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.

What gets handed over

Control matrix

Each requirement mapped to the system that enforces it: SOX section, control, platform, owner.

Auditors find their answer in one document.

Pipeline gates

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.

Security tooling, wired

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.

Evidence pack and runbooks

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.

Who you work with

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.

Engagements, quoted per project

Current opening: 50% capacity from 23 November 2026 (latest start 1 January 2027), six months plus, mostly remote, on-site days by arrangement.

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
Start with a work package
CURRENT OPENING

The 6-month program

50% capacity

One engineer embedded in your platform team.

  • SOX controls configured, not drafted
  • Security tooling wired as pipeline gates
  • Evidence pack that refreshes itself
  • Start from 23 November 2026, latest 1 January 2027
Ask about the current opening

Ongoing fractional

1 day per week

Steady state after the program, or a light footprint from day one.

  • Access reviews every quarter
  • New systems reviewed before they ship
  • The standing answer to “can we prove this control?”
Discuss the fractional option

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.

Questions before the call

Are you an auditor?

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.

Which platforms and tools does he actually configure?

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.

Which SOX requirements does this cover?

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.

We are a European subsidiary of a US-listed parent. Does this touch us?

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.

Remote or on-site?

Mostly remote, with individual on-site days where they help. Working language English, German on top.

How do we start?

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.

What do the first two weeks produce?

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.

How does this survive an auditor who does not trust CI/CD?

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.

Your officers sign what the pipeline produces. Build it so they can.

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.