What we do
01  Advanced Infrastructure 02  Applied AI & Data 03  AI Cybersecurity 04  AI Assurance
Engagements
AI estate inventory Assurance review
Industries
Financial Services Government & Public Sector Energy & Utilities Telecommunications Healthcare & Life Sciences Transport & Logistics Industrial & Manufacturing Retail, Hospitality & Real Estate
Research
The Trust Maturity Model The GCC Assurance Index Readiness self-assessment Case studies Perspectives Sector briefings Technology evaluations
Company
About us Partners Events Careers Contact العربية Talk to our team
Evaluations

We publish the method before the result.

We publish what we are going to test and how, before we test it. Then we publish what happened, including when the answer was inconvenient for a vendor we work with.

The rule

Three commitments, in advance.

01

Scope before test

What is being tested, on whose data, against which threshold. Published before the fieldwork.

02

Relationship disclosed

If we hold a commercial relationship with the vendor, it is stated in the evaluation, at the top.

03

Result either way

An evaluation we started gets published. Quietly dropping the ones that came out badly is how this category lost its credibility.

Planned

Three evaluations.

EVALUATION

Synthetic media detection

Vendor benchmark performance against performance on a customer’s own traffic. Scope and method published before the test is run.

PLANNED
EVALUATION

Immutability and retention lock

Whether a vault actually refuses a deletion when a privileged credential asks it to.

PLANNED
EVALUATION

Agent frameworks and the stop

How quickly a running agent can be halted, and what it leaves behind when it is.

PLANNED

Be told when a result is published.

One email per evaluation, and the method goes out before the fieldwork.

Subscribe