Dependency-Track Experts in Germany
matched in minutes from over 15,000 CVs with the power of AIHire experts who set up Dependency-Track, connect SBOM pipelines, tune policy rules, and keep component risk visible across release cycles. Get fast, precise matching with vetted, available freelancers.
Meet FRATCH Experts in Germany, who have recently used Dependency-Track
Alejandro Prieto
Last position:
DevOps Consultant at Freelance
- Kubernetes: EKS management, cluster upgrades and stability improvements, Infrastructure-as-Code reviews and updates, AWS support, and cost optimization.
Halil Oeztoprak
Last position:
Senior Cloud Operations & DevSecOps Engineer (Azure / Terraform / CI-CD) at KfW Bankengruppe
Regulated environment within a German banking group (approx. 8,500 employees, hybrid cloud strategy).
Responsible for operating, provisioning, and continuously securing business-critical platforms – including a GenAI chat application, a big data/AI platform, and data science workspaces based on Azure Virtual Desktops and VMs. Ownership of Azure DevOps projects for ShaiHulud and React2Shell, as well as BSI alerts – Security Operations improvements across the SDLC.
Deployment responsibility for the GenAI chat application, big data/AI platform (BDAI), and data science workspaces (AVD/VM-based) in the respective landing zones.
Deployment & release management: end-to-end responsibility for deploying portal and service applications across multiple Azure landing zones, including technical approvals, compliance with development team deployment guidelines, and ensuring ITIL-based change and release processes via ServiceNow.
Azure landing zones & network architecture: design, provisioning, and operation of Azure landing zones for 3-tier web applications with enhanced network segmentation, VNet peering, hub-and-spoke architectures, private endpoints, and firewall integration across separate subscriptions and tenants.
Azure DevOps governance & operations: ownership of the Azure DevOps organization, including projects, repositories, and CI/CD pipelines; implementation of governance requirements such as branch policies, approval gates, permission models, and audit-ready operating structures.
Infrastructure as Code (Terraform): design, implementation, and operation of a modular Terraform architecture for standardized cloud infrastructure deployment, including state management, provider versioning, reusability, and policy-as-code approaches.
CI/CD pipeline engineering: design, operation, and optimization of complex YAML-based CI/CD pipelines with multi-stage deployments, template standardization, self-hosted agents, integrated secret management, and automated quality and security checks.
Git migration & platform consolidation: planning and execution of repository and pipeline migration from Azure DevOps to GitLab CI/CD, including automated scripts, full Git history transfer, pipeline porting, and platform consolidation.
Container & platform operations (AKS): operation and security assessment of containerized workloads on Azure Kubernetes Service, centralization of on-premises container registries for ACR.
OpenShift (OCP) security reviews: security assessment of code baselines, build pipelines, and deployment processes for on-premises OpenShift clusters with critical applications, and derivation of specific hardening recommendations.
Shift-left security & DevSecOps transformation: introduction of a company-wide shift-left approach for early security integration in development and deployment processes, enabling developers to perform self-led security checks and sustainably reduce vulnerabilities before production (IDE integrations, pre-commit hooks, local scanners).
Software supply chain security: analysis and mitigation of supply chain risks in NPM- and Yarn-based applications through dependency audits, CI/CD pipeline hardening, token rotation, and restriction of risky build and lifecycle mechanisms.
Frontend & framework security (React / Next.js): security assessment and coordination of critical vulnerability remediation across platform applications and web frameworks, including coordination and complementary technical mitigations with all teams following BSI alerts.
Software composition analysis (SCA): introduction and operation of automated vulnerability scans for container images, pipelines/artifacts, and third-party dependencies, including SBOM exports within CI/CD pipelines.
SAST/DAST integration: design and piloting of static and dynamic application security tests in close collaboration with security architecture and development teams, for continuous improvement of code and runtime security, and establishing operational acceptance tests.
Artifact & registry consolidation: analysis and consolidation of all package and container repositories for service applications and AKS workloads, aiming for a centralized, secured registry strategy with centralized vulnerability scanning and governance.
Dependency-Track & SBOM strategy: advising the compliance board on introducing a central SBOM and vulnerability management platform to increase enterprise-wide dependency transparency and accelerate CVE response capability.
CI/CD pipeline hardening: security analysis and cleanup of the existing pipeline landscape by removing unused pipelines, improving secrets hygiene, implementing least-privilege principles, and isolating build agent environments.
Azure Web Application Firewall (WAF) optimization: analysis and tuning of existing Azure WAF rules (OWASP Top 10 Core Rule Set, DSR/SDC, custom rules) to defend against known vulnerabilities and exploit patterns, including reducing false positives and improving threat detection.
Documentation & stakeholder communication: creating and maintaining technical documentation, runbooks, and architecture overviews in Jira and Confluence, as well as active knowledge transfer between operations, development, security, and compliance stakeholders.
Enrique Gallardo
Last position:
Security Architect at Capgemini
I implemented a Zero-Trust architecture for robust, military-grade maritime container mini data centers based on VMware & Tanzu to support containerized GIS workloads for ground forces. The main focus was on securing communications, workload protection, and data access in contested electronic battle environments affected by jamming, interception, signal manipulation, and constantly changing operational conditions. I designed and architected use cases so that every element of workload, identity, and system could continue to operate independently and securely even in degraded or disrupted scenarios. In parallel, I defined the enterprise and solution security architecture with LeanIX, Bizzdesign, and HOPEX as enterprise architecture, repository, and governance platforms to maintain architecture inventory, relationships, traceability, target pictures, and security governance in complex environments. For the architectural designs, I used Sparx Enterprise Architect to describe formal architecture views, interfaces, trust boundaries, and system architecture in both IT and OT environments. IriusRisk was used for threat modeling of the solution to identify architecture-driven risks, derive security requirements, and detect countermeasures and design gaps directly from the solution models. Risk and compliance management was supported with Archer. Architecture decisions, control gaps, and operational risks were translated into controlled governance and auditable compliance measures. For documentation, collaboration, and visual design, I used Confluence to maintain Architecture Decision Records, Security Blueprints, and workflows. I used Lucidchart and draw.io to create design artifacts tailored to stakeholders. I also defined OT security concepts with support from electrical and mechanical engineers in the areas of oil, vehicle onboard systems, rail, power plants, pharma, gas turbines, and nuclear technology. I created the end-to-end OT security strategy, starting with global policy, developed into standards and procedures, and finally aligned with Bell-LaPadula, Purdue Model, SABSA, TOGAF ADM, CENELEC 50701, IEC 62443, and NIST standards. In addition, I worked with engineering team leads to identify critical KBP assets and place them under protective measures that segmented SCADA, PLC, and HMI assets. I drove collaboration between Security, IT, and OT teams to create standardized workflows and use cases for the OT security solution catalog, while integrating Defense-in-Depth and Zero-Trust principles into operational environments. A key part of my work was integrating multidisciplinary engineering, security, and operations stakeholders into a unified security blueprinting strategy and ensuring that architecture, threat modeling, governance, and documentation were technically strong and operationally practical.
Tobias Engelbrecht
Last position:
C# Fullstack Developer / Scrum Master / Product Owner Cloud Services / Product Owner Infrastructure & Core Services / Head of at TRUMPF Werkzeugmaschinen SE & Co. KG
- Many years of work in various roles within the MES product area, with technical development, agile leadership and strategic product responsibility for key MES components.
- As C# Fullstack Developer / Scrum Master (2018–2020): further development of a programming system for laser machines, introduction and facilitation of Scrum processes, quality assurance through automated tests and documentation.
- As Product Owner Cloud Services (2019–2020): led two AWS-based cloud services for providing laser data and legal documents, defined the product vision, managed the backlog and communicated with stakeholders.
- As Product Owner Infrastructure & Core Services / Head of DevOps / Product Security (2020–2025): responsible for core MES components such as Service Orchestrator, Licensing Service, IAM and AppLauncher, building and maintaining Azure DevOps pipelines for over 70 components, and introducing security standards (CRA).
- Company-wide point of contact for Azure DevOps and majorly responsible for its implementation.
- Standardized versioning of all components.
- Structuring CI/CD and release pipelines.
- Building an agent scale set with a custom software configuration.
- Integrating Azure DevOps with ServiceNow.
- Standardized integration of security tools like SonarCloud, Dependency Track and digital signing.
- Technologies & tools: .NET (C#, 4.8 / Core 3.x / 8), WPF, WCF, REST, OData, JSON, DevExpress, Duende IDP, Azure DevOps, AWS, Power BI, SonarCloud, Dependency Track, Visual Studio Pro.
- Methods: Scrum.
- Project language: German / English.
Nils Klawitter
Last position:
Vulnerability Management and Secure SDLC at DB InfraGO AG
- Successfully implemented vulnerability management with DefectDojo
- Advised on and implemented technical and procedural aspects of vulnerability management with DefectDojo
- Provided guidance on implementing a secure software development lifecycle
- Skills: GitLab, DefectDojo, Vulnerability Management, SCA, SAST, DAST, Python, Kubernetes, Argo CD, Docker, AWS, Azure, WhiteSource/Mend, Greenbone
Mirko Haucke
Last position:
Cybersecurity Manager at Joynext GmbH
Cybersecurity for RTCU project for the Stellantis Group.
The management of cybersecurity was strongly criticized by the customer Stellantis, questioning competence. Requirements were missing or incomplete, the architecture for cybersecurity controls was non-existent, and documentation such as cybersecurity plans and concepts were incomplete and formally incorrect.
- Building customer trust and de-escalation
- Sprint planning with the customer based on SAFe
- Task-force management
- Switching planning and control to an agile approach
- Review and update of cybersecurity documents
- Communication and problem solving with suppliers, particularly Rolling Wireless and Autocrypt
- Internal workshops and coordination across various hierarchy levels from developers to CTO
- Coordination of work packages and implementation across locations in Dresden, Ningbo, and Oborniki
- Reporting and support of cybersecurity audits
- Coaching of Joynext cybersecurity managers
- De-escalation of critical customer issues
- Acceleration of requirement creation and release by a factor of 5
- Timely provision of 3rd party components
- Reduction of vulnerability management effort by factor 3
- Creation of cybersecurity documents conformant to existing standards
- Technologies and Methods: V-Modell, ASPICE, IREB, ISTQB, Scrum, Kanban, SAFe, PMP, IPMA, BPMN 2.0, Microsoft Office, Microsoft Project, Jira, Confluence, Siemens Polarion, Dependency Track
Discover over 15,000 top freelancers
Statistics of experts using Dependency-Track
Aggregated from the professional profiles of matched freelancers.
Experience
18 years
Position duration
2.3 years
Positions per freelancer
13
Top business areas
Information Technology, Project Management, Product Development
Top industries
Information Technology, Manufacturing, Energy
Certification focus areas
Information Technology, Product Development, Project Management
Bachelor's degree or higher
80%
Master's degree or higher
60%
Certifications per freelancer
11
Most common languages
German, English, Spanish
Speak two or more languages
100%
Based on our profile pool as of 30 Aug 2026.
Daily rate distribution
The chart shows how the daily rates of freelancers in this technology in Germany are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows how many freelancers charge within that range.
Average rates of experts in Germany using Dependency-Track
Rates are based on recent contracts and do not include FRATCH margin.
The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.
The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.
Calculated based on our freelancers’ daily rates as of 30 Aug 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
About the technology
What it does
Dependency-Track is used to track software components and their risk after a system is built. It helps teams follow SBOMs, monitor known vulnerabilities, and see where third-party packages affect a product. Many teams know it as OWASP Dependency-Track.
Common use cases
- Import SBOMs from build and release pipelines
- Monitor vulnerable libraries across products and services
- Set policy rules for approved or blocked components
- Review exposure for open source and vendor packages
- Produce audit evidence for security and compliance work
Ecosystem and setup
Strong specialists connect Dependency-Track with the tools that create SBOMs, scan builds, and send alerts. They work with formats and workflows around CycloneDX, CI/CD systems, API integrations, and reporting. In Germany, this often fits product teams that need clear supply-chain visibility across distributed delivery setups.
When to bring in help
Companies bring in freelance expertise when they need a clean rollout, not just a server install. Typical signs are messy SBOM data, weak policy design, unclear ownership, or too many false alerts.
- You need the first setup or a redesign
- Your pipeline produces SBOMs but no useful tracking
- Your teams need better risk triage and reporting
- You want integration support without slowing delivery
What good experts do
Good Dependency-Track professionals understand software supply-chain risk, not only the user interface. They can map component sources, design practical policies, and explain findings to security, platform, and product teams in plain language. They also know when to automate and when to keep a manual review step.
Delivery in practice
Projects often focus on making risk data usable in daily work. That can include build integration, notification routing, dashboard cleanup, and documentation for internal teams.
- SBOM intake and normalization
- Policy and workflow design
- Release and audit reporting
- Support for handover and training
Frequently asked questions
Questions about Dependency-Track? Start with the answers below.
Dependency-Track is used to follow software components after they enter a product. Teams use it to ingest SBOMs, track known vulnerabilities, and keep an eye on supply-chain risk across releases. It is most useful when many services share libraries and the ownership is spread across teams.
Dependency-Track is not just another scanner. It focuses on component intelligence over time, policy evaluation, and SBOM-driven visibility, while scanners usually focus on detecting issues in a codebase or container at a point in time. Many teams use both because they solve different parts of the risk problem.
The most common name is Dependency-Track, and many people refer to it as OWASP Dependency-Track. In conversation you may also hear DTrack, but the official product name is the one to use in project briefs and handover notes. Search terms usually center on the full name rather than a long list of variants.
A strong Dependency-Track specialist usually knows SBOM formats, CI/CD tooling, and software supply-chain security. They should also be comfortable with API-based integrations, alert routing, policy rules, and reporting for security or compliance teams. Clear communication matters because the tool often sits between platform, security, and product groups.
A small proof of concept with Dependency-Track can be handled by someone who has set it up before and understands SBOM flow. A larger rollout needs deeper experience with integration design, data quality, policy tuning, and stakeholder adoption. The harder the reporting and governance requirements, the more senior the specialist should be.
Yes, Dependency-Track work is often done remotely because setup, integration, and policy design can be shared online. For teams in Germany, remote collaboration works well when security and platform stakeholders can review workflows in regular sessions. On-site time is mainly useful for kick-off workshops, sensitive environments, or faster alignment on ownership.
A good Dependency-Track deliverable has clean SBOM intake, meaningful policies, and alerts that help people act quickly. Look for clear documentation, sensible thresholds, and integration that fits existing release processes instead of adding noise. The best work makes risk visible without overwhelming the team.
Dependency-Track is often paired with SBOM generation, source control workflows, build pipelines, and security review processes. Teams may also connect it with notification systems, issue trackers, and dashboards used for release governance. The best specialists know how to fit the tool into the wider software supply-chain process.
The average hourly rate of freelancers in Germany who have used Dependency-Track in their recent projects is 107 €, which corresponds to a daily rate of about 853 € based on an 8-hour working day.
Of the freelancers in Germany who have used Dependency-Track in their recent projects, 80% hold at least a Bachelor's degree and 60% hold at least a Master's degree.
On average, freelancers in Germany who have used Dependency-Track in their recent projects have 18 years of professional experience, with a single engagement typically lasting around 2.3 years.
The most common languages among freelancers in Germany who have used Dependency-Track in their recent projects are German (100%), English (100%), and Spanish (33%).
The most common industries among freelancers in Germany who have used Dependency-Track in their recent projects are Information Technology (100%), Manufacturing (100%), and Energy (50%).
The most common business areas among freelancers in Germany who have used Dependency-Track in their recent projects are Information Technology (100%), Project Management (100%), and Product Development (83%).
Main locations of FRATCH Experts, who have recently used Dependency-Track
Our freelancers and interim experts are at home across the DACH region — available on-site in the major business hubs or fully remote. Choose a location to discover matched specialists, local market insights and up-to-date availability.
Request a free demo
Get in touch with the FRATCH team and we will get back to you within 4 hours.
Would you rather directly get in touch?
We always have the time for a call or email!
