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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 |
Per ISO/IEC Directives Part 2 drafting conventions: shall denotes an absolute requirement; should denotes a recommendation; may denotes a permitted action.
The deploying organisation shall execute all SQL DDL migrations in the Supabase SQL Editor before activating any n8n workflow node.
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.
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.
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.
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.
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.
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.