Skip to content
DM11AI TRUST & IT RISK PROTECTION
AI TrustAI governance, ISO/IEC 42001 and AI risk
Governance, Risk & CompliancePCI DSS, ISO 27001, Central Bank, SOC 2 and LGPD
CybersecurityPentesting, SAST/DAST, phishing, cloud and forensics
Security OfficeCISO, DPO, Ethical Hacker and DevSecOps as a Service
Business ContinuityResilience, BIA, crisis management and Cyber Antifrágil®
ProductsStandardsServicesProposals
Self-assessmentsFree assessments with the result on screen, no sign-up required
ComparisonsISO 27001 vs SOC 2, LGPD vs GDPR, pentest vs vulnerability assessment
FAQA hundred answers on standards, deadlines and scope
Case Studies42 stories by segment and signed testimonials
About UsContact
PTES
Talk to an expert
  1. Home
  2. Proposal
  3. AI model audit

Proposal

AI model audit

We examine the model on two fronts people often confuse: whether it treats different groups fairly, and whether anyone can explain a specific decision when the affected person asks. A model can be fair and incomprehensible, or perfectly explainable and biased. When AI decides about people, the LGPD, Brazil's General Data Protection Law, gives them the right to request a review, and answering that takes more than saying the system is good.

No price appears on this page. Scope does: what we do, how we run it, who runs it and what is not included. The people who read your request are the ones who will look after you, and they come back with the proposal and with time to talk it through.

Request steps: 2/5, Define

  1. Choose
  2. Define
  3. Identify
  4. Detail
  5. Review

2/5 · Define

AI governance

AI model audit

The model decides. Someone has to be able to explain why.

How we run it

What we examine in the model

Fairness and explainability are different questions. A model can be fair and incomprehensible, or perfectly explainable and biased.

After that come around 9 quick questions about your environment. All optional: whatever you do not know, we assume and confirm in the conversation.

Requesting is not hiring. You can ask for a proposal on more than one service, review everything on a single screen and decide what you send at the end.

What you receive

  • A bias report, with performance compared across groups
  • An explainability report, with individual decisions broken down
  • A model card: what it is for, what it learned from, where not to use it
  • An action plan with named owners and a sequence

Who runs it

ISO/IEC 42001 · ISO/IEC 23894 · NIST AI RMF · CISA · Digital Forensics

What this work consists of

We examine the model on two fronts that people often confuse: whether it treats different groups fairly, and whether anyone can explain a specific decision when the person affected asks. A model can be fair and incomprehensible, or perfectly explainable and biased. They are different examinations, and you choose one or both.

The work starts by putting the scope in writing: which model, which decisions, which groups to compare. We then test with evaluation data: performance by group, behavior on the hard cases, and the ability to reconstruct an individual decision. The result comes as a report with an action plan, and the full option adds the executive report and the presentation to leadership.

We need access to the model or its outputs, whatever development documentation exists, and your data team available to answer questions. We audit the model as it arrives: fixing what we find stays with whoever built it, and our action plan says where to start.

The backdrop is legal, not just technical. When AI makes decisions about people, the LGPD gives them the right to request a review, and answering takes more than saying the system is good. The model card and the reports are the material that supports that answer before a client, a regulator, or a data subject.

How we conduct it, stage by stage
  1. 01

    Scope definition

    We agree in writing what is in and what is out, and why. A badly defined scope is the most common cause of a project running over.

  2. 02

    Evidence gathering

    We collect what already exists: documents, configurations and logs. We start from what the company has, rather than from a blank form.

  3. 03

    Model assessment

    We test the model against evidence data: performance by group, behaviour in the hard cases and the ability to explain a specific decision.

  4. 04

    Report

    We consolidate the findings into a report where every item comes with severity, evidence and the path to fix it. We write to be read by the people who will act, not to fatten pages.

  5. 05

    Presentation

    A meeting with leadership translating the technical result into business risk and investment decisions. We arrive with the answers to the questions the board always asks: what to attack first, how much effort it takes and what happens if nothing is done.

What is not included
  • Fixing or retraining the model, which stays with your data team
  • Labeling or collecting test data, which only enters if agreed separately
  • Any guarantee of results: we audit the model as it is, not as it could be
  • Continuous model monitoring after the audit: we examine a snapshot in time, and tracking what changes is your team's routine
  • Adversarial attacks on the system, trying to make it act outside its intended behavior, which is work of a different nature
  • Legal opinions on the automated decision, which stay with the law firm you hire
  • The direct response to a data subject who requested a review, which is the controller's role: we deliver the material that supports that response

Usually comes together with

Not a bundle, and it changes nothing you have already chosen. It is what tends to come up next, in the experience of companies that have been through this.

DM11AI TRUST & IT RISK PROTECTION

ouvir. entender. resolver.

Trust to grow in the AI era. AI governance, IT risk and compliance, cybersecurity and business continuity for companies that cannot stop.

Solutions

  • AI Trust
  • Governance, Risk & Compliance
  • Cybersecurity
  • Security Office
  • Business Continuity

Products

  • oitenta20®
  • Jigphish®
  • Ethical Hacker as a Service
  • DPO Backoffice®
  • SastAction®
  • NosConformes®
  • Cyber Antifrágil®
  • All products

Company

  • About Us
  • Case Studies
  • FAQ
  • Contact

Contact

  • contato@dm11.com.br
  • +55 (11) 4837-5758
  • Av. Eng. Luís Carlos Berrini, 1140, 7º andar, Brooklin, São Paulo/SP, CEP 04571-000
  • Standards and certifications
  • Comparisons between standards
  • Self-assessments
  • Services
  • Request a proposal

DM11 © 2026 · All rights reserved.

  • Privacy Policy
  • Cookies
  • Terms of use
  • Ethics and conduct
  • Anti-corruption
  • Social responsibility