Trust & firm
Data processing
Collect only what is necessary for the qualification, delivery and evidencing of the engagement.
Limit data to the mandate
Collection starts from the decision to be made and excludes information that improves neither qualification, nor verification, nor reporting.
An assurance engagement does not need to cover the entire information system. It favours metadata, extracts, samples and demonstrations wherever these are sufficient to reach the conclusion.
Production credentials, secrets and complete datasets stay out of the initial exchange when an extract, metadata or a demonstration will do.
Minimisation cycle
Each piece of data collected must retain a justifiable purpose and retention period.
Classification and restrictions
Retention linked to purpose
Deletion and export tracked
Putting into practice
Link each piece of data to its purpose and retention period.
Qualify
Name the category, source, purpose and restrictions before processing.
Minimise
Choose the extract, sample or demonstration sufficient for the conclusion.
Retain
Link the availability period to the engagement, the contract and the decisions still open.
Return
Export what needs to be exported, then delete or isolate what no longer serves a purpose.
Checkpoints
Category
Nature of the data and level of sensitivity.
Purpose
Mission question that the processing must support.
Access
Authorised people, locations and systems.
Duration
Deadline for review, return or deletion.
Engagement data cycle
Keep a purpose and a deadline for each category collected.
The file links relevant data to its source, the authorised individuals and its retention period; the absence of a purpose triggers a decision to return, isolate or delete it.
Read the processing rules →Preliminary exchange
Define the data actually needed for the mandate.
Identify the data categories, purposes, countries of access and retention periods before opening a workspace.

