UEM-14 Third-Party Endpoint Security Posture
Maintain the security posture of third-party endpoints that reach organisational assets, using technical measures, contractual terms or both.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Evaluation evidence that the measures operate · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Identification of third-party endpoints with access to organisational assets · Policy repository / GRC workspace
- Technical measures applied, such as posture checking at connection · Policy repository / GRC workspace
- Contractual terms binding the third party to endpoint standards · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Third party access granted with no posture requirement at all
- Contractual terms present with no technical verification
- Third-party endpoints not identified, so the population is unknown
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet