Hidden in plain sight: How SVGs carry malicious scripts
SVGs are difficult to detect, can be snuck into content — and can do malicious and legitimate actions. Here's how malicious SVGs work.
Build Pipeline Security
What is build pipeline security?
Build pipeline security refers to the protection of the systems, tools, and processes involved in building, testing, and deploying software. It ensures that unauthorized code, configurations, or behaviors aren’t introduced during software delivery by securing CI/CD systems and their dependencies.
Why secure your build pipeline?
Build environments have become high-value targets in software supply chain attacks. Compromise at this stage can lead to widespread distribution of malware or backdoors. Without a strict build pipeline security, organizations risk shipping vulnerable or tampered software to customers.
How build pipeline security works:
Build pipeline security typically involves:
- Enforcing strong identity and access management (IAM)
- Hardening and isolating build environments
- Using cryptographic signing for artifacts
- Implementing secrets management
- Continuously monitoring and logging all build actions
- Integrating security tools throughout the CI/CD lifecycle
Benefits:
- Tamper Prevention: Reduces the risk of unauthorized changes to software
- Trust & Integrity: Assures customers and regulators that software is built securely
- Breach Prevention: Protects against lateral movement and credential theft
- Audit Readiness: Improves compliance posture for ISO, SOC 2, and EO 14028
- Supply Chain Assurance: Strengthens security in vendor-delivered builds
Build pipeline security vs
Topic | Focus Area | Difference from Build Pipeline Security |
|---|---|---|
DevSecOps | Integration of security in SDLC | Broader cultural and workflow changes across the SDLC |
Post-Compilation Scanning | Review of compiled binaries | Focuses on outputs after build; the build pipeline secures the process |
Secure Build Environments | Hardening the build infrastructure | A subset of the build pipeline security focused on the environment itself |
How to Limit Attacks Using Build Pipeline Security
- Require multi-factor authentication for all CI/CD tools
- Use ephemeral and isolated build agents to prevent persistence
- Store secrets in dedicated vaults, not in build scripts
- Sign and verify all build outputs using trusted certificates
- Regularly audit and update build dependencies and plugins
Build Pipeline Security Use Cases
- Securing open-source projects against malicious PRs
- Hardening internal pipelines for financial or healthcare software
- Preventing artifact poisoning in public or internal package repositories
Additional considerations
- Always assume CI/CD systems are high-value attack targets
- Combine pipeline security with runtime verification for full coverage
- Align with guidelines like NIST 800-218, SSDF, and CISA SBOM minimum elements
- Maintain version control over pipeline definitions and infrastructure-as-code (IaC)
