EvidenceSheet

OIS-03 Interfaces and Dependencies

Document and communicate the interfaces and dependencies between delivery activities run by the provider and those run by third parties, covering how vulnerabilities, security incidents and malfunctions are handled, and

4
artefacts
0
held by a system
0
at each review
hard
to go live
Vendor register / contract repository
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

none for this control

governing documentDocuments that govern the control

  • Shared responsibility model or duty matrix splitting delivery tasks between provider and third parties · Vendor register / contract repository
  • Service descriptions and contract clauses that fix cooperation duties for incidents and malfunctions · Vendor register / contract repository
  • Change notifications issued to dependent organisations, with dates showing the lead time given · Vendor register / contract repository
  • Joint escalation and contact directory used for reporting faults across organisational boundaries · Vendor register / contract repository

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

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

OIS-02 Information Security Policy · OIS-04 Segregation of Duties