Security Review Pushback
Situation
Security, compliance, or platform teams delay approval, ask for more detail, or challenge the deployment approach.
What the customer may say
"Security won't approve this until every control is documented."
What you should say
"That makes sense. Let's identify which controls are approval blockers versus documentation follow-ups, map each one to evidence, and agree who owns the review path."
What not to say
"Security reviews are usually just paperwork."
Follow-up question
"Which specific control, policy, or approver is preventing us from moving to the next step?"