What did not happen? Show what your answer rests on.

Why an empty search result is not enough

Internal audit asks whether any emergency approvals were used during the last quarter. The responsible team searches a log and finds no entry. A defined, recorded emergency path may genuinely not have been used. Alternatively, the wrong source may have been searched, a page may not have loaded or a record may have been omitted because its time value was missing. The result count alone cannot distinguish these cases.

Negative Assurance^™ makes the basis of the answer part of the examination. Relevant sources and event characteristics are specified beforehand. The run records what it could capture, which gaps remain and which dataset supports its result. A missing relevant time value or an incomplete required source prevents a positive attestation.

Three types of examination, simply explained

How a traceable receipt is created

1. Define the question

   Sources, period and relevant event characteristics are specified in a profile.

2. Examine the records

   The module captures available records, identifies gaps and examines the claim.

3. Preserve the result

   The result and its limits are secured together; examination material can be recomputed.

JSON, PDF and TXT represent the same stored examination. Machine-readable material supports recomputation within the declared scope; readable formats make results and limits accessible in reviews and records.

What changes for your institution

The answer to an audit question becomes a bounded evidence package. The declared period, named sources, preserved examination material and statement limits accompany the result. Teams, auditors and leadership can discuss the same basis rather than assembling different log extracts after the fact.

An unfavourable result remains visible. A counterevent produces evidence contradicting the claim. Incomplete capture produces a visible gap. This helps an institution distinguish the statements it can support from those that require a better data foundation first.

The potential time benefit comes from a prepared checking path and repeatable verification. No specific reduction in hours, costs or review duration is promised. Negative Assurance^™ supplies material for professional assessment; it does not replace internal audit, an assurance opinion or a supervisory decision.

Three questions from institutional practice

Internal audit: “Was any of our named emergency paths used during the period?” The profile identifies the paths and their sources. A match contradicts absence. A gap prevents confirmation. A positive result means only that the defined characteristics are absent from the completely captured dataset.

Data protection: “Are the required destruction records present for these data and keys?” The run examines the declared records and recorded key status. Storage locations or copies beyond the coverage remain beyond the statement. The evidence becomes easier to understand without claiming complete deletion that has not been established.

Due diligence and governance: “What supports your statement that a particular event class is absent?” Instead of a result count alone, the institution can provide bounded examination material and its receipt. The meaning of the class must be established first. A label no system ever emits cannot support a claim about proper conduct.

The next review will not wait for your evidence foundation

The advantage begins before the request. Institutions that clarify event sources, time values and responsibilities now can answer more precisely later. A team discovering incomplete capture at the start of a review cannot reliably recreate any missing history at will. A new report cannot replace absent evidence.

Depending on the framework, regulatory obligations address documentation, accountability, risk management or logging. They do not mandate this module. Negative Assurance^™ can contribute evidence for selected questions. Whether that evidence is sufficient for a particular duty requires a separate assessment.

Regulatory timing in context

Sources reviewed: 15 October 2026. Applicability depends on role, system and framework. These dates do not mandate Negative Assurance^™.

• DORA · Art. 6, 64
• DSGVO / GDPR · Art. 5, 17
• European Commission · AI Act timeline

A clear statement needs clear limits

The statement applies only to the declared event universe, period and evidenced capture scope. Retrieving every available record does not automatically establish that every real-world action was logged. Sources without demonstrated sequence coverage or tenant binding are identified accordingly.

The currently described implementation uses a symmetric signature. Origin verification requires the key holder; public signature verification is not included. Examination material and hashes can be recomputed, but are not, on their own, independent evidence of origin. External time attestation is not connected.

The internal module acceptance was reported as 44 out of 44 cases passed. These covered valid cases, counterevents, data gaps, modified material and correction receipts, among other checks. This is internal testing of a declared scope, not independent certification or verification of every customer installation.

Start with one concrete audit question

Choose a question whose relevant event characteristics are actually captured in your systems. Define sources and period and identify who owns the interpretation of the result. Only then does an absence proof become more than a technically correct answer to an empty question.

For banks, insurers, funds, critical infrastructure operators and other evidence-intensive organizations, this is a practical starting point: a bounded question, inspectable material and an honest result. Existing execution control remains separate. Negative Assurance^™ does not grant execution rights^™, consume capabilities or change gate decisions.

Questions about Negative Assurance^™