Data security before a business review

What Lode examines

Lode examines business problems and the evidence behind management decisions. Probe frames an initial examination, Verdict develops a comprehensive diagnosis, and Countersign provides a second opinion before a decision. The deliverable is an assessment that separates observations, explanations and uncertainty. It is not a request to move every company record into a new system.

Start with an inventory, not an upload

In the first conversation, describe the decision, the deadline and the types of records available. A list of systems and reporting periods is enough to discuss scope. Do not include confidential documents, passwords or personal data extracts in the contact form.

For example, an examination of delayed renewals might start with aggregated renewal counts and the stages of the renewal process. Individual correspondence should only enter scope if it is necessary to examine a specific question. More data does not automatically mean stronger evidence.

Agree the sharing boundaries before work begins

Use these questions to define the engagement before handing over records:

• Purpose: which decision will the review support, and which records are necessary?
• People: who may access the material, and who can authorise additional access?
• Method: which sharing channel, tools and service providers may be used?
• Location: where will records be stored and processed, including any external model service?
• Duration: what retention period applies, and what happens to working copies, backups and access at closure?
• Exceptions: what requires fresh approval if the scope or tools change?

Lode defines scope, confidentiality and data-sharing arrangements before receiving examination data. Raise security requirements in the initial conversation so their feasibility can be assessed before an engagement is agreed. A website description does not replace the engagement's documented arrangements.

AI: ask about the data flow, not just the label

“Not used for model training” does not by itself mean “not stored” or “processed only on your premises”. Storage, inference, logging and model training are different operations. Ask which service and configuration would be used, what would leave your environment and what evidence supports the answer.

Microsoft's documentation, for example, distinguishes model training from stored service data and describes how processing location depends on deployment type. These distinctions help assess a proposed workflow; they do not describe a Lode deployment or imply that a particular provider is used in every engagement.

Where tools can act on business systems, permissions also matter. A review should not need unrestricted write access. OWASP recommends limiting tool functionality and permissions and requiring human approval for consequential actions.

What if your records are incomplete?

Begin with the records you have and the decision you face. Reports, process descriptions and scoped interviews can help identify what is known and what still needs checking. Missing evidence must remain visible in the conclusion. Neither a model nor a larger data room can turn an unverified explanation into a proven cause.

Prepare the first conversation

Tell us the business question, your target date and any restrictions on data sharing or tool use. We can then discuss whether the examination can be scoped appropriately. Read the data preparation guide for a practical inventory, or discuss your decision with Lode.

Sources and scope

This guide describes questions to settle before a business examination. It is not a security certification or legal opinion. Technical references reviewed on 19 October 2026:

• Microsoft: data, privacy and security for Foundry models
• OWASP: excessive agency and permission controls