devsecops-radar 0.4.2

Unified CI/CD Security Dashboard — Pipeline Sentinel

🛡️ Pipeline Sentinel

The Open‑Source DevSecOps Command Center — Unify, Analyse, Remediate.

📖 Read this in: Русский | 中文 | العربية

Severity doughnut, trend line chart, attack‑path graph (clickable nodes), topology view, executive summary, and attack simulation panel — all fully offline.

---

📑 Table of Contents (Click to expand)

1. What Is Pipeline Sentinel? (Simple Explanation)
2. Why You Need It
3. Where to Run It in Your Network
4. Network Flow & Topology
5. Dashboard Preview
6. Quick Start
7. Prerequisites
8. Installation
9. How to Use (Step‑by‑Step)
10. Complete Command Reference
11. Core Capabilities
12. Community Rules & Online Updates
13. Attack Simulation & What‑If Analysis
14. Security Improvements in v0.4.2
15. Architecture
16. Roadmap
17. Testing & CI
18. Security Policy
19. Contributing
20. Code of Conduct
21. Support Development
22. Author
23. License

---

👨‍👩‍👧 What Is Pipeline Sentinel? (Simple Explanation)

Imagine you have several security guards, each watching a different door of a building. They all shout their findings in different languages, and you have to run around to understand what’s going on.

Pipeline Sentinel puts them all in one room, translates their reports, and shows you a single, clear screen with the full picture. It connects to tools like Trivy (checks your containers), Semgrep (scans your code), Poutine (audits your GitLab pipelines), Zizmor (secures your GitHub Actions), and Gitleaks (finds secrets).

Instead of digging through multiple JSON files, you get a beautiful, dark‑mode command‑center dashboard that tells you what’s critical, how risks are trending, and even how an attacker might chain several small issues into a big problem.

Think of it as a security camera system for your entire CI/CD pipeline — it watches everything, alerts you, suggests fixes, and even lets you simulate attack chains, all without needing internet access if you want.

---

💥 Why You Need It

In 2026, supply chain attacks have become the #1 threat. Tools like Trivy themselves were compromised, and attackers now inject malicious code directly into build pipelines. You can no longer just scan your code; you must scan your pipeline.

Pipeline Sentinel gives you:

• 🎯 Unified Aggregation: One screen for all scanners – stop juggling log files.
• 🧠 Graph AI Insights: AI that understands attack chains – "A leaked secret + an old library = a disaster."
• ⚡ Auto-Remediation: Automatically patches files and opens a pull request (with automated backups) with a single flag.
• 👥 Human Review Mode: Step-by-step interactive interface to inspect each fix before applying it to production.
• 📊 Compliance-Ready Reports: Instantly generate beautiful, executive-ready PDF summaries for auditors or stakeholders.
• ⚔️ Attack Simulation: Select security findings and automatically generate operational proof-of-concept scripts.
• 🔒 Air-Gapped Privacy: 100% offline capable. Perfect for highly restricted environments where data residency is paramount.
• 🧙 Interactive Wizard: A single command leads you through the entire initialization and onboarding process.
• 🛒 Rules Marketplace: Dynamically fetch and update curated detection definitions directly from the community.

---

📍 Where to Run It in Your Network

Pipeline Sentinel is designed to adapt to your setup. You decide where it fits best:

Deployment Mode	Operational Profile & Context
🖥️ Local Dev Machine	Run the CLI and dashboard right on your laptop. Perfect for individual pentesters or developers who want instant, localized feedback.
🔧 CI/CD Runner Pipeline	Integrate directly into Jenkins/GitLab CI or GitHub Actions. Fail builds automatically if critical vulnerabilities exceed your security policy rules.
🏢 Central Security Operations	Deploy via Docker on a central server to collect scan history across multiple teams, unifying visibility into a shared security console.
🌐 Air‑Gapped Environments	Air-gap friendly. Deploy the standalone Docker bundle to isolated networks with zero external asset dependencies or tracker requests.

---

🔍 Network Flow & Topology

🔄 Logical Data Lifecycle

The functional flow below maps exactly how raw multi-scanner inputs route through our parsing engine to be normalized and centralized:

graph LR
    subgraph Scanners [Multi-Scanner Core Inputs]
        T[Trivy Scan] 
        S[Semgrep Scan] 
        P[Poutine Scan] 
        Z[Zizmor Scan] 
        G[Gitleaks Scan]
    end

    Scanners --->|Raw Reports| CLI(🛡️ devsecops-radar CLI Engine)
    CLI --->|Normalize & Deduplicate| Out[findings.json]
    Out ---> Web(📊 Flask Dashboard App)
    Web ---> UI[🌐 Modern Browser Command Center]

    style CLI fill:#1e1e2e,stroke:#3b82f6,stroke-width:2px,color:#cdd6f4
    style Web fill:#1e1e2e,stroke:#10b981,stroke-width:2px,color:#cdd6f4
    style Out fill:#181825,stroke:#fab387,stroke-width:1px,color:#a6e3a1
    style UI fill:#11111b,stroke:#a6e3a1,stroke-width:2px,color:#cdd6f4

🌐 Operational Infrastructure Mapping

Once processed, the centralized findings are rendered inside your topology mapping network boundaries, visualising the operational relationship between distinct pipeline segments:

---

📸 Dashboard Preview

(See the animated demo at the top of this README for a live preview of the UI in action!)

---

🚀 Quick Start

Get up and running in 3 simple steps:

# 1. Install from PyPI
pip install devsecops-radar

# 2. Feed scanner data (sample data is included in the repo)
devsecops-radar --trivy sample_trivy.json --semgrep sample_semgrep.json

# 3. Launch the dashboard
devsecops-radar-web

Open http://localhost:8080 — your unified command center is live with sample findings.

[!TIP] 🧙 Want a fully guided setup? Run the interactive wizard:

devsecops-radar --wizard

---

📦 Installation

View All Installation Options (PyPI, Docker, Source, One-Command)

Option 1 — PyPI (Recommended)

pip install devsecops-radar

Option 2 — From Source

git clone https://github.com/Mehrdoost/devsecops-radar.git
cd devsecops-radar
pip install -e ".[dev]"

Option 3 — Docker

docker pull ghcr.io/mehrdoost/devsecops-radar:latest
docker run -p 8080:8080 ghcr.io/mehrdoost/devsecops-radar:latest

Mount your own findings file:

docker run -p 8080:8080 -v $(pwd)/findings.json:/data/findings.json ghcr.io/mehrdoost/devsecops-radar:latest

Or use Docker Compose:

docker compose up

🧙 One‑Command Install (curl)

curl -fsSL https://raw.githubusercontent.com/Mehrdoost/devsecops-radar/main/install.sh | bash

This script installs Python dependencies, Ollama, pulls the AI model, and starts the wizard.

---

📋 Prerequisites

[!IMPORTANT] Pipeline Sentinel relies on external security tools to produce the JSON reports it consumes. You must install these tools separately according to your needs.

• Required for offline scanning: Trivy, Semgrep, Poutine, Zizmor, Gitleaks.
• Optional: Ollama (AI analysis), Docker (Sandboxing), OPA (Rego policy).

📖 See PREREQUISITES.md for full installation details of these tools.

---

🧭 How to Use (Step‑by‑Step)

1. Run Your Security Scanners

Generate JSON output from your tools:

trivy image --format json -o trivy.json nginx:latest
semgrep --config=auto --json --output semgrep.json .
poutine scan ./repo --format json --output poutine.json
zizmor scan ./repo --output zizmor.json --format json
gitleaks detect --source . --report-format json --report-path gitleaks.json

2. Merge Findings with the CLI

devsecops-radar --trivy trivy.json --semgrep semgrep.json --poutine poutine.json --zizmor zizmor.json --gitleaks gitleaks.json

This produces a single findings.json with all findings merged and normalised.

3. View the Dashboard Engine

Execute the web wrapper to spin up your centralized analytics engine:

devsecops-radar-web

📊 Tactical Web Console Architecture

The single-page real-time dashboard elegantly partitions telemetry into high-impact actionable items:

Dashboard Component	Interface Visualization Type	Core Operational Value
Severity Breakdown	Dynamic Doughnut Charts	Instant tracking of global exposure density and total counts.
Trend Over Time	Aggregated Line Timelines	Historical trajectory graphs drawn from persistent scan logs.
Pipeline Security	Specialized Poutine + Zizmor Matrix	Micro-telemetry analyzing supply chain health and meta-workflows.
Attack Path Graph	Interactive D3.js Force Nodes	Clickable chain mapping demonstrating structural flaw correlations.
Executive Summary	Context-Rich Summary & Risk Scoring	Algorithmic threat intelligence translated into executive-ready metrics.
Findings Datagrid	Searchable Paginated Checkbox Tables	Granular configuration control built for isolating entities for target simulations.

4. Enable AI Analysis (Optional)

ollama pull llama3.2:latest
devsecops-radar --trivy trivy.json --analyze
devsecops-radar-web

The LLM generates findings_ai_summary.json containing: executive_summary, risk_score, attack_paths (with MITRE ATT&CK), top_remediations, and false_positives_likely.

5. Auto‑Remediation (with Human Review)

# Apply fixes automatically
devsecops-radar --trivy trivy.json --analyze --fix

# Interactive step‑by‑step review
devsecops-radar --trivy trivy.json --analyze --fix --review

[!NOTE] All modified files are backed up to ~/.devsecops-radar/backups/. The tool creates a new git branch auto-fix and pushes it for review.

6. Policy Enforcement

Create a policy.json file:

{
  "max_critical": 5, 
  "on_violation": "fail"
}

devsecops-radar --trivy trivy.json --policy policy.json

If critical findings exceed 5, the command exits with code 1. You can also use OPA Rego policies (--rego-policy).

7. Generate Compliance & Standard Reports

# PDF report with compliance mapping
devsecops-radar --trivy trivy.json --analyze --compliance CIS --report cis-report.pdf

# Export as SARIF for GitHub Code Scanning
devsecops-radar --trivy trivy.json --export-sarif report.sarif

# Export as CycloneDX SBOM
devsecops-radar --trivy trivy.json --export-cyclonedx report.cdx.json

8. Security Badge for Your Project

Embed a dynamic security badge in your README:

[![Security Status](https://your-server/badge/1.svg)](https://github.com/Mehrdoost/devsecops-radar)

9. Jira / Asana Integration (New!)

Set environment variables to create issues automatically:

export JIRA_URL="https://your-domain.atlassian.net"
export JIRA_TOKEN="your-api-token"
devsecops-radar --trivy trivy.json --analyze --notify-jira

export ASANA_TOKEN="your-asana-token"
export ASANA_WORKSPACE="your-workspace-gid"
devsecops-radar --trivy trivy.json --analyze --notify-asana

---

📋 Complete Command Reference

Click to Expand Command Categories

🔎 Scanners & Inputs

Flag	Description	Example
--trivy	Trivy JSON file or image name	--trivy results.json or nginx:latest
--semgrep	Semgrep JSON file or directory	--semgrep results.json or ./src
--poutine	Poutine JSON file or repo path	--poutine results.json or ./repo
--zizmor	Zizmor JSON file or repo path	--zizmor results.json or ./repo
--gitleaks	Gitleaks JSON file or repo path	--gitleaks results.json or ./repo
--rules	Directory with custom JSON rules	--rules ~/my-rules/
--topology	Path to topology JSON file	--topology topology.json

🧠 AI, Policies & Remediation

Flag	Description	Example
--analyze	Enable async LLM analysis (Ollama required)	--analyze
--llm-backend	ollama (default) or litellm	--llm-backend litellm
--llm-model	Model name	--llm-model gpt-4o-mini
--fix	Auto‑apply AI‑suggested fixes (with backup)	--fix
--review	Interactive step‑by‑step remediation	--review
--policy	Policy JSON file for gating	--policy policy.json
--rego-policy	OPA Rego policy file	--rego-policy policy.rego

📊 Reports & Exports

Flag	Description	Example
--output	Output JSON file (default: findings.json)	--output merged.json
--report	Generate PDF/JSON/HTML report	--report report.pdf
--export-sarif	Export findings as SARIF	--export-sarif report.sarif
--export-cyclonedx	Export findings as CycloneDX	--export-cyclonedx report.cdx
--compliance	Framework: CIS, PCI-DSS, ISO27001	--compliance CIS

⚙️ Integrations & Setup

Flag	Description	Example
--notify-jira	Create Jira issues for criticals	--notify-jira
--notify-asana	Create Asana tasks for criticals	--notify-asana
--wizard	Interactive first‑time setup wizard	--wizard
--update-rules	Download/update community rules	--update-rules

[!TIP] devsecops-radar-web — Web Server Options

devsecops-radar-web                         # Launch on http://localhost:8080
FINDINGS_FILE=my.json devsecops-radar-web   # Use a custom findings file
PIPELINE_API_KEY=secret devsecops-radar-web # Enable API authentication

---

✨ Core Capabilities

🔌 Multi-Scanner Ingestion Engine

• Pluggable Architecture: Native modular decoders ingest structured data seamlessly from Trivy, Semgrep, Poutine, Zizmor, and Gitleaks.
• Hybrid RuleFusion Layer: Dynamically evaluation of custom local JSON policies mapped on top of live community-driven git feeds.
• Scan History Optimization: Persistent historical compilation powered by SQLAlchemy featuring sub-second result slicing.

🧠 Advanced Intelligence & Active Remediation

• Asynchronous Context Enriched LLM: Multi-backend integration hooks (Ollama/LiteLLM) mapping structural CVE configurations to real-world MITRE ATT&CK vectors.
• Interactive Remediation Tracks: Intelligent mutation options applying autonomous hotfixes (--fix) balanced by modular human verification checklines (--review).
• Exploit-Aware Scoring: Modern analytical calculations analyzing vector severities alongside real-time asset exposure and dynamic surface reachability.

🛡️ Enterprise Policy & Supply-Chain Governance

• Policy-as-Code Frameworks: Advanced control assertions parsing validation rules via strict local JSON constraints or distributed Open Policy Agent (OPA) Rego scripts.
• Supply Chain Verification: Comprehensive CycloneDX SBOM data compilation complete with proactive VEX vulnerability masking layers.
• Air-Gapped Absolute Confidentiality: Complete dependency localization guaranteeing data processing loops execute with zero external request callbacks.

---

🌍 Community Rules & Online Updates

Pipeline Sentinel features a community‑driven rule marketplace housed in a separate repository: devsecops-radar-rules.

How It Works: The repository contains curated JSON rule files for all supported scanners. You can pull the latest rules with a single command:

devsecops-radar --update-rules

Rules are stored locally in ~/.devsecops-radar/community-rules/. To use them alongside your scanner results:

devsecops-radar --trivy scan.json --rules ~/.devsecops-radar/community-rules/

[!NOTE] You can even point to your own private repository via COMMUNITY_RULES_REPO!

---

⚔️ Attack Simulation & What‑If Analysis

Interactive attack simulation directly from the dashboard:

1. Tick the checkboxes next to the findings you want to investigate.
2. Click “⚡ Simulate Selected”.
3. A modal displays a generated attack script (bash), attack chain description, and (if Docker is available) the sandbox output.

(You can also click any node in the Attack Path Graph and press “Simulate this attack”).

---

🔐 Security Improvements in v0.4.2

• Path Traversal Prevention: All file operations (rules, manifests, SBOM, backups) now strictly validate that paths remain within the allowed base directory.
• Input Sanitization for Attack Simulation: Bash script generation now safely escapes all user-controlled data, eliminating command injection risks in sandboxed PoCs.
• Hardened Docker Sandbox: Attack simulation containers run with --cap-drop=ALL, --read-only filesystem, --network=none, and as non-root user nobody.
• Constant-time API Key Comparison: Login and API key verification use hmac.compare_digest to prevent timing attacks.
• Database Connection Security: SQLite WAL mode enabled, foreign keys enforced, and pool_pre_ping configured for connection health checks.
• Input Size Limits: Payload size restricted (1MB), database field lengths truncated to prevent DoS and log bloat.
• Safe Community Rule Updates: Git operations are restricted to whitelisted https://github.com URLs only, with strict argument validation.
• Secrets Redaction: PDF reports and logs automatically redact passwords, tokens, and keys.
• Mandatory Environment Secrets: JWT secret and API key must be provided; the server fails fast if they are missing or weak.

---

🏗️ Architecture

devsecops_radar/
├── cli/            # CLI entry point – plugin discovery, policy, remediation
├── core/           # RuleFusion engine, DB (SQLAlchemy), async LLM analysers
├── scanners/       # Pluggable scanner classes (extend ScannerPlugin)
├── plugins/        # ScannerPlugin abstract base class & entry points
└── web/            # Flask dashboard (modular Blueprints, WCAG 2.1 AA)
    ├── dashboard/  # Main dashboard routes & embedded HTML
    ├── attack_paths/
    ├── topology/
    ├── summary/
    └── sentry/     # Live webhook agent for CI/CD

---

🗺️ Roadmap

Phase	Feature	Status
✅ Phase 1	Multi‑scanner engine (Trivy, Semgrep, Poutine, Zizmor), LLM analysis, GH Actions	Done
✅ Phase 2	Attack‑path visualization, Policy‑as‑Code, Auto‑remediation, Compliance reports	Done
✅ Phase 3	Web dashboard Blueprint, ORM pagination, SBOM, Dynamic Risk Scoring, Gitleaks	Done
✅ Phase 4	Advanced attack simulation, VEX filtering, Async LLM, SARIF/CycloneDX	Done
🔲 Phase 5	eBPF runtime security agent	Planned
🔲 Phase 5	Rule marketplace with YAML	Planned
🔲 Phase 5	Pull Request assistant (GitHub App)	Planned

[!NOTE] See the open issues for a full list of proposed features.

---

🧪 Testing & CI

Pipeline Sentinel is thoroughly tested to ensure reliability for production use.

• Unit & Integration Tests: 23+ tests covering scanners, rule engine, database, analyzer, API, and CLI.
• CI Pipeline: Every push and pull request triggers automated testing (pytest with coverage) and linting (ruff, mypy) via GitHub Actions.

Run tests locally:

pip install -e ".[dev]"
pip install pytest pytest-flask ruff
pytest tests/ -v --cov=devsecops_radar --cov-report=term-missing
ruff check .
mypy .

---

🤝 Community & Support

• Security Policy: We take security seriously. If you discover a vulnerability, please report it privately. See our full Security Policy for details.
• Contributing: We welcome contributions of all kinds! Please read our Contributing Guide. For adding new rules, see the Community Rules section.
• Code of Conduct: This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code.

---

⚡ Support Development

Sponsor this project with a crypto donation.
All funds go directly to the developer.

🔗 Donate USDC (Polygon) _{0x1234...5678} ·

---

👨‍💻 Author

ReverseForge — ( Mehrdoost And Mi0r4 )

---

📜 License

MIT — see LICENSE.

⭐ If this project helps your team ship safer software, drop a star — it makes a real difference.