Security you can
show

We help software houses, SaaS companies and IT teams in finance secure the software they build — with evidence produced at every release.

What we do

CyberForge works on the security of the process in which software is made. We work where the code is actually made: at feature design, change review, build and release.

We specialise in technology and financial companies: banks, fintechs, software houses and software vendors. One thing connects them — they have to deliver fast while proving to a client or a regulator that they do it safely.

We do three things: we train teams, measure process maturity, and implement security practices. We start where there is a real problem — sometimes with a single workshop, sometimes straight with an implementation.

The principles we stick to

We base every project on these — from the first conversation to handing over the finished solution.

We start from your repository

We assess your real pipeline and one specific release, not questionnaire answers. Only then do we know what makes sense — sometimes the problem lies somewhere entirely different than you assumed.

We sell only the scope you will use

If after a conversation we conclude that one workshop is enough for you instead of a three-month engagement — we will say so, even though we earn less. Selling you something you won't use is the shortest way to make sure you don't come back.

We finish when the change works

A project does not end with a report. It ends when the change works in your system and has survived the first weeks of the team's normal work — so that the next audit does not show the same gaps.

Your team keeps its pace

A control that adds fifteen minutes to a build or floods people with false alarms will be switched off within a week — and rightly so. We choose tools and thresholds so the signal is useful. Security developers hate simply does not work.

Meet our founders

CyberForge is built by two founders who are responsible for its direction, the standard of work, and what ultimately reaches the client.

Michał Jaśniewski, co-founder of CyberForge
Co-founder
Michał Jaśniewski

Responsible for business development and client relationships. Sets the scope of projects and makes sure they answer a real problem, not what is easier to sell. He leads the first conversation and he stands behind what we promise you.

Business developmentClient relationshipsScope and pricingRegulatory compliance
LinkedIn →
Szymon Mytych, co-founder of CyberForge
Co-founder
Szymon Mytych

Leads the technical team and owns the standard of delivery. Oversees every implementation — from the first configuration to the handover to your team — designs secure delivery processes and leads threat modeling. He decides whether a solution is ready to hand over to the client.

Team leadershipDelivery oversightSecure SDLCThreat modeling
LinkedIn →

We work in what
your team already uses

We select and implement security tools for your process — starting with the ones you already have. Everything we implement stays with you and runs in your team's hands.

Build and release

  • GitHub Actions
  • GitLab CI
  • Azure DevOps
  • Jenkins
  • Bitbucket Pipelines
  • Argo CD

Containers and Kubernetes

  • Kubernetes (k8s)
  • k3s
  • AKS · EKS
  • Rancher
  • OpenShift
  • Docker · Helm

Code and dependency analysis

  • CodeQL
  • Semgrep
  • SonarQube
  • Snyk
  • Trivy · Grype
  • Dependency-Track

Security testing

  • OWASP ZAP
  • Burp Suite
  • Nuclei
  • Schemathesis
  • DefectDojo

Secrets and access

  • HashiCorp Vault
  • AWS Secrets Manager
  • Azure Key Vault
  • TruffleHog · Gitleaks
  • OIDC

Supply chain

  • CycloneDX · SPDX
  • Syft
  • Cosign / Sigstore
  • SLSA
  • in-toto

Infrastructure as code

  • Terraform
  • Ansible · Pulumi
  • Checkov
  • tfsec · Terrascan

Policy and modeling

  • OPA / Rego
  • Kyverno
  • Falco
  • OWASP Threat Dragon
  • IriusRisk
  • STRIDE

Monitoring and observability

  • Prometheus
  • Grafana
  • Loki
  • OpenTelemetry

Using a tool that is not on this list? We plug into what works for you, instead of replacing everything from scratch. Replacing a tool is the most expensive and least often necessary way to improve security.

Let's find where risk
enters your delivery process

We reply within 24h on business days