Security Patch Communication: English Collocations
Security patching involves precise coordination between engineering, security, and operations teams. From issuing advisories to applying patches and assessing attack surfaces, the right vocabulary builds trust and speeds response. This exercise practises the collocations used in security bulletins, change requests, and incident communications.
0 / 5 completed
1 / 5
The security team needs to ___ a CVE advisory to all affected customers within 24 hours.
Issue an advisory is the standard security communication collocation — advisories are formally 'issued' by security teams or organisations. 'Publish' is used for public advisories; 'send' is too informal; 'release' is more associated with software than communications.
2 / 5
The patch was ___ to production on an emergency change request outside the normal release window.
Applied the patch is the standard security operations collocation — patches are 'applied' to systems. 'Deployed' is used for application releases; 'pushed' is informal; 'installed' is used for software packages but 'applied' is the preferred term for patches specifically.
3 / 5
Security engineers should ___ the attack surface before and after each patch deployment.
Assess the attack surface is the standard security collocation — threat modelling and security reviews 'assess' attack surfaces. 'Evaluate' is also correct; 'measure' implies quantification; 'review' is more general. 'Assess' is the canonical term in security documentation.
4 / 5
The CISO asked the team to ___ a risk assessment for delaying the patch by one sprint.
Produce a risk assessment is the natural collocation — risk assessments are formal documents that teams 'produce'. 'Conduct' a risk assessment is also correct; 'write' focuses on drafting rather than the analysis; 'complete' implies finishing an existing document.
5 / 5
All service owners must ___ the patching checklist before the maintenance window closes.
Complete the checklist is the standard collocation — checklists are completed item by item to ensure no step is missed. 'Sign off' implies approval of someone else's work; 'submit' implies sending to a system; 'finish' is informal and doesn't carry the structured connotation.