Installations, energy, power quality, machinery, equipment, electrical or electronic failures and automation are examined according to the technical question and the available records.
Engineering · technology · technical evidence
Evidence for complex decisions
Technical analysis of engineering, systems, documents, signatures and digital evidence for lawyers and companies that need to understand, demonstrate and support complex technical issues.
Do not send documents or sensitive data in the first contact.
06
Technical scope
A speciality is the technical subject in which Badenas works. Its definition starts with the problem, the available sources and the question that needs to be answered.
Select an area to explore its application context.
Software, firmware, embedded systems, IoT, integrations, logs and system behaviour require a joint reading of architecture, versions, configuration and operating context.
Physical documents, substrates, alterations, erasures, compositions, handwritten signatures and comparison standards are analysed using methods appropriate to each object.
PDFs, metadata, document structure, electronic contracts, certificates, signature platforms and authentication journeys are assessed without treating an isolated indicator as automatic proof.
Logs, files, timelines, system records, electronic operations, hashes, preservation and chain of custody are correlated according to origin, integrity and availability.
On-chain transactions, smart contracts, wallets as technical identifiers, tokens and off-chain sources may form part of the analysis. A wallet does not by itself identify a person, establish authorship or enable promises of asset recovery.
01 → 05
Matrix method
Frame, preserve, examine, correlate and communicate form the method.
Review
Scope, sources and communication are reviewed throughout the work.
Select a step to explore its role in the whole.
Define the technical question, object and purpose.
Purpose
Establish scope and limits before examination.
Connection
Guides which sources to preserve and which procedures to apply.
Record relevant source origin, collection, access and transformations.
Purpose
Maintain references for examining data integrity.
Connection
Supports examination and comparison; preservation does not establish authorship.
Analyse the object using procedures proportionate to the technical question.
Purpose
Identify observable elements, records and limitations.
Connection
Provides elements to be related during correlation.
Relate documents, records, mechanisms and the sequence of events.
Purpose
Check agreements, discrepancies and gaps between sources.
Connection
Connects examinations to communication while keeping inference limits explicit.
Present findings, inferences, gaps and limitations distinctly.
Purpose
Make the technical analysis understandable within its scope.
Connection
Returns to the initial question and includes review of sources and communication.
Correlation
Sources in context
A document, signature, log and device may contribute to a combined reading. No isolated indicator determines authorship.
Correlation
Select a source to understand its contribution.
Structure, metadata and versions help contextualise a file and its transformations. Interpretation depends on the origin and availability of the material.
Signature mechanisms, certificates and authentication help explain formalisation. Analysis considers available evidence and the event context.
System records and timestamps may help establish an event sequence. A log does not automatically guarantee truthfulness, completeness or attribution.
Device information may contextualise records and authentication journeys. A device in isolation does not necessarily prove authorship.
Knowledge & tools
Technical synthesis
Technical Dossier
Evidence, method and decisions.
Ten themes connecting engineering, digital evidence, cryptoassets and technical expert practice.
Dossier themes
- Badenas practice
- Fraud and digital evidence
- Blockchain and cryptoassets
- Engineering and causation
- Expert strategy
Technical resources
Badenas Lab
Badenas Lab organises data, files, timelines and questions with local processing. Select a category, read the limits and keep the technical context under professional review.
Open Badenas LabServices
A service is the work or deliverable that may be commissioned. The appropriate combination depends on the purpose, object and limits defined for each matter.
- Strategic Technical Assessment
- Expert Technical Assistance
- Technical Opinion
- Technical Analysis
- Expert Questions
- Technical Investigation
- Technical Audit
- Evidence Preservation and Analysis
How it works
Each stage clarifies the next step without anticipating conclusions or requesting sensitive material before an appropriate channel is established.
- 1. Describe the problem — No attachments or sensitive data in the first contact.
- 2. Initial framing — Identify the object, purpose and urgency.
- 3. Define the scope — Establish what must be analysed and which elements are necessary.
- 4. Proposal — Scope, procedure and conditions.
- 5. Secure channel — Sensitive material only after the engagement has been properly defined.
- 6. Technical work — Apply the method and record the analysis.
- 7. Delivery — Technical opinion, expert report, technical note or support corresponding to the scope.
Responsibility
Alan Badenas dos Santos — Engineer | Court Expert | Technical Consultant · CREA-PR 185062/D · IBAPE-PR associate no. 1338.
Technical responsibility
Experience
- Responsável técnico: Alan Badenas dos Santos
- CREA-PR 185062/D
- Associado ao IBAPE-PR nº 1338
Next step