Keeping scan results as build artifacts: five CI systems compared
How GitHub Actions, GitLab CI, Jenkins, CircleCI and Azure DevOps keep scan output, the keyword each uses, retention defaults and the failed run trap.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
How GitHub Actions, GitLab CI, Jenkins, CircleCI and Azure DevOps keep scan output, the keyword each uses, retention defaults and the failed run trap.
MCP config files get committed and shared. Use environment variable references and input prompts, never pasted tokens. Examples for three clients.
Slow hooks get bypassed. Use pre-commit stages to run cheap checks on commit, heavier ones on push, and the rest on demand, with a practical time budget.
Hash each file, re-embed only what changed, delete what vanished, and record the model version. A simple recipe for an index that never goes stale.
AI assistants tend to over-engineer fixes. How to prompt for a minimal diff on a security patch, so reviewers can see exactly what changed and why.
How ssl.principal.mapping.rules turns long certificate distinguished names into short Kafka principals you can actually write ACLs against.
RFC 8725 warns against human-memorable passwords as HMAC keys and against compressing before encrypting. What each rule means for JWT code and key choice.
When IntelliJ based IDEs ask whether to trust a project, Safe Mode limits builds and scripts. See what it blocks and how Trusted Locations work.
JetBrains plugins are signed twice, by the author and by Marketplace. Here is what the IDE checks, the warning you may see, and what signing leaves open.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.