Audit Trail & Compliance

Every action recorded. Every record immutable. Every audit passed.

HelixGate's audit system is not an afterthought. It is enforced at the database layer — no application code, no administrator, no engineer can alter what happened. When auditors arrive, your evidence is already there — structured, timestamped, and tamper-proof.

0
Records modifiable
DB-layer
Enforcement
SOC 2
+ ISO 27001 ready
The evidence gap

Most audit trails can be edited by someone with database access. Yours shouldn't be.

What happens without it

Audit logs that can be tampered with are not audit logs.

Mutable logs. Audit logs stored in application tables that admins can modify. A single UPDATE statement can rewrite what happened.
Manual evidence assembly. Compliance evidence assembled manually before audits. Teams spend weeks pulling records from multiple systems and hoping nothing was missed.
No tamper proof. No proof that governance records haven't been tampered with. Auditors have to take your word for it — and increasingly, they won't.
Ad-hoc erasure handling. GDPR erasure requests handled ad-hoc with no structured retention management and no audit trail of the erasure process itself.
What HelixGate provides

Immutability enforced by the database, not by policy.

Database-enforced immutability. Immutable audit records enforced by database constraints — no UPDATE or DELETE permitted. Not even a database administrator can alter what was recorded.
Full actor attribution. Every action attributed to authenticated identity with timestamp, IP address, and user agent. Not just what changed, but who did it, from where, and when.
Automatic evidence generation. Compliance evidence generated as a byproduct of normal work. When auditors ask for proof, it already exists — you don't reconstruct it.
Structured retention management. GDPR Article 17 erasure handled through structured retention policies and soft-delete patterns on core tables — not by deleting audit records.
How it works

Audit that is architectural, not aspirational.

🔒

Database-Layer Immutability

Audit records are protected by database constraints, not application code. No process — not even a database administrator — can modify or delete what was recorded. This is physical immutability, not policy.

👤

Actor Attribution

Every action is tied to an authenticated identity, a timestamp, an IP address, and a user agent. Not just 'what changed' but 'who did it, from where, and when.'

📊

Cross-Module Audit Stream

One unified audit trail across all nine governance modules. Business case approvals, supplier changes, contract renewals, ADR decisions, AI governance actions — all in one searchable, filterable stream.

📋

Compliance Evidence Generation

Audit evidence for SOC 2 and ISO 27001 is generated as a byproduct of normal governance work. When auditors ask for proof, it already exists — you don't reconstruct it.

Who it's for

Built for the teams that answer to auditors.

Compliance & Risk Officers

Generate audit evidence on demand. Every governance action across all modules is already recorded, attributed, and immutable. No more pre-audit scrambles.

External Auditors

Structured, tamper-proof evidence that proves governance processes were followed. Database-level enforcement, not just application-level assertions.

CISO / Security Teams

Every state change logged with actor, timestamp, IP, and user agent. Separation of duties enforced. No administrator bypass possible.

Compliance-ready

The compliance evidence your auditors expect.

HelixGate's immutability is not a feature toggle — it is an architectural constraint. The same database rules that prevent tampering also generate the evidence trail that SOC 2 and ISO 27001 auditors require.

SOC 2 CC7.2 ISO 27001 A.12.4.2 UK GDPR Article 17 OWASP Top 10
0
records alterable
100%
actions attributed
Technical detail

For teams that want to understand the architecture.

Database-layer immutability. Audit tables have no UPDATE or DELETE grants at any role level. PostgreSQL row-level constraints enforce append-only behaviour. No application code — regardless of privilege level — can bypass these constraints. The immutability is enforced by the database engine itself, not by application-layer access controls.

SOC 2 controls addressed. CC7.2 (system monitoring) — every state-changing operation is logged with actor, timestamp, IP, and outcome. CC7.3 (evaluate security events) — the audit stream provides a searchable, filterable record of all governance actions for security event analysis. CC1.2 (board oversight) — audit evidence can be generated on demand for governance reporting to boards and committees.

ISO 27001 Annex A references. A.12.4.1 (event logging) — all governance events are logged with structured metadata. A.12.4.2 (protection of log information) — audit records are protected by database-level constraints that prevent modification or deletion. A.12.4.3 (administrator and operator logs) — administrator actions are logged to the same immutable audit trail as all other actions, with no special bypass available.

GDPR Article 17 handling. Right to erasure is managed through structured retention policies and soft-delete patterns on core tables, while the audit trail itself is preserved for compliance. Personal data subject to erasure is handled through the retention management system — not by deleting audit records.

Separation of duties. The system enforces that submitters cannot approve their own records — ADRs, business cases — at the database constraint level. This is not a UI restriction; it is a server-side enforcement that cannot be bypassed by any user, including platform administrators.

Related modules

Governance that connects across your platform.

Questions

Frequently asked questions

Can an administrator modify audit records?

No. Audit tables are protected by database-level constraints that prevent UPDATE and DELETE operations. This applies to every user role, including platform administrators and database administrators. The immutability is architectural, not policy-based.

How does HelixGate handle GDPR right to erasure?

Personal data in core tables is managed through structured retention policies and soft-delete patterns. The audit trail records that an action occurred and who performed it, but personal data subject to erasure is handled through the retention management system — not by deleting audit records.

What compliance frameworks does the audit trail support?

The audit system is designed to satisfy SOC 2 Type II (CC7.2 system monitoring, CC7.3 security event evaluation), ISO 27001 Annex A (A.12.4.1 event logging, A.12.4.2 log protection), and UK GDPR Article 17 requirements. Evidence is generated automatically as governance actions occur.

Ready to see it?

See what tamper-proof governance evidence looks like.

Book a demo and we'll show you the audit trail in action — live, not screenshots.