DUBSAR
Private portal Flash audit
Menu

DUBSAR Flash Audit

First, see where AI is actually being used.

A useful first view to decide calmly what your organisation should protect first.

The Flash Audit does not claim to see everything and controls nothing unless the relevant flow is connected. It only reviews sources your organisation agrees to share, explains its limitations, and provides a concrete starting point.

See what the Flash Audit covers Read the governance guides

Selected sources · Read-only · No hidden surveillance

The right starting point

A clear view, not a magical search through the organisation.

Your organisation chooses what it agrees to connect. DUBSAR reviews what those sources can genuinely reveal: AI services, accounts, known owners, and the first blind spots.

This step supports a concrete discussion with the AI lead, management, the DPO, or IT. It does not read employees’ private data by default and never turns missing information into certainty.

  1. 01

    Identifiable AI use

    The AI services, accounts, or routes that authorised sources can actually identify.

  2. 02

    Ownership and blind spots

    Missing teams, owners, rules, or information that prevent a clear understanding.

  3. 03

    A first control scope

    One precise flow to connect to the Gateway next, rather than a promise to control the entire organisation.

Planned sources

Connectors help reveal AI use. They do not collect every piece of data.

Identity and collaboration

  • Google Workspace
  • Microsoft 365

Access and security

  • Cloudflare Zero Trust
  • Okta
  • Zscaler
  • Cisco Umbrella

Managed browser

  • Chrome Enterprise, depending on the authorised scope

These integrations are part of the product roadmap. What they can reveal depends on the connector, granted permissions, and the chosen scope.

The boundaries

What the Flash Audit does not do.

It does not read every prompt.

An account, device, or source that is not connected remains outside scope. Business content is not collected without a clear reason and separate authorisation.

It does not block actions yet.

Blocking, filtering, or holding an action becomes possible only when the chosen flow actually passes through the DUBSAR Gateway.

It does not certify compliance.

It helps organise AI use, ownership, and evidence. It does not replace legal advice or the organisation’s own decisions.

After the report

Choose a first flow to protect, one step at a time.

  1. 01

    Choose the flow

    Select one workflow, assistant, or AI call, with a named owner and a clear reason to protect it.

  2. 02

    Prepare the connection

    The technical owner identifies where calls travel, which models are allowed, which data needs special care, and when a person must approve.

  3. 03

    Connect the Gateway

    The selected flow then sends its AI calls through DUBSAR. The rule decides, while the Cockpit keeps a clear record of what happened.

Current status

The portal is in private testing. We do not claim more than what is ready.

The Flash Audit is the first product. Flow protection comes next, one flow at a time. It is not available everywhere yet, and we state that clearly.

Read the DUBSAR documentation Discuss a scope