EvidenceSheet

C1.1 Confidential information is identified and protected during receipt, processing, storage

Identifies and maintains confidential information to meet the entity's objectives related to confidentiality.

5
artefacts
0
held by a system
3
at each review
hard
to go live
Document 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

  • Evidence confidential information is identified across the system, covering where it is received, processed, stored and transmitted · Document repository
  • Evidence of the retention period applied to confidential information and of its basis · Data governance / DLP tooling
  • Evidence customers are informed of and agree the confidentiality commitments the entity makes · Document repository

governing documentDocuments that govern the control

  • The definition of confidential information for the entity, including information designated confidential by customers or by contract · Vendor register / contract repository
  • The protections applied, such as access restriction, encryption and handling rules, tied to the identification · Document 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

A1.3 Recovery plan procedures support system recovery from failures · C1.2 Confidential information is disposed of securely