Governance and Audit / evidence it

The evidence and assurance auditors expect.

Audit ready evidence, produced as a by product of doing the work properly, and kept current between assessments. So when a regulator, insurer, or prime contractor asks how you protect data, the proof is already in order. From a team that is UKAS accredited for ISO 27001 and a Cyber Essentials certification body.

Governance and Audit / 01 · What assurance means

Evidence is not a folder you scramble together the week before.

Assurance is the ongoing work of producing and maintaining the evidence that your controls are in place and working. It is a by product of running the technology properly and recording it as you go, not a separate project you start when an audit looms. We capture the trail continuously, package it the way assessors actually want it, and keep it current, so an audit becomes a matter of producing a pack rather than starting from scratch.

01BaselineA recorded starting position you can demonstrate progress against.
02LogMonitoring, change records, and policy evidence captured continuously.
03PackageA plain English pack mapped to the certification or framework.
04MaintainInternal review between assessments, so the evidence never goes stale.
Governance and Audit / 02 · What the evidence is

The proof an assessor actually asks for.

When a regulator or auditor asks how you protect data, they want to see specific things. We make sure each one exists, is current, and is ready to hand over.

01Document

Policies and procedures

The documented backbone: information security and acceptable use policies, access control and data retention procedures, and the incident response plan, all written to hold up under scrutiny rather than to fill a binder.

Security policyAccess controlData retentionIncident plan
02Log

Audit logs and monitoring

Comprehensive logging and monitoring, with the records retained so the trail is there when an assessor asks. The difference between saying a control works and showing it has been working.

LoggingMonitoringLog retentionChange records
03Configure

Security configurations

The state of your systems, captured as evidence: hardening, firewall rules, multi factor authentication, and patch status, recorded so an auditor can verify what is actually in place rather than what is claimed.

HardeningFirewallsMFAPatch status
04Certify

Certification evidence

The certificates, assessment records, and training logs that show your obligations are met. Mapped to whichever standard applies, from Cyber Essentials to ISO 27001 to a sector toolkit.

CertificatesAssessment recordsTraining logs
Governance and Audit / 03 · The assurance cycle

Why assurance is continuous, not annual.

A certificate is a snapshot. It says your controls were in good order on the day you were assessed. The trouble is that systems change, people come and go, and threats move on, so a control that was sound in March can quietly drift out of shape by September. Assurance is the discipline that keeps the picture true between those snapshots.

For a standard like ISO 27001, this is built in. You do not certify once and stop. You keep the management system alive with internal audits, management reviews, and surveillance audits between full recertifications. The same logic applies even where a standard does not formally require it: the evidence is only worth having if it reflects reality, and reality keeps moving.

That is the part organisations most often underestimate, and the part a compliance platform cannot do for you. A dashboard can remind you that a review is due. It cannot patch the server, check the configuration actually changed, or stand behind the control it is asking you to tick. Because we run and secure the technology as well as evidence it, the assurance we provide reflects what is genuinely in place, and there is one accountable team behind both halves.

Governance and Audit / 04 · How we work

How the evidence comes together.

The same approach we use for our own UKAS ISO 27001 certification. Evidence captured as the work happens, then assembled when it is needed.

01

Establish the baseline

We record where you stand against the standards that apply, so progress and ongoing compliance are demonstrable rather than asserted.

02

Capture as you go

Monitoring, change records, and policy evidence are captured and retained continuously, as part of running the technology, not bolted on before an audit.

03

Review internally

Regular internal review and management oversight keep the evidence current and catch drift early, the same way an ISO 27001 system stays alive between audits.

04

Package for assessment

When an audit, insurer, or client asks, we assemble a clear, plain English pack mapped to the relevant certification or framework, ready to hand over.

The same rigour we hold ourselves to. The discipline behind our UKAS ISO 27001 certification and our Cyber Essentials certification body status is the discipline we apply to your evidence.
Governance and Audit / 05 · How this fits

Assurance rests on the controls behind it.

Evidence is only as good as the security and the systems it describes. That is why the same team produces the proof and runs the technology underneath it.

Audit and assurance is part of our governance and audit work. It builds on the documented backbone from our policy frameworks service and the preparation in compliance readiness. For organisations in the regulated supply chain, including defence and aerospace, this ongoing evidence is what turns a one off certification into something a prime contractor can keep relying on.

FAQ

Common questions

What is the difference between an audit and assurance?

An audit is a point in time review that tells you where you stand. Assurance is the ongoing work that keeps your evidence current between audits, so your compliance position stays true as systems and people change. Our standalone audit is a low commitment way to get a clear picture, while assurance is the continuous discipline behind a certification you have to keep.

What evidence will an auditor or regulator actually want?

Typically your policies, your security configurations, your audit logs, and your certification evidence. In other words, the documents that show your controls exist, the records that show they have been operating, and the certificates that show your obligations are met. We make sure each of these exists, is current, and is mapped to the standard being assessed.

How long do you retain audit logs?

We capture monitoring and change records continuously and retain them so the trail is available when an assessor asks. The right retention period depends on the standard and the sector you operate in, so we agree it with you against your specific obligations rather than applying a single blanket figure.

Can you help with a data subject access request?

We can support the technical discovery, helping you find and assemble the relevant data. The legal assessment of what to provide remains your responsibility, because that is a judgement only you can make about your own data. We make the technical side straightforward so you can focus on the decision.

Do I need this if I already use a compliance platform?

A platform can track tasks and store documents, which is useful. What it cannot do is operate the controls, verify a change actually happened, or stand behind the security it asks you to confirm. Because we run and secure the technology as well as evidence it, the assurance reflects what is genuinely in place, and one accountable team is responsible for both.

Stay ready, and prove it.

Tell us which assessments you face and we will make sure the evidence is in order and stays that way. We reply within one working day, and you will speak to an engineer, not a salesperson.

Reading, Berkshire  /  UKAS ISO 27001  /  reply within one working day