Cortex CLI - The Cortex CLI is a unified command-line tool integrating Cloud Workload Protection, API Security, and Code Security scans into a single executable. - Administrator Guide - Cortex CLOUD

Cortex Cloud Posture Management Documentation

Product
Cortex Cloud Application Security > Cortex CLOUD
License
Cloud Posture Management
Creation date
2025-01-22
Last date published
2026-06-10
Category
Administrator Guide
Abstract

The Cortex CLI is a unified command-line tool integrating Cloud Workload Protection, API Security, and Code Security scans into a single executable.

The Cortex CLI is a unified command-line tool that integrates scanning for Cloud Workload Protection (CWP), API Security (WAAS), and Code Security (AppSec). From a single binary, security teams can enforce organizational policies and proactively detect vulnerabilities, misconfigurations, and exposed secrets across source code, container images, and API specifications.

Scope: The Cortex CLI evaluates findings against Unified Application Security Policies and returns structured results with policy correlation, severity breakdowns, and remediation guidance. The Cortex CLI does not create, edit, or delete policies; all policy management operations are performed through the Cortex Cloud tenant or the public API.

Primary use cases

The CLI supports the following primary workflows:

  • Local code development (AppSec): Enable developers to detect hardcoded secrets, IaC misconfigurations, and vulnerable dependencies directly from their terminal before committing code

  • CI/CD automation: Embed security checks into build scripts (such as Jenkins, GitHub Actions) to automatically detect issues and enforce security gates during the build process

  • Container Workloads (CWP): Integrate container scanning directly into CI builds to detect vulnerabilities and malware before images are pushed to production registries

  • API Testing: Evaluate application endpoints for high-risk vulnerabilities and specification leaks as a standard step prior to deployment

Core capabilities

The Cortex CLI consolidates multi-domain security scanning into a single executable tool:

  • Unified scanning engine: Integrates native scanning for Cloud Workload Protection (CWP), API Security, and Code Security. A single set of global flags controls authentication, output format, upload behavior, and error handling across all scan types

  • Code security: Detects hardcoded secrets, Infrastructure-as-Code (IaC) misconfigurations, and open-source dependency vulnerabilities (SCA) directly within developer environments. The SCA scanner generates Software Bills of Materials (SBOMs) for supply chain compliance

  • Container security (CWP): Generates Software Bill of Materials (SBOMs) and detects vulnerabilities or malware in container images before registry push. Container scanning integrates directly into CI builds to prevent vulnerable images from reaching production registries

  • API risk validation: Identifies vulnerabilities, sensitive data leaks, and configuration errors by analyzing OpenAPI and Swagger specifications. API testing validates application endpoints for high-risk vulnerabilities and specification leaks as a standard step prior to deployment

  • Automated security guardrails: Enforces compliance directly within CI/CD pipelines by dynamically blocking deployments that violate organizational security policies

Prerequisites

Before installing and running the Cortex CLI, verify that your environment and account meet the following system and access requirements:

Prerequisite

Description

License

An active Cortex Cloud license with the Application Security add-on for Code Security if required

Permissions

The API key must be associated with a user or role that has CLI Tools permissions:

  • View: grants read-only access (sufficient for --upload-mode no-upload).

    Note

    This role is not supported for CWP, as the CWP system does not support offline mode.

  • View/Edit: grants full access including scan result upload (required for --upload-mode upload and --upload-mode no-code)

Note

There are no preconfigured CLI-specific roles. Add the CLI Tools permission to an existing role or create a dedicated custom role.