Source Code

JFrog’s shift-left approach to security empowers developers to catch and fix issues early, long before software reaches production. By moving security checks to the left of the development timeline — during coding, pull requests, and local builds — teams can detect vulnerabilities, secrets, malware, and license risks when they’re easiest and cheapest to resolve. Tools like the JFrog Security CLI, IDE plugins, and Frogbot make it seamless to integrate security into everyday workflows: scanning code and artifacts locally, surfacing issues directly in the IDE, and automating PR reviews for dependency health.

This guide offers comprehensive instructions and best practices to help secure your software development lifecycle using:

• JFrog Security CLI
• Code security within your IDEs
• Repository scanning with Frogbot

System Requirements

The system requirements for enabling security scans using the JFrog Security CLI, IDE plugins, and Frogbot are:

Linux support is not limited to specific distributions. JFrog Advanced Security scanners, including SAST, run on Linux distributions for these architectures, including Alpine, Debian, Ubuntu, RHEL, CentOS Stream, and Amazon Linux.

Air-Gapped Environments

Air-gapped environments are physically isolated systems disconnected from unsecured networks, used to protect sensitive data from cyber threats, malware, and remote hacking.