
Closed
Posted
Paid on delivery
We’re looking for an experienced GitLab security/DevSecOps reviewer to assess one private software project before controlled human testing. We need a practical review of the project’s CI/CD configuration and the controls actually in effect. Existing configuration, test evidence and review notes will be provided privately once the scope is agreed. Scope: - Project permissions and relevant inherited group controls - Protected branches, merge permissions, approvals and possible bypasses - Runner isolation, job trust boundaries and execution permissions - CI/CD variables, secrets, token permissions and exposure risks - Artifact access, retention and unintended data exposure - Dependencies or security checks within the pipeline, including gaps in the existing evidence Recommendations should work with GitLab Free wherever possible. Clearly identify anything requiring a paid tier. Distinguish controls verified from actual settings or evidence from controls that could not be verified. Deliverables: - A written report identifying the configuration/version and settings reviewed - Prioritised findings with severity, supporting evidence and practical remediation steps - A clear summary of verified controls, unresolved risks and exclusions - One clarification round and a clearly bounded recheck of agreed fixes Please include in your proposal: 1. Your hands-on GitLab security-review experience, ideally three years or more, with examples of controls you have assessed. 2. A redacted sample report or equivalent evidence of your own review work. Relevant certifications are welcome alongside practical examples. 3. Who will personally perform the review and whether you use subcontractors or external AI services. 4. Your fixed-price quote, scope limits and availability. Ideally we’d like delivery within 2–3 days of agreeing the scope and receiving the materials; please confirm what is realistic. The review starts read-only using agreed, least-privilege access or owner-supplied evidence. Changes, pipeline runs and active tests require separate approval. Confidential materials must not be uploaded to external services or shared with others without approval. We are also seeking a Python application security review. If you have demonstrable experience in both areas, please provide separate prices and an optional combined fixed-price quote, with evidence of your Python security-review experience.
Project ID: 40775864
69 proposals
Remote project
Active 5 days ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
69 freelancers are bidding on average £167 GBP for this job

Hi there, I noticed you're seeking a thorough assessment of your GitLab CI/CD configuration. With over three years of hands-on GitLab security review experience, I can effectively evaluate permissions, runner isolation, and any potential exposure risks associated with CI/CD variables and tokens. I'll ensure that all recommendations align with GitLab Free tiers wherever possible and distinctly identify any areas requiring paid features. I will conduct a detailed review and deliver a report prioritizing findings along with actionable remediation steps. Let's ensure a smooth review process with agreed least-privilege access, and I'm available to initiate this within 2–3 days upon confirming the scope. Please share any existing configurations to start. Looking forward to your response. Regards, Ali
£20 GBP in 1 day
3.8
3.8

Hello, I can review your GitLab project’s security controls in read-only mode, covering project and inherited permissions, protected branches, merge approvals, runner isolation, CI/CD secrets and tokens, artifact access, and pipeline security checks. I’ll document verified settings separately from unverified assumptions, prioritise findings by severity, and recommend practical fixes compatible with GitLab Free wherever possible. You’ll receive a version-specific report with supporting evidence, remediation steps, exclusions, and one clarification round plus a bounded recheck of agreed fixes. I’ll work within your confidentiality requirements and won’t run pipelines or change settings without approval. Best regards, Inam
£127 GBP in 1 day
2.2
2.2

Hi there - I'd genuinely enjoy this one. You'll get a detailed report that identifies the CI/CD configuration and settings reviewed, along with prioritized findings that include severity and practical remediation steps. I'll ensure all aspects, from project permissions to runner isolation, are thoroughly evaluated for security gaps. Talk soon, hopefully. Thanks for putting this out there!
£200 GBP in 6 days
0.0
0.0

Hi there, The key risk is that GitLab permissions, protected branches, runners, variables, artifacts, and inherited controls may appear secure while effective settings or evidence leave bypasses and exposure paths. I have strong hands-on experience with GitLab security review, DevSecOps, Python, and DevOps, including CI/CD trust boundaries, least-privilege access, secrets handling, protected branch controls, runner isolation, dependency checks, and artifact exposure. My approach would be to: * Review the existing GitLab configuration, project evidence, CI/CD files, inherited group controls, and relevant version or tier limitations. * Identify the root cause of any bypass, excessive permission, secret exposure, runner risk, artifact issue, or evidence gap. * Implement a clean, maintainable review report using risk-ranked findings, supporting evidence, exclusions, and practical GitLab Free-compatible remediation. * Test edge cases, reliability, security, approval behavior, token scope, variable exposure, and integration behavior through read-only evidence unless separately approved. * Deploy or integrate the fix without disrupting the existing system, then perform one clearly bounded recheck of agreed fixes. Effective GitLab security depends on distinguishing configured controls from inherited and actually enforced controls; I will document that distinction explicitly and flag paid-tier dependencies. I prefer fixing the actual root cause rather than applying temporary pat
£250 GBP in 3 days
0.0
0.0

your private gitlab project needs a review that keeps verified controls apart from the ones nobody could check i can do this review for you, working read-only from the access or evidence you supply i'll stay on it through the clarification round and the recheck until the fixes are settled - gitlab experience: i can assess permissions, protected branches, runners, variables and artifacts, the areas you listed - sample report: the report names the version and settings reviewed, with verified controls split from unverified ones - reviewer: me personally, and nothing confidential goes to outside services or anyone else without your approval - quote: £120 fixed, 7 days from agreed scope and materials, open to your budget and happy to agree details in chat is the project on hosted gitlab or a self-managed install, and which version? send the scope over when it's ready Sela
£120 GBP in 7 days
0.0
0.0

Hello There! I hope you're doing well! I’d love to help review your GitLab project’s security posture before controlled human testing. My approach is to assess project permissions, protected branches, approval rules, runner isolation, CI/CD variables, token scopes, artifact access, and pipeline security checks. I’ll document verified controls separately from unverified settings, prioritise findings by severity, and provide practical remediation steps compatible with GitLab Free wherever possible. I’ll also define clear scope limits, complete one clarification round, and recheck agreed fixes with separate approval for any changes or active testing. My skills in Python, Git, Linux, Docker, and software architecture make me confident I can deliver exceptional results. I have a few questions: 1. Which GitLab version and tier are you using? 2. Can you provide a redacted sample report? 3. Is the Python review required in the same engagement? I’ll clarify pricing, review boundaries, and confidentiality arrangements before starting. Looking forward to hearing from you. Best Regards, Touhidul Islam
£60 GBP in 3 days
0.0
0.0

You want a practical, read-only review of your GitLab CI/CD configuration, permissions, secret hygiene, and pipeline trust boundaries before human testing starts. How I work: testing starts only after written authorisation and proof that the target is yours, with the scope agreed in one page. I personally perform every review — no subcontractors, no external AI upload of your confidential materials. I assess project permissions, protected branches, runner isolation, variable and token exposure, artifact access, and pipeline security gaps against GitLab Free capabilities where possible, distinguishing verified settings from unverified ones. What you receive within 3 days: - A written report with configuration details, prioritised findings (severity, evidence, remediation), and clear exclusions. - A summary of verified controls and unresolved risks. - One clarification round and a clearly bounded recheck of agreed fixes. I run a production Node.js/MongoDB platform myself, manage its Linux/Cloudflare/Nginx/PM2 deployment, and built my own scope-gated web audit and SAST pipelines (Python) with tamper-evident SHA-256 evidence chains. I do not use subcontractors or third-party AI for client code. Two questions: - Will you provide read-only repository access or an exported configuration package for the initial review? - Are you also interested in the optional Python application security review mentioned in your brief?
£200 GBP in 3 days
0.0
0.0

The biggest challenge was separating real protections from settings that only appeared secure. I solved this by auditing protected branches, approval rules, runner tags, token scopes, artifact visibility, and inherited group permissions. I then documented each finding with evidence, severity, and a practical fix. For your project, I will perform a read-only review of permissions, branch protection, merge approvals, runners, variables, secrets, artifacts, and pipeline security checks. I will clearly mark verified controls, unresolved risks, and any features requiring a paid GitLab tier. You will receive a prioritized report, remediation steps, one clarification round, and a bounded recheck of agreed fixes. Q1 : Can you share the GitLab project path and confirm whether group-level settings are also in scope? Q2 : Should I include the Python application security review, or focus only on GitLab CI/CD? I will personally perform the review using least-privilege access, with no subcontractors or external AI services. Looking forward to your reply.
£200 GBP in 1 day
0.0
0.0

Hi, We can review your GitLab project’s security configuration, covering permissions, protected branches, runner isolation, secrets, token access, artifacts, and CI/CD security checks. You’ll receive a prioritised report with supporting evidence, practical fixes, verified controls, unresolved risks, and any recommendations requiring a paid GitLab tier. The review will begin read only, with no changes or pipeline runs without separate approval. We can confirm the fixed price and 23 day turnaround once the scope and evidence requirements are clear. We would also clarify the reviewer’s experience, report sample, and confidentiality arrangements before proceeding. Could you confirm whether inherited group settings are included alongside the individual project configuration? Best regards, The 4 Loop
£100 GBP in 7 days
0.0
0.0

Your goal is absolute certainty that your CI/CD pipeline is locked down and no secrets are exposed before human testing begins. I will provide a rigorous security audit of your GitLab configuration and a deep-dive Python application security review to ensure no critical vulnerabilities reach your testing phase. I will handle the entire process as a Done-For-You service: 1. Complete audit of project/group permissions, protected branches, and Runner isolation boundaries. 2. Exhaustive review of CI/CD variables and token exposure risks, specifically optimizing for GitLab Free constraints. 3. Dedicated Python security review to identify vulnerabilities in the application logic and dependencies. 4. Delivery of a prioritized report with severity levels and actionable remediation steps. You will receive an initial "Critical Findings" brief within 24 hours of access, so you can address the most urgent risks immediately. I perform all reviews manually—no external AI services or unauthorized third-party uploads will be used, guaranteeing total confidentiality. I have extensive experience securing Python-based automation and CI/CD workflows. Let's align on the scope and I can start the rea
£450 GBP in 4 days
0.0
0.0

Hello I checked your project and the main point is an independent, read-only GitLab security and CI/CD review covering permissions, protected branches, runners, variables, tokens, artifacts, dependencies, and evidence gaps. I have hands-on experience reviewing Python and Django applications, CI/CD workflows, access controls, secrets handling, and security-sensitive integrations. However, I don’t want to overstate a specific GitLab certification or review history that I cannot document. I would review the supplied settings and evidence against GitLab Free capabilities, clearly separate verified controls from assumptions, and provide prioritised findings with practical remediation steps. The report would also include scope limits, unresolved risks, a clarification round, and a bounded recheck of approved fixes. I will personally perform the review without subcontractors, and I will not upload confidential materials to external AI services. Could you confirm whether a redacted prior GitLab review sample is mandatory, and whether you also want a separate Python application security review and combined fixed-price option? Best regards
£135 GBP in 3 days
0.0
0.0

Your GitLab controls need evidence-based verification before human testing, not a checklist-only review. We will inspect inherited permissions, protected branches, approval bypasses, runner trust, secrets, tokens, artifacts, and pipeline dependencies using read-only, least-privilege access. Findings will separate verified controls from unresolved risks, identify GitLab Free versus paid-tier remedies, and include severity, evidence, remediation, one clarification round, and a bounded recheck. Leonhard will personally conduct the review without subcontractors or external Artificial Intelligence services. Confidential material stays within the approved environment. Our Web Security assessment can also cover Python application risks, including dependency and pipeline concerns affecting Typescript components where relevant. A redacted sample, fixed scope, separate Python price, combined option, and realistic availability can be discussed before access. Which outcome matters most for this review: validating release readiness, reducing pipeline compromise risk, or establishing an auditable security baseline? Best regards, **TomorrowBits GmbH**
£550 GBP in 5 days
0.0
0.0

Hello, The main challenge is verifying which GitLab security controls actually prevent unauthorized changes, rather than relying on settings that appear secure but allow bypasses. I'd begin with a read-only review of project permissions, inherited group policies, protected branches, merge approvals and pipeline execution rights. I'd then examine runner isolation, CI/CD variable exposure, token scopes, artifact permissions and retention, plus dependency and security checks in the pipeline. A key focus would be identifying privilege escalation paths, including whether developers or runners can access protected secrets or bypass intended approval controls. My report would document the GitLab version, verified settings, evidence gaps, prioritized findings, severity and actionable remediation, favoring GitLab Free and clearly identifying paid-tier dependencies. I'd personally handle the assessment, keeping confidential materials out of external AI services and away from subcontractors without approval. Any active testing, pipeline execution or configuration changes would require separate authorization. I'd also include one clarification round and a focused recheck of agreed fixes. I can provide an illustrative report format, although it would not substitute for verified evidence of previous client audits. Will the review include read-only access to parent-group settings, or only project-level evidence? Best regards, nicolas
£80 GBP in 5 days
0.0
0.0

I can deliver 'Independent GitLab Security and CI/CD Review for One Private Project' end to end — clean architecture, tests, and deployment. I'll start with a short plan, share progress daily, and hand over production-ready code. Could you confirm your timeline and must-have features so I can lock the scope?
£163.92 GBP in 7 days
0.0
0.0

Hi, we have experience with software security reviews, CI/CD workflows, access controls, and secrets management. We can review your GitLab configuration, runner permissions, protected branches, pipeline variables, and artifact access, then provide an evidence-based report with prioritized risks and practical fixes. We can also assess the Python application separately if you share its scope and requirements.
£135 GBP in 7 days
0.0
0.0

Your pre-testing audit requires verifying actual enforcement across pipeline trust boundaries, not just reviewing static YAML. I will audit your inherited group policies, branch approval bypass risks, shared/specific runner isolation, masked variable leakage vectors, and artifact token exposure. My approach: I will map your existing configuration against active execution evidence to separate fully verified controls from untestable assumptions. Gaps in pipeline dependency scanning and secret exposure will be flagged with hardened remediations prioritized for GitLab Free tier, clearly isolating any controls that strictly require Ultimate/Premium tiers. The final handoff will include a practical assessment matrix and actionable remediation steps. Are your CI/CD jobs executing on shared GitLab-hosted runners or self-managed infrastructure? Are environment-scoped secrets and deployment tokens currently used in this repository? I am ready to review the configuration notes and deliver an audit that ensures zero pipeline bypasses.
£98 GBP in 5 days
0.0
0.0

Hi, I am a devops security engineer with 8 years of rich experience in software development, with a background in GitLab CI/CD reviews. I'd start read-only from your evidence, checking protected branch and approval bypasses, runner trust boundaries, masked and protected variables, token scopes and artifact expiry, then mark each control as verified or unverified and flag anything that needs a paid tier. I'll do the whole review myself with no subcontractors, keep your materials off external AI services, and can deliver the report within 2 days of getting the materials. I am familiar with GitLab CI/CD, GitLab Runner, Docker, Linux, Bash, Python, Semgrep, Trivy, Gitleaks and OWASP. I'm an individual freelancer and can work on any time zone you want. Please contact me with the best time for you to have a quick chat. Looking forward to discussing more details. Thanks. Emile.
£250 GBP in 7 days
0.0
0.0

Hi, Fernando here, from Mexico. Setting up the independent GitLab security and CI/CD review for your one private project is doable; what matters most is deploys you can repeat and roll back, with no surprise downtime. I'm a senior cloud and DevOps engineer with 12+ years of experience working with CI/CD and Python. For the independent GitLab security and CI/CD review, the real challenge is environment differences and secrets. A common issue: no rollback plan, so a bad release means downtime while someone fixes it live. My plan: first, audit the current setup, secrets and backups. Then, script the build and deploy pipeline, with a staging step first. Finally, test a rollback and a restore from backup before handover. The price and timeline are in the bid details. I've done deployment work in Python, so I check early for secrets in code and untested backups. A few questions to better understand the scope: 1. Can the database schema change in a deploy? Schema changes need a rollback path first. 2. Deploy to a staging copy before production? I'd recommend it, check releases before users do. 3. Are your users spread across time zones? Then zero-downtime deploys matter a lot more. I can start right away. Happy to go over the details here in chat and suggest the best approach. Looking forward to hearing from you, Fernando
£135 GBP in 2 days
0.0
0.0

Hi there, Hi there, Over the past three years, I've performed comprehensive evaluations of various controls, including permissions and configurations, protected branches and merge permissions, runner isolation, CI/CD variables, artifact access and many more—all of which align seamlessly with your project scope. Best regards, Mobasher Reza
£135 GBP in 3 days
0.0
0.0

GitLab Security Review =====$ Hi, Aleksandar here from Serbia $===== Your GitLab review only works if effective controls are separated from what configuration appears to enforce. I’ll focus on evidence, inherited permissions and real bypass paths. I noticed you need runner isolation, protected branches, variables, artifacts and approvals checked against actual evidence, so I’d trace each control and clearly mark verified, unverified and excluded areas. I would deliver a focused GitLab DevSecOps review with prioritised findings, evidence and practical remediation steps. I’ve built similar security-focused systems. Which GitLab version and subscription tier is the project currently using? Let’s connect over a chat so we can discuss the scope, access boundaries and review approach in more detail..
£100 GBP in 1 day
0.0
0.0

Middlesbrough, United Kingdom
Payment method verified
Member since Oct 19, 2026
£20-250 GBP
$250-750 USD
$30-250 USD
$250-750 USD
$30-250 USD
₹12500-37500 INR
$15-25 USD / hour
$30-250 USD
$30-250 USD
$15-25 USD / hour
€8-30 EUR
₹12500-37500 INR
₹600-1500 INR
₹750-1250 INR / hour
₹100-400 INR / hour
$750-1500 USD
₹1500-12500 INR
$15-25 USD / hour
₹600-1500 INR
₹1500-12500 INR
$250-750 USD