Secure Pipeline Template

Wed, 27 May 2026 00:00:00 +0000

“Six Gates to Production”

Most CI/CD templates stop at build-and-deploy. This one treats every commit as untrusted until six independent security tools have examined it. It is the pipeline I wish every client already had.

What problem this solves

A container image landing in production without being scanned is a liability. But bolting a scanner onto an existing pipeline is fragile: the scanner runs, the output gets ignored, and the deployment continues anyway. This template makes security gates non-negotiable. A critical finding in Semgrep, Trivy, or any other tool blocks the pipeline. A warning gets logged to a SARIF report. The deployment only proceeds when every gate passes.

AI-Assisted DevSecOps Workflows

Mon, 18 May 2026 00:00:00 +0000

“Putting LLMs in the Deployment Pipeline”

Should an LLM read your infrastructure code? Should it suggest Terraform changes? Should it triage security alerts? This guide answers those questions. It is not a tutorial. It is a living document that records what works, what breaks, and what security controls are non-negotiable when AI assistants touch production systems.

What this is

A Hugo + Docsy documentation site that covers:

Core architecture patterns for AI-assisted operations
A comparison of LLM assistant frameworks (oh-my-opencode-slim, Aider, Claude Code, ShellGPT, AIChat)
Security concerns specific to AI in DevSecOps: prompt injection, data exfiltration, over-privileged agent permissions
Three paradigms: orchestrated multi-agent, single-agent pair programming, and CLI command generation
Production-ready configuration templates for OpenCode Go

The zero-trust principles

AI assistants in DevSecOps must follow the same principles as any other automated system with production access:

Security on Adur

Secure Pipeline Template

What problem this solves

AI-Assisted DevSecOps Workflows

What this is

The zero-trust principles