TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Client-side Code Protection

1 post · Jun 2021

What this trail covers

GitLab is enhancing its DevSecOps platform with client-side code protection capabilities, integrating with third-party tools like Jscrambler to provide runtime protection, obfuscation, and anti-tampering measures for JavaScript-based applications. This aims to secure proprietary code, prevent bypasses of app restrictions, and mitigate data exfiltration attacks.

All GitLab trails
  1. How to protect your source code with GitLab and JscramblerThis post introduces the integration of Jscrambler with GitLab CI/CD to protect client-side JavaScript code. It details the importance of runtime code protection against tampering and reverse engineering, outlines prerequisites for the integration, and provides step-by-step instructions for configuring Jscrambler via its web app and CLI within a GitLab CI pipeline. The process involves downloading a JSON configuration file, storing API keys as GitLab environment variables, and defining a new 'protect' stage in `.gitlab-ci.yml` to obfuscate the built application code before deployment. It also demonstrates how to verify the protection by inspecting the obfuscated source code.