MODULE

Mizan — the compliance center

Mizan presents your controls mapped to regulation and generates evidence packs for audit. It answers the real question of AI in a regulated institution — "what do we show the examiner" — with evidence.

Controls are mapped to KVKK, BDDK, SPK, and MASAK obligations.
Evidence packs are generated ready for internal audit and the regulator.
Mappings are presented as "designed to support".

Use cases

Audit preparation

Ahead of a BDDK, SPK, or independent audit, controls and evidence are compiled into a single pack on the audit calendar — the era of scattered screenshot-gathering ends.

Internal audit and control testing

Log summaries, policy snapshots, and configuration outputs needed for periodic control tests are produced ready to use.

KVKK documentation

Data-processing records and inventory views provide traceable input to your VERBİS and KVKK inventory work.

Gap analysis

Which obligation maps to which control — and where gaps remain — is visible on one board, so remediation can be prioritized.

Capabilities

Control library

  • A control set mapped to KVKK, BDDK, SPK, and MASAK obligations
  • Mappings follow the "designed to support" principle; no certification claim
  • Institution-specific controls and obligations can be added

Evidence generation

  • Timestamped, traceable evidence packs
  • Log summaries, policy snapshots, configuration outputs
  • Export in formats you can hand to the auditor

Continuous monitoring

  • Control-status dashboard and gap view
  • The effect of policy changes on control mappings is tracked
  • A periodic reporting calendar

How it works

  1. 01

    Choose the obligation scope

    You select the regulations and obligations that apply to your institution.

  2. 02

    Map the controls

    Start from the built-in mappings, add institution-specific controls.

  3. 03

    Let evidence gather

    Evidence is compiled automatically from platform logs and policy records.

  4. 04

    Generate the pack

    A timestamped evidence pack is produced in a single operation.

  5. 05

    Present and archive

    The pack goes to the auditor — and is itself archived as an auditable record.

What it delivers

  • Designed to reduce the effort of audit preparation
  • One timestamped pack instead of scattered evidence
  • Ready documentation for explaining AI use to the regulator
  • Not a certification claim — auditable evidence

Why it matters

In a regulated institution the real obstacle to AI is not technology but the question "what do we show the examiner." Mizan was built to answer it with evidence — it does not assert, it shows records.

Auditability

Evidence packs are timestamped and traceable; the pack itself forms an auditable record.

Related modules