This is what ad hoc access control is meant to prevent. In a continuous integration and continuous deployment environment, permissions change often, but not all users should have the same keys to the kingdom. Code deploys faster when the right people have the right access at the right time—and no more. The danger comes when roles blur and access persists long after the need is gone.
Ad hoc access control in CI/CD is about creating precise, temporary, and revocable permissions that align with exact tasks in the pipeline. Instead of fixed roles and broad privileges, it enables targeted access tied to a specific job, build, or deployment stage. This is critical for enforcing security without slowing down development velocity.
The risk of not using ad hoc access control is real: unauthorized database changes in staging, production-hotfix deploys without code review, and debugging sessions that linger with elevated permissions days after the problem is fixed. Over time, this creates both security threats and compliance nightmares.