top of page

 HOW WE WORK

Four questions. The order is the method.

 

Open almost any regulatory gap assessment produced in this region in the last five years. You will find a register of controls, a maturity score and a remediation plan. What you will not find is an architecture.

​

That omission is why so many well-funded compliance programmes fail their second audit. The controls were implemented against a checklist, not against a design. Nobody can explain why this control, at this boundary, enforcing this policy, on this classification of data. So when the estate changes — and it always changes — the controls drift, the evidence rots, and the programme starts again.

​

Most programmes we review started at Architecture. Some started at procurement, which is worse.

P

Posture

Where you actually are

​

Not where the architecture diagram says. Where discovery finds it.

​

We establish current state honestly — estate, topology, data flows, enforcement points, identity boundaries, and the gap between what is documented and what is running. Where data is in scope, discovery runs at full estate scope: cloud and on-premises, structured and unstructured, production and non-production, including backup repositories and the disaster recovery environment.

​

This is the phase organisations most want to skip, because they believe they already know. We have never completed a discovery exercise that matched a client's prior inventory. There is always an analytics extract somebody built years ago and forgot. There is often a test database holding real customer records. And there is very frequently a backup target in a jurisdiction that changes the conversation.

​

You receive: current-state topology · data inventory by classification tier and jurisdiction · the documented-versus-actual gap.

STANDARDS AND LINEAGE

Our practice is informed by and compatible with:

​

  • Attribute-driven security architecture — the traceability principle and the attribute method.

  • TOGAF — architecture development cycle, governance, architecture repository.

  • NIST CSF 2.0 — outcome structure and the Govern function.

  • NIST SP 800-207 — zero trust tenets and policy decision/enforcement separation.

  • ISO/IEC 27001:2022 and 27002:2022 — control vocabulary and management-system integration.

  • CSA Cloud Controls Matrix v4.1 — 207 controls across 17 domains, for cloud control mapping.

  • NCSC Cyber Assessment Framework v4.0 — we use its outcome-based logic as our internal assessment engine because it produces materially better findings than checklist scoring, and we report against whichever framework you are accountable to.

  • Open FAIR — for quantified risk, where a board needs exposure expressed in currency rather than as a severity label.

​

We do not claim these frameworks as our own and we do not pretend to replace them. Our contribution is the connective tissue that makes them deliver evidence in a MEA regulatory context.

bottom of page