Misconfigurations Scans

Learn how JFrog Advanced Security detects misconfigurations in code, services, and libraries.

JFrog Advanced Security goes beyond detecting CVEs, first-party JFrog SAST issues, and exposed secrets. It also identifies security misconfigurations that can leave your applications vulnerable. By scanning for misconfigurations across your infrastructure, services, and applications, JFrog Advanced Security helps you strengthen your security posture early in the development pipeline and ensures compliance at every stage.


Infrastructure as Code Scans

JFrog Advanced Security scans your Terraform files for cloud misconfigurations at different stages of the development pipeline. During development, it scans Terraform modules to catch issues early before deployment. Once the infrastructure is deployed, JFrog Advanced Security scans Terraform state files in JFrog Artifactory so cloud services remain securely configured. It supports cloud services from AWS, Azure, and Google Cloud Platform (GCP).

For step-by-step setup instructions, see How to Scan Terraform State Files for IaC Misconfigurations.

A key differentiator of JFrog Advanced Security is its focus on real security risks in infrastructure as code (IaC) scanning. Unlike common IaC tools that report many low-severity issues with little impact, JFrog Advanced Security provides detailed severity ratings, so you can identify and address actual security risks.

Examples of Detected Infrastructure Misconfigurations

  • Insufficient access restrictions to services, such as public access to repositories, publicly accessible clusters, globally readable, deletable, or writable buckets, admin roles in ECS services, IAM users with privileged access to all resources, and API Gateway methods without authorization
  • Insecure use of credentials, such as hardcoded credentials
  • Allowing weak cryptographic algorithms, such as weak cipher suites
  • Running batches in privileged mode
  • Enforcement of secure communication, such as listening to HTTP and unencrypted communications
  • Wildcard actions in Glue policies
  • Missing logging, for example CloudTrail trails with logging disabled
  • Disabled upgrades, for example an RDS database instance with disabled minor engine upgrades
  • Data at rest encryption enablement for Kinesis streams

Services Configuration Scans

JFrog Advanced Security scans common open-source libraries and services in your containers for misconfigurations, ensuring that services such as web servers, databases, and proxies are securely configured by default. This helps prevent vulnerabilities in essential services.

For Helm and Helm OCI charts, these findings come from the container images the chart deploys, not from the chart's own files. For more information, see Helm and Helm OCI.

Supported Services

  • Envoy
  • etcd
  • Prometheus
  • NGINX
  • Apache

Examples of Detected Service Misconfigurations

  • Insecure use of credentials, such as an NGINX credential in a configuration file or a credential stored insecurely
  • Enforcement of secure communication, such as redirecting HTTP to HTTPS, enforcing TLS, and the TLS version
  • Allowing weak cryptographic algorithms
  • Externally exposing the Admin interface
  • Unauthenticated access to resources

Application Library Misuse

JFrog Advanced Security detects misconfigurations and insecure usage of libraries and services within your containers. Supporting Python and Node.js, JFrog Advanced Security scans for issues like excessive privileges, insecure communication, and unsafe cryptographic operations.

For Helm and Helm OCI charts, these findings come from the container images the chart deploys, not from the chart's own files.

Examples of Detected Application Issues

  • Insecure use of credentials, such as insecure key storage
  • Enforcement of secure communication, such as redirecting HTTP to HTTPS, enforcing TLS, verifying the TLS certificates of all servers in Python scripts, enforcing the TLS version, and using secure HTTP headers
  • Use of weak cryptographic keys
  • Throttling Node.js logins to prevent brute-force attacks
  • Invoking Node.js exec functionality with user-provided input

Related Topics


Did this page help you?