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.
Sources
همفکران فناوری شریف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
همفکران فناوری شریف
