Industries
What differs between industries is the pressure — which regulator, which contractual obligation, which consequence when a control fails. Each sector page sets out that context, the regimes that apply, and how our practices support organisations working in it.
These pages describe the regulatory and risk context in each sector and how our practices apply to it. Engagement details remain confidential: security, audit and compliance work is sensitive by nature, and we do not publish client names, logos or engagement material without written consent.
Cross-sector
Sector shapes the obligation and the consequence. It does not change the underlying discipline.
Wherever several regimes apply, the answer is normalisation rather than parallel programmes — one control, tested once, satisfying every requirement it maps to.
The people who will run a control help design it. A framework agreed only with a central function is the most reliable route to implementing it twice.
If producing evidence requires a special effort, it will not be there when it is needed. Controls are designed so operating them generates the record.
The measure is not the certificate or the clean report. It is whether the registers are still current and the reviews still happening twelve months later.

Sector-specific scoping
Tell us which supervisory framework, standard or contractual requirement is driving the work. The assessment is scoped against that obligation and the control environment you actually operate.