Pipeline Sketch

Draw secure SDLC pipeline — SAST, gitleaks, deps, DAST on YOUR $REPO CI.

Pipeline Sketch• Audio Walkthrough

00:00/02:42

Visual · t17_pipeline_sketch

Pipeline sketch = shift-left controls on code you ship. Original Cyberlium.

One diagram beats ten slides if it shows where security actually runs in YOUR workflow.

Sketch CI/CD pipeline for $REPO: commit → lint/unit → SAST → gitleaks → dependency audit → build → deploy to $LAB_URL → optional DAST baseline against lab deploy. Mark manual gates: code review, triage, rotation on leak. Note what runs on PR vs main vs nightly. Paper or Mermaid in private notes — no copying employer pipeline internals without permission. Gap paragraph: what fails open if you skip gitleaks or deps.

1. Stages

PR: fast SAST + gitleaks + tests. Main: build + deploy lab. Nightly: DAST baseline + deep audit.

Block merge on critical SAST/leak per policy from Module 7.

Command guide

Try these commands — Stages

═══ LINUX / BASH (Network & Reconnaissance Audit) ═══

Scan target host for open ports and service version signatures

Command — copy this

nmap -sS -sV -p 80,443,8080 -Pn ${LAB_HOST:-127.0.0.1}

DNS and WHOIS reconnaissance on authorized domain

Command — copy this

dig +short A target.local
dig +short MX target.local
whois target.local 2>/dev/null | grep -iE "(Registrar|Creation Date|Name Server)" | head -6

Inspect HTTP headers for technology stack fingerprinting

Command — copy this

curl -s -I "http://${LAB_HOST:-127.0.0.1}:8080" | grep -iE "(Server|X-Powered-By|Set-Cookie|Content-Security-Policy)"

Primary tools to practice this lesson: grep, curl. Reference sites: DevSecOps (https://owasp.org/www-project-developer-guide/); NIST SSDF (https://csrc.nist.gov/publications/detail/sp/800-218/final). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.