EvidenceSheet

CC3.3 Considering fraud risk (COSO principle 8)

The possibility of fraud is taken into account when risks to objectives are assessed. Points of focus: the assessment covers fraudulent reporting, loss of assets and corruption; incentives and pressures are weighed; opportunities for unauthorised acquisition, use or disposal of assets or for altering records are examined; the ways people might rationalise wrongdoing are considered; and IT-specific threats and weaknesses that come with using technology and reaching information are included.

Source: SOC 2 (2017 Trust Services Criteria), CC3.3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open SOC 2 (2017 Trust Services Criteria) in the compliance library.

These are criteria, not controls: you design controls that meet them, and which criteria are in scope follows the categories your report covers (Security always; Availability, Confidentiality, Processing Integrity and Privacy only if chosen). A Type 2 report tests that the controls operated across the period, so the evidence asked for is samples across that period, not one copy.

4
artefacts
0
held by a system
2
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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Fraud risk assessment or fraud section of the enterprise risk assessment · Policy repository / GRC workspace
  • Analysis of privileged access and data misuse scenarios · Identity provider / directory

governing documentDocuments that govern the control

  • Anti-fraud policy and reporting channel · Policy repository / GRC workspace
  • Actions taken to address identified fraud risks · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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

CC3.2 Identifying and analysing risks to objectives (COSO principle 7) · CC3.4 Identifying and assessing significant changes (COSO principle 9)