UNUS London  —  Compliance Architecture Division  |  UNCLASSIFIED // REGULATED INDUSTRIES
Home Solutions Legal & Professional Financial Services Manufacturing Healthcare ITSM & Operations Academy Blogs Ebooks Book Discovery Call UNUS Govern
⚙ ITSM & Operations SOC 2 · ISO/IEC 27001 · ITIL 4

SOC 2 Auditors Assess
Evidence, Not Intent.

IT operations teams carry the heaviest evidentiary burden in any SOC 2 audit. Change authorisations, access revocations, incident response timestamps, vendor review logs — all must be machine-produced, continuous, and queryable on demand. Most organisations have the policies. Almost none have the structured evidence trail that satisfies a Type II auditor.

CC9.2
Most commonly failed SOC 2 criterion in year-one audits — vendor compliance monitoring
6–12
Months of continuous evidence required to satisfy SOC 2 Type II observation period
1,340
Maximum Regulatory Readiness Score achievable across six ITSM mini solutions

The Six Evidence Gaps That Fail SOC 2 Audits

SOC 2 auditors do not assess policies — they assess whether controls operated continuously over the observation period. The following gaps are the six most common reasons IT operations teams receive qualified opinions or management letter findings.

🔁
SOC 2 CC8.1 · ISO/IEC 27001 A.8.32

No Authorised Change Log

Changes to infrastructure, software, and data are made without a structured authorisation record. Without immutable CAB records with approver identity and timestamp, the auditor has no evidence that CC8.1 operated — and the control fails on assertion alone.

🚨
SOC 2 CC7.3 · CC7.4 · ISO/IEC 27001 A.5.26

Incident Response Without Timestamps

Security events are triaged informally and documented retrospectively — or not at all. CC7.3 requires evidence of classification; CC7.4 requires timestamped response records. A Slack thread or email chain does not satisfy either criterion under Type II scrutiny.

🔑
SOC 2 CC6.1 · CC6.2 · CC6.3 · ISO/IEC 27001 A.5.18

Leaver Access Not Revoked on Record

The Joiner–Mover–Leaver (JML) control set is the most frequently cited gap in SOC 2 audits. CC6.3 requires documented evidence that access was revoked when no longer required. Without a structured revocation log, organisations face a critical finding regardless of their actual practice.

📊
SOC 2 A1.1 · A1.2 · ISO/IEC 20000-1 §8.3

SLA Evidence Exists in Policy Only

Availability commitments are documented in service agreements but monitored manually — or monitored with no persistent record. A1.2 requires machine-generated uptime evidence across the full observation period. Spreadsheet logs are not accepted as continuous monitoring evidence.

🏭
SOC 2 CC9.2 · ISO/IEC 27001 A.5.19

Vendor Risk Tracked in Spreadsheets

CC9.2 is the single largest point of failure in Year 1 SOC 2 audits. Organisations have vendor lists but no evidence of continuous monitoring, DPA currency tracking, or overdue review escalation. Spreadsheets are not accepted as evidence of an operating control.

🔴
SOC 2 A1.3 · CC7.5 · ISO 22301 §8.4

BCP/DRP Plans Tested Without Records

Business continuity and disaster recovery exercises are conducted but test outcomes, gaps, and remediation actions are not formally recorded. A1.3 requires documented evidence that recovery procedures were tested. A policy document and a verbal assurance constitute simultaneous failures of A1.3 and CC7.5.

Why Assertion Fails Where Evidence Succeeds

SOC 2 Type II auditors operate on a simple principle: if it is not recorded, it did not happen. The observation period — typically six to twelve months — requires that every control operated continuously, not just at the point of audit preparation. Retrospective documentation is identifiable and constitutes a finding.

The ITSM domain carries disproportionate audit risk because it sits at the intersection of Security (CC6–CC9), Availability (A1), and Confidentiality (C1) Trust Services Criteria simultaneously. A single unresolved JML gap — one leaver whose access revocation is undocumented — can trigger findings across CC6.1, CC6.3, and C1.1 in a single audit cycle.

The UNUS London approach is architectural, not procedural. Evidence is produced structurally by the database and workflow layer — not generated by a person filling in a form. This means the evidence trail is continuous, immutable, and auditor-ready without any additional effort at the point of assessment.

ISO/IEC 27001:2022 ISO 9001:2015 ISO/IEC 20000-1:2018 ITIL 4 SOC 2 AICPA TSC 2017 ISO 22301:2019
⚖️
Most Common Year-1 Finding
CC9.2 — Vendor Compliance Monitoring
🔐
Highest-Risk Multi-Criterion Failure
CC6.1 + CC6.3 + C1.1 — JML Control Set
📅
SOC 2 Type II Observation Period
6–12 Months of Continuous Evidence Required
⏱️
Leaver Revocation SLA (Default)
24 Hours — Monitored Structurally
📋
Change Authorisation Requirement
CC8.1 — Immutable Pre-Deployment Record
🔄
BCP/DRP Test Evidence Requirement
A1.3 — Written Outcome + Remediation Log

Database-First. Evidence-Grade. Auditor-Ready.

Every UNUS London ITSM mini solution is built on three production components: a PostgreSQL/Supabase schema with immutable audit triggers and Row Level Security, an n8n automation workflow producing timestamped evidence records without human intervention, and a single-file HTML portal surfacing the evidence trail in auditor-exportable format. Regulatory justification is embedded in every design decision.

01 — Evidence Production Layer

Immutable PostgreSQL Schema with Audit Triggers

Every record written to the database is immutable by design. Audit triggers capture every state transition — who changed what, and when — without relying on application-layer logging. Row Level Security enforces firm-scoped data isolation. Evidence views (vw_*) pre-aggregate the audit trail for direct auditor consumption without exposing operational tables.

ISO/IEC 27001 A.8.15 SOC 2 CC6.1
02 — Continuous Monitoring Layer

n8n Workflow Automation — Zero-Touch Evidence

Workflows trigger on schedule or webhook — not on human action. Approval routing, escalation alerts, health checks, and SLA breach detection all write structured records automatically. The observation period evidence trail is produced continuously from day one of deployment, satisfying the Type II requirement for controls that operate without periodic manual intervention.

ITIL 4 — Continual Improvement ISO 9001 §9.1
03 — Evidence Retrieval Layer

Single-File HTML Portals with Audit Export

Each portal surfaces the evidence trail relevant to its control domain — with RAG-status dashboards, overdue-item alerts, and a one-click evidence pack export. Evidence packs render as timestamped, print-ready HTML suitable for direct audit submission. Auditors shall be granted read-only access to vw_* views rather than operational tables, protecting data integrity during the audit window.

SOC 2 Type II ITIL 4 — Service Reporting

Aggregate Compliance Coverage Across Trust Services Criteria

1,340
out of 1,600 points
Audit-Ready Band

Six solutions deployed place an organisation in the Audit-Ready band for SOC 2 Security, Availability, and Confidentiality criteria. Privacy and Processing Integrity reach Monitored band pending PI1 and P1–P8 scope decisions.

CC8.1 + CC6.8 — Change Enablement
MS-ITSM-01 — CAB Register
+220 pts
CC7.3 + CC7.4 + A1.2 — Incident Management
MS-ITSM-02 — Incident & Problem Register
+240 pts
CC6.1 + CC6.2 + CC6.3 + C1.1 + P5.1 — Access Control
MS-ITSM-03 — Access & Identity Lifecycle
+280 pts
A1.1 + A1.2 + PI1.1 — SLA Monitoring
MS-ITSM-04 — SLA Evidence Dashboard
+200 pts
CC9.2 + C1.2 — Vendor Risk
MS-ITSM-05 — Vendor & Third-Party Risk Register
+220 pts
A1.2 + A1.3 + CC7.5 — Business Continuity
MS-ITSM-06 — BCP/DRP Planner
+180 pts

Six Production-Ready SOC 2 Evidence Systems

Each mini solution is independently deployable and production-ready in 14 days. All six systems share the UNUS London database-first architecture. Pricing for all ITSM mini solutions is available exclusively on discovery call — book below to receive a scoped proposal.

📋 MS-ITSM-01
SOC 2 CC8.1 · CC6.8 · ISO/IEC 27001:2022 A.8.32 · ITIL 4 Change Enablement

Change Advisory Board (CAB) Register

Every proposed change — normal, standard, or emergency — is logged as an immutable database record. The n8n workflow routes requests to the relevant approver, captures approval decisions with a timestamp, and closes each change with a structured post-implementation review. The HTML portal surfaces the full CAB backlog with RAG-status indicators and an exportable evidence pack for audit submission.

SOC 2 Evidence Produced
  • Change log with immutable timestamps and approver identity
  • Pre- and post-implementation notes with rollback record
  • Directly satisfies CC8.1 and CC6.8
Regulatory Readiness Contribution: +220 points (Security Domain)
Book Discovery Call for Pricing
🚨 MS-ITSM-02
SOC 2 CC7.3 · CC7.4 · A1.2 · ISO/IEC 27001:2022 A.5.26 · ISO 9001 §10.2

Incident & Problem Management Register

Incidents are classified by priority (P1–P4) using a severity matrix and routed to on-call responders within five minutes for critical events. Every status transition is timestamped. P1 incidents trigger automatic root cause analysis records. Problems — recurring incidents sharing a root cause — are linked to child incidents in the schema, enabling structured trend analysis and MTTR computation against SLA thresholds.

SOC 2 Evidence Produced
  • Incident log with severity, timestamps, and responder identity
  • RCA linkage and MTTR computation against defined SLAs
  • Satisfies CC7.3, CC7.4, and contributes to A1.2
Regulatory Readiness Contribution: +240 points (Security + Availability Domains)
Book Discovery Call for Pricing
🔑 MS-ITSM-03
SOC 2 CC6.1 · CC6.2 · CC6.3 · C1.1 · P5.1 · ISO/IEC 27001:2022 A.5.18 · A.8.2

Access Control & Identity Lifecycle Register

The Joiner–Mover–Leaver (JML) control set is the most commonly cited gap in SOC 2 audits. Every access lifecycle event is recorded with time-gated approval enforcement. Leaver records trigger an automated revocation deadline monitor: if access is not confirmed revoked within 24 hours, an escalation alert fires and the overdue record surfaces in the portal's red RAG panel — constituting a critical control failure if unresolved.

SOC 2 Evidence Produced
  • Access grant log with approver identity and provisioning timestamp
  • Access revocation log with deadline enforcement audit trail
  • Satisfies CC6.1, CC6.2, CC6.3, C1.1, and P5.1
Regulatory Readiness Contribution: +280 points — Highest Single-Solution Score
Book Discovery Call for Pricing
📊 MS-ITSM-04
SOC 2 A1.1 · A1.2 · PI1.1 · ISO/IEC 20000-1:2018 §8.3 · ISO 9001 §8.6

SLA Evidence Dashboard

The n8n Health Monitor workflow pings configured endpoints every six hours and writes structured availability records to Supabase. The dashboard aggregates these into monthly uptime percentages, SLA breach events with duration, and MTTR statistics. A one-click monthly SLA report produces machine-generated, timestamped evidence — replacing the assertion-only documentation that fails A1.2 under Type II audit.

SOC 2 Evidence Produced
  • Monthly uptime percentages per service with stored SLA thresholds
  • Breach event log with timestamps, duration, and escalation audit trail
  • Satisfies A1.1 and A1.2; contributes to PI1.1
Regulatory Readiness Contribution: +200 points (Availability Domain)
Book Discovery Call for Pricing
🏭 MS-ITSM-05
SOC 2 CC9.2 · C1.2 · ISO/IEC 27001:2022 A.5.19 · A.5.20 · ITIL 4 Supplier Management

Vendor & Third-Party Risk Register

CC9.2 is the most commonly failed criterion in Year 1 SOC 2 audits. Every vendor with access to systems or data carries a risk tier (Critical/High/Medium/Low), DPA currency status, and a structured review schedule. The daily monitoring workflow sends renewal alerts, escalates overdue reviews, and surfaces non-compliant vendors in the portal's risk dashboard — constituting the continuous monitoring evidence CC9.2 requires and spreadsheets cannot provide.

SOC 2 Evidence Produced
  • Vendor register with risk classification and DPA expiry tracking
  • Review completion log with timestamps and overdue escalation trail
  • Satisfies CC9.2 and contributes to C1.2
Regulatory Readiness Contribution: +220 points (Security Domain — CC9.2)
Book Discovery Call for Pricing
🔄 MS-ITSM-06
SOC 2 A1.3 · CC7.5 · ISO/IEC 27001:2022 A.5.29 · ISO 22301:2019 §8.4 · ITIL 4 IT Service Continuity

Business Continuity & DR Planner

BCPs and DRPs are registered with structured RTO/RPO commitments and scheduled test exercises. The n8n workflow sends test reminders 14 days before due dates, captures structured test outcomes (pass/pass-with-gaps/fail), and tracks remediation actions to closure. The HTML portal displays the full continuity plan register, test history, and open remediations — giving an auditor everything needed to satisfy A1.3 and CC7.5 in a single evidence export.

SOC 2 Evidence Produced
  • BCP/DRP register with RTO/RPO commitments and test schedule
  • Test exercise log with outcome, gaps identified, and remediation status
  • Satisfies A1.2, A1.3, and CC7.5
Regulatory Readiness Contribution: +180 points (Availability Domain)
Book Discovery Call for Pricing

SOC 2 Criterion Coverage Map

The table below maps each SOC 2 Trust Services Criterion to the ITSM mini solution that addresses it, and documents the audit finding that arises in its absence.

TSC Criterion Control Objective Solution Without Solution Failure Type
CC6.1 Logical access controls implemented MS-ITSM-03 No structured evidence of access control operation Critical
CC6.2 New access registered and authorised MS-ITSM-03 No JML log; auditor cannot verify who was granted what Critical
CC6.3 Access removed upon role change or departure MS-ITSM-03 Leaver revocations undocumented; critical CC failure Critical
CC6.8 Changes authorised before deployment MS-ITSM-01 No change log; authorisation by assertion only Critical
CC7.3 Security events evaluated and classified MS-ITSM-02 No incident classification evidence Major
CC7.4 Incidents responded to per defined procedures MS-ITSM-02 No response timestamp or escalation trail Major
CC7.5 Disruption response procedures exercised MS-ITSM-06 Test records absent; simultaneous A1.3 failure Critical
CC8.1 Changes to infrastructure authorised and logged MS-ITSM-01 Same as CC6.8; compound finding risk Critical
CC9.2 Vendor compliance monitored continuously MS-ITSM-05 Most common Year 1 SOC 2 finding; no monitoring evidence Critical
A1.1 Availability commitments communicated MS-ITSM-04 SLA targets exist in policy only; not machine-enforced Major
A1.2 System meets availability commitments MS-ITSM-02 + MS-ITSM-04 No uptime data; no MTTR evidence across observation period Critical
A1.3 Recovery procedures tested and documented MS-ITSM-06 No test records; criterion fails on assertion alone Critical
C1.1 Confidentiality commitments met MS-ITSM-03 Access to confidential data unaudited and untracked Major
PI1.1 System performs as committed MS-ITSM-04 No performance baseline or deviation evidence Major

Deployment Requirements

Per ISO/IEC Directives Part 2 drafting conventions: shall denotes an absolute requirement; should denotes a recommendation; may denotes a permitted action.

Shall

The deploying organisation shall execute all SQL DDL migrations in the Supabase SQL Editor before activating any n8n workflow node.

Shall

The deploying organisation shall configure Row Level Security using the auth.uid() IS NOT NULL pattern; recursive subquery patterns shall not be used in RLS policies on any table in this stack.

Shall

SOC 2 Type II auditors shall be provided with read-only Supabase access scoped to the relevant evidence views (vw_*) rather than direct table access, to protect operational data integrity during the audit period.

Should

The deploying organisation should conduct a quarterly evidence export from each portal and retain the output in a designated audit evidence folder for the duration of the SOC 2 observation period.

Should

The deploying organisation should initiate solution deployment no later than six months prior to the intended SOC 2 Type II report period start, to ensure a full observation window of continuous evidence is available at audit.

May

The deploying organisation may extend any schema with additional columns without affecting the regulatory mapping, provided that audit trigger coverage is maintained on all columns that carry evidence value.

Your Organisation's SOC 2 Evidence Shall Be Structurally Produced

Book a 30-minute discovery call. We will assess your ITSM compliance posture against SOC 2 Trust Services Criteria, identify your highest-risk evidence gaps, and specify the production-ready systems that address them — deployed in 14 days. ITSM mini solution pricing is provided on discovery call only.