Securing the CI/CD pipeline: when your software factory is the target

Regulation & securityBy: Mahdi Mansour Samaei2 min readSource: OWASP
Securing the CI/CD pipeline: when your software factory is the target

1Introduction

CI/CD needs server keys, database credentials and repository access, making it highly privileged.

2Discussion

Attacks include stolen tokens, malicious pull requests, poisoned actions/plugins and tampered build files.

Keep secrets out of code, store them in the CI vault or a secrets manager, and scope them per job.

Protect branches with mandatory review and passing tests; require explicit approval for production deploys.

3Conclusion

Log who deployed what and when, and sign build artifacts.

Share:TelegramWhatsAppLinkedIn

Sources

  1. OWASP ↗
  2. NIST ↗
همفکران فناوری شریفThis article summarises the official sources cited, prepared by the Hamfekran Fanavari Sharif team for finance leaders.
Want to see these solutions in your organisation?Book a free demo

Related articles

Regulation & securityContainer and Docker security: from image to runtimeContainers speed deployment, but a poisoned image or bad config can expose the whole host.Regulation & securityBank cyber resilience: when prevention isn’t enoughResilience means keeping critical services running during an attack and recovering fast.Regulation & securityLLM security: prompt injection and data leakageAI assistants create a new attack surface distinct from classic software security.Regulation & securityActive Directory security: protecting the heart of corporate identityAD holds the keys to every door; compromising it means access to everything.