Saltar al contenido principal

Security Scanner Bundles

Plexicus ships 11 security scanner bundles plus connectors for external enterprise tools. This guide explains what each bundle detects, how to configure it, and how severity levels behave across bundles.

Scanner Bundles Overview​

Each bundle packages one or more specialized detection engines behind a single, product-managed capability. Select which bundles to enable when creating or updating an application. In the Plan column, "Scale+" means the Scale plan and above; see Plans & Entitlements.

BundleDetectsPlan
plexicus-sastCode vulnerabilities, injection flaws, unsafe patterns — with dataflow tracing and Python-specialized checks. Includes Deep Code Analysis (Scale and above)All plans
plexicus-scaVulnerable dependencies across all major package managers, cross-referenced against CVE databases (NVD, GitHub Security Advisory)All plans
plexicus-secretsHardcoded credentials, API keys, and tokens — in the working tree and across Git history, with live verification against issuing servicesAll plans
plexicus-containerMisconfigurations in Dockerfiles, Kubernetes manifests, and config files (CIS benchmarks)Scale+
plexicus-iacInfrastructure-as-Code policy violations across Terraform, CloudFormation, Kubernetes, Helm, Ansible, ARMAll plans
plexicus-cicdCI/CD pipeline misconfigurations (GitHub Actions, GitLab CI, Azure Pipelines)Scale+
plexicus-sbomSoftware Bill of Materials (SBOM) generation in CycloneDX/SPDXScale+
plexicus-aibomAI Model Bill of Materials (AIBOM): ML models, training datasets, model cardsScale+
plexicus-cbomCryptographic Bill of Materials (CBOM): algorithms, key sizes, quantum-readiness (NIST 2030/2035)Scale+
plexicus-licenseLicense compliance: copyleft, proprietary, or unknown licenses across dependenciesScale+
plexicus-scmSupply-chain posture and SLSA compliance: signed commits, artifact provenance, build hardeningScale+

External Tool Integrations​

Plexicus ingests results from external enterprise security tools alongside its own bundles:

ToolPurposeIntegration
Black Duck (Synopsys)Commercial SCA & license analysisJSON report upload (Findings › Upload Scan), or API during a scan — see Black Duck
Checkmarx (Checkmarx One)SAST + IaCAPI ingestion
Fortify (OpenText)SASTAPI ingestion
CodeQLGitHub code-scanning alert ingestionGitHub webhook ingestion
SemgrepSemgrep AppSec Platform findingsAPI token

Parameter Configuration​

Canonical Parameters​

Three parameters are available on most bundles and are translated automatically to each engine's native options:

  • Severity · Minimum severity level to report (info, low, medium, high, critical)
  • Exclude Paths · Filesystem patterns to skip (e.g., node_modules/, test/)
  • Severity Filter · Post-scan filtering for engines without a native severity option

Advanced Bundle Parameters​

Bundles expose additional parameters for fine-grained control:

plexicus-sast:

  • config · Custom rule configuration
  • baseline_commit · Differential scanning (only new issues since a commit)
  • dataflow_traces · Enable taint tracking
  • exclude_rule · Disable specific rules
  • max_lines_per_finding, timeout, max_target_bytes, exclude_minified_files, strict · Output and performance tuning
  • Python-specific: tests / skips (check IDs to run or skip), confidence_level, ignore_nosec

plexicus-sca:

  • fail_on · Exit with an error code when vulnerabilities are found
  • only_fixed / only_notfixed · Filter to fixed/unfixed CVEs
  • by_cve · Group results by CVE instead of package
  • scope · Container layer scope (squashed vs. all-layers)
  • distro · OS distribution hint (Alpine, Debian, …)

plexicus-container / plexicus-license:

  • ignore_unfixed · Skip vulnerabilities without an available patch
  • include_dev_deps · Include development dependencies
  • pkg_types · Package-type filter (jar, wheel, npm, …)
  • offline_scan · Run without internet access
  • detection_priority · Detection algorithm selection

plexicus-iac / plexicus-cicd:

  • check · Run only specific policy checks (e.g., CKV_TF_1, CKV_AWS_8)
  • skip_check · Disable specific checks
  • skip_framework · Skip entire frameworks (e.g., terraform, kubernetes)
  • soft_fail · Report violations without failing the scan

plexicus-secrets:

  • redact · Redact secret values in output
  • no_verification · Skip live verification against issuing services
  • include_detectors / exclude_detectors · Detector selection

plexicus-sbom:

  • enrich · Package enrichment (all, golang, java, javascript)
  • scope · Image layer handling (squashed, all-layers, deep-squashed)

Severity Behavior per Bundle​

info

Not every engine has native severity filtering. Where an engine lacks it, Plexicus collects all findings first and filters server-side — nothing is missed during collection, at the cost of slightly longer scans.

BundleSeverity handling
plexicus-sastNative. Canonical levels map onto each engine's own scale (three-level and four-level engines); critical maps to the engine's highest level.
plexicus-container / licenseNative five-level scale — canonical levels map 1:1 (with info treated as the lowest level).
plexicus-scaPost-scan filtering (use fail_on for exit-code gating).
plexicus-secretsPost-scan filtering.
plexicus-sbom / aibom / cbomNot applicable — BOM bundles catalog components rather than grade findings.
plexicus-iac / cicdConfig-based check selection instead of severity flags.

What this means: if you set severity: "high" on a bundle with post-scan filtering, Plexicus collects everything and filters to high/critical in the dashboard.

Exclude Paths Support​

BundleExclude paths
plexicus-sast✓ (glob patterns, e.g. node_modules/, *.test.js)
plexicus-sca✓
plexicus-container / license✓ (directory skips, e.g. test/, .git/)
plexicus-iac / cicd✓
plexicus-sbom✓
plexicus-secrets✗ (scope via repository structure)
plexicus-scm / aibom / cbom✗

Per-Bundle Parameter Support​

BundleSeverityExclude PathsAdvanced Params
plexicus-sast✓✓✓
plexicus-sca✗✓✓
plexicus-secrets✗✗✓
plexicus-container✓✓✓
plexicus-iac✗✓✓
plexicus-cicd✗✓✓
plexicus-sbom✗✓✓
plexicus-aibom✗✗—
plexicus-cbom✗✗—
plexicus-license✗✓—
plexicus-scm✗✗—

Bundle Selection Guide​

For Python Projects​

Enable plexicus-sast + plexicus-sca + plexicus-secrets. If your code handles cryptography: add plexicus-cbom.

For Node.js / JavaScript​

Enable plexicus-sast + plexicus-sca + plexicus-secrets. For monorepos with Kubernetes manifests: add plexicus-iac.

For Infrastructure-as-Code (Terraform, CloudFormation, Helm)​

Enable plexicus-iac to scan the Terraform, CloudFormation and Helm definitions in the repository.

For Dockerfiles and Container Images​

Enable plexicus-container for the Dockerfiles and images declared in the repository, plus plexicus-license for license compliance.

For CI/CD Pipelines (GitHub Actions, GitLab CI, etc.)​

Enable plexicus-cicd to audit workflow definitions for security misconfigurations.

For APIs & Web Applications​

Create an AI Pentest (Nexus) assessment against the running application. Dynamic testing is not a repository scan bundle.

For Bill of Materials & Compliance​

Enable plexicus-sbom for dependency inventory. Add plexicus-cbom for cryptographic assets, plexicus-aibom for ML models, plexicus-license for license risk, and plexicus-scm for supply-chain posture.

See Also​