DevSecOps
6 posts tagged #devsecops
6 posts on DevSecOps, spread across LLM Hardware & Local AI (2), AI in Production (1), AI Security & Safety (1) — most read: “How to Build a Local Model Registry for GGUF” and “Verify GGUF Model Hashes: 10-Step Supply Chain Workflow”.
Developer Tools How to Build a Local Model Registry for GGUF
Stop downloading random weights from links. Build a local model registry with GGUF versioning, provenance attestations, eval gates, and a real rollback plan.
Cybersecurity Verify GGUF Model Hashes: 10-Step Supply Chain Workflow
A team-ready workflow to verify GGUF integrity: compute SHA256, require signed manifests, handle mirrors safely, scan sidecars, and ship updates via an internal registry.
Cybersecurity How to Secure Docker Rootless Mode in Production
Rootless Docker shrinks the blast radius of a daemon compromise. Here’s the production hardening checklist, how it stacks up vs userns-remap, and what it won’t save you from.
Cybersecurity LLM Supply Chain Security Checklist: Lock Down Agents
A CI-ready checklist to treat models, MCP servers, tool plugins, and prompt packs as real dependencies. Pin, sign, attest, sandbox, and monitor before your agent ships malware.
Developer Tools How to Set Up gitleaks + pre-commit + CI
A terminal-first, defense-in-depth secrets workflow for 2026: staged-only hooks, CI full-history scans, baselines for legacy repos, and sane allowlists.
![claude code terminal laptop screen — illustration for article on Claude Code Security [2026]: Risks, Safe](https://img.kunalganglani.com/images/vzekdneq/production/ae489a760c8efd343421ac3a5e4b1f9b048acc2c-1200x675.webp?auto=format&fit=max&q=75&w=600)
Technology Claude Code Security: Risks, Safe Setup, Team Policy
Claude Code is safe only if you treat it like a junior engineer with terminal access. Here’s the 2026 playbook: permissions, sandboxing, egress controls, MCP allowlists, retention settings, and incident response.
Keep exploring
Close to this topic, not on this page.
