Home // FORENSIC UNITS // LITIGATION AND BUSINESS

Information Security and Compliance

Forensic examinations and audits in corporate environments: technical inquiry into internal fraud, IT contracts and projects, software licensing and digital assets, with documented evidence and a method that withstands adversarial scrutiny.

The nature of the work

Corporate forensic examination, not off-the-shelf consultancy

Under the label of compliance, the market offers standardised adequacy programmes that promise conformity within a few weeks. This forensic unit does something else. The work here is forensic: examining systems, contracts, records and devices in order to establish facts capable of supporting a decision, be it dismissing an employee for cause, terminating an IT contract, responding to a software audit notice or closing an acquisition.

That is why this forensic unit does not promise conformity. Conformity is a state that depends on the continuous conduct of the company; what forensic examination delivers is different and, in a dispute, worth more: the technical and documented demonstration of what happened, of who did what, and of what the records actually prove.

The method comes from computer forensics: preservation of the evidence before any analysis, cryptographic hashing, chain of custody under arts. 158-A to 158-F of the CPP (Brazilian Code of Criminal Procedure) and ABNT NBR ISO/IEC 27037, and conclusions confined to what the evidence supports. The difference lies in the setting: here the object is the company, its systems, its contracts and its people.

Those who turn to this forensic unit are usually the legal department, the board, the audit committee or the law firm advising the company: someone who needs an impartial technical answer before taking an expensive decision.

From protection to audit: information security with forensic method
e-Discovery and fact-finding

Finding, among millions of files, the ones that decide the case

Corporate litigation, regulatory investigations and international cooperation proceedings frequently require locating and producing electronic evidence scattered across mail servers, corporate systems, laptops and mobile phones belonging to dozens of custodians. Doing that without method means producing too much, exposing what did not need to be exposed, or producing too little and answering for concealment.

The work follows the ISO/IEC 27050 series framework, the international reference for electronic discovery, which organises the process into linked and documented phases. The result is a defensible body of evidence: every document produced has its origin, hash and processing trail on record.

IT contracts and projects

What was contracted, what was delivered, and the distance between the two

Technology projects fail often, and the contract alone rarely says where responsibility lies. Forensic examination reconstructs the project from the evidence: proposals, schedules, minutes, emails, support tickets, code and system logs.

ERP

Failed ERP implementations

A go-live postponed or disastrous, corrupted data migration, endless customisations. The examination separates what was the implementer's obligation, what depended on the client and what the product was never able to do, and sizes the breach in technical terms.

Contracts

Forensic examination of IT contracts

Item-by-item comparison between contracted scope and actual delivery: requirements, acceptance records, SLAs, schedules and technical evidence of operation. A basis for termination, claims, defence or well-founded renegotiation.

Systems

Audit of websites and systems

Technical examination of systems in production: how features actually work, availability, content published on a given date and adherence of what was developed to what was specified, with a record fit to support court proceedings.

M&A

Technology due diligence

Forensic assessment of technology assets in mergers, acquisitions and investments: ownership and quality of the code, licensing liabilities, critical dependencies and hidden risks that change the price of the deal.

Corporate investigations

From the report of wrongdoing to the document that supports the decision

The allegation arrives through the internal channel, from a manager or from a client: suspected fraud, misappropriation of funds, information leakage, conflict of interest, harassment documented by digital means. From then on, every wrong step is costly: accessing the computer of the person under investigation without formal preservation, confronting before collecting, inadvertently destroying what would have proved the wrongdoing.

A forensic inquiry begins with the silent preservation of the evidence: forensic images of corporate equipment, preservation of mailboxes and system logs, all with hashing and chain of custody.

The examination is impartial by definition: the commitment is to what the evidence shows, including when it clears the person under investigation. The final report documents method, findings and limits, and serves as the basis for the internal disciplinary procedure, for dismissal for cause, for a recovery claim or for a criminal complaint, according to the decision of the company and its lawyers.

The processing of personal data during the inquiry observes the limits of the investigative purpose, with access restricted to what is necessary and segregation of out-of-scope material.

Infrastructure and operations

Forensic diagnosis of the environment that sustains the business

Infrastructure

Forensic diagnosis of infrastructure

Documented technical survey of the estate: inventory of installed software and the corresponding licences, critical dependencies, single points of failure and business continuity risks. A faithful picture of the environment, backed by evidence, before it becomes the object of a dispute.

Licensing

Software licensing and infringement

Technical defence against audit and infringement notices sent by major software vendors: independent review of the vendor report, identification of counting inaccuracies and a technical basis for negotiation. Also in the opposite direction: investigation of irregular use of the company's own software.

Employment

Electronic time and attendance systems

Forensic examination of attendance records in high-volume employment claims: integrity of the clockings, processing and adjustments applied, consistency between the timesheet, the database and the working hours alleged. Mass analysis, with a method reproducible case by case.

Forensic readiness

Preventive forensic audit: can the company investigate the next incident?

Every company knows it may suffer an incident. Few know whether, when it happens, there will be evidence to establish what occurred. The answer depends on decisions taken long before: which records the environment keeps, for how long, in what detail and where.

The preventive forensic audit answers that question. It is not adequacy for certification or a conformity programme. It is a forensic examination of the environment, carried out with the method of an expert examination, which verifies whether the means exist to investigate a cyber incident or a fraud and, where they do not, where maturity needs to improve.

Evidence

Logs and retention

Which systems generate access logs, how long they are kept and whether they carry what the inquiry will ask for: user, time with time zone, source address and source port. A log that expires before the incident is discovered is evidence that does not exist.

Access

Identities and privileged accounts

Who has administrator access, how those accounts are used and whether their trail makes it possible to know who performed each action. Many attacks pass through them, and it is on them that the inquiry usually stumbles.

Exposure

Sensitive data out of place

Workstations and servers examined for data that should not be there. A critical finding reaches the company by formal preliminary notification, before the final report.

Controls

Anti-fraud controls

Whether the anti-fraud controls work in practice, and not just on paper: what they record, what they let through and where the process gaps are.

After an incident or a fraud, the same examination becomes a post-incident assessment. Identities, privileged accounts and logs are reviewed so that the next inquiry does not stumble on the same gaps. When authorship cannot be established for lack of records, the opinion says so frankly and brings the plan for the traces to exist next time.

REAL CASE · ANONYMISED

Hundreds of suspects and no source port

Challenge. A company that had suffered fraud through unauthorised access to its systems wanted to reach the perpetrator from the connection logs.

Method. The examination cross-checked the logs of the unauthorised accesses with the data supplied by the carriers and narrowed the list down to a few hundred suspects.

Outcome. The inquiry stopped there. The company did not keep the source port of the connections, and without it there was no way to separate the perpetrator from the other subscribers sharing the same IP address. A forensic audit carried out before the incident would have shown that gap in time.

Cyber insurance

Before the incident, so the insurer does not deny cover

The adjustment of a cyber claim depends on two things: the insured showing what happened, and the environment matching what the company declared when it took out the policy. If the environment keeps no records, or if the controls declared in the application questionnaire do not exist in practice, the denial of cover arrives precisely when the company most needs the insurance.

The forensic assessment carried out before the incident compares what the policy and the questionnaire presuppose with what the environment actually has. It points out the gaps in management and in IT controls which, in an incident, would sustain a denial. The company fixes them beforehand and reaches the claim with evidence.

If the incident happens, the examination carried out afterwards reconstructs the timeline with preserved evidence and delivers the information the insurer needs to adjust the claim.

ILLUSTRATIVE EXAMPLE

The denial found before the claim

A company takes out cyber insurance and declares, in the questionnaire, that all remote access uses a second authentication factor (MFA) and that access logs are kept for one year. Before renewal, it requests a forensic assessment. The examination finds administrator accounts without a second factor, a remote access server outside the inventory and logs that are erased within a few days. In an incident, each of those gaps could sustain a denial of cover. The company fixes the points, documents the fix and renews the policy with declarations that match the real environment.

How it works

The course of an inquiry

01 · ConsultationConfidential presentation of the problem and assessment of technical feasibility, at no cost
02 · ScopeWritten definition of the questions to be answered, the data sources and the limits of the inquiry
03 · PreservationForensic imaging and freezing of the relevant sources, with hashing and chain of custody
04 · ExaminationTechnical analysis on copies, with a record of every procedure applied
05 · ReportExpert report or technical report with method, findings and limits, fit to support a decision or court proceedings
06 · Court supportClarifications, supplementary questions to the expert and party-appointed expert support should the case turn into litigation
Completed cases
ANONYMISED CASE

Internal investigation of misconduct at a large manufacturer

Impartial technical inquiry with chain of custody control. The report provided the grounds for the internal disciplinary procedure.

ANONYMISED CASE

Defence against a software infringement notice from a major international vendor

An audit of the vendor report identified technical inaccuracies. Technical negotiation reduced the amount originally claimed by 60%.

REAL CASE · ANONYMISED

Card numbers in plain text

Challenge. A company wanted to know whether customers' card data was circulating outside the authorised systems, on the workstations of the sales department.

Method. Examination of the workstations, with preservation and chain of custody, looking for sensitive data outside the authorised systems.

Outcome. Card numbers were stored in plain text on the workstations. The company received a formal preliminary notification before the final report.

Frequently asked questions in this area
Does this forensic unit implement compliance programmes or LGPD adequacy projects?
No. The work here is forensic: establishing facts, examining systems and contracts and documenting evidence to support decisions and proceedings. Continuous conformity programmes are a matter of legal and management consultancy, conducted by the legal department or by dedicated advisers. The two worlds meet when the programme fails or is put to the test: that is the moment when forensic examination comes in. Nor is it an audit for certification: the preventive forensic audit verifies whether the company has the means to investigate an incident. (LGPD is the Brazilian General Data Protection Law.)
Can the insurer deny cover under a cyber insurance policy?
It is a real risk when the incident reveals that the environment did not match what was declared at inception, or when information is missing to adjust the claim. The assessment before the incident shows those gaps in time; the examination after the incident delivers the evidence the insurer asks for.
What if the audit finds something outside the scope?
The scope and the confidentiality of the work are defined in the proposal and in the confidentiality agreement. Incidental findings follow the applicable legal obligation.
What is e-Discovery and when does it become necessary?
It is the structured process of identifying, preserving, collecting, processing, reviewing and producing electronic evidence for litigation, a regulatory investigation or an arbitral proceeding, following the ISO/IEC 27050 series framework. It becomes necessary when the evidence is scattered across large volumes of emails, systems and devices belonging to multiple custodians, and the way it is produced may be challenged by the opposing party or by the regulator.
The ERP implementation failed. What can forensic examination demonstrate?
The examination reconstructs the project from the records: proposal, schedules, meeting minutes, emails, support tickets, acceptance records and the system itself. On that basis it separates the implementer's obligations, the dependencies that fell to the client and the limitations of the product, and shows in technical terms where the project broke down. That picture supports renegotiation, termination, court action or arbitration, according to the lawyers' strategy.
The company has received a software infringement notice. What is the first step?
Not signing any terms or replying to the notice before an independent technical review. Vendor audit reports frequently contain counting inaccuracies: decommissioned machines, licences not taken into account, metrics applied incorrectly. In an anonymised case from this forensic unit, the independent review reduced the amount originally claimed by 60%. The reply is built on the real inventory, not on the spreadsheet of the party making the claim.
How is an internal allegation investigated without contaminating the evidence?
By preserving before confronting. The evidence is frozen quietly: forensic images of the equipment, preservation of emails and system logs, with hashing and chain of custody. Only then do the analyses begin and, where appropriate, the interviews. The most common error in informal inquiries is the opposite: confronting first, giving both time and motive for the destruction of the evidence.
Does the inquiry report work as evidence in court?
The report is produced for that purpose: documented method, chain of custody, hashes of the evidence and conclusions confined to what the examination supports. Like all evidence, it is subject to adversarial scrutiny; the difference is that technically rigorous work withstands challenge, whereas an informal inquiry tends to fall at the first objection. Should litigation arise, the work continues as party-appointed expert support.
Is it feasible to examine thousands of electronic attendance records?
Yes, and it is precisely at that volume that method makes the difference. The examination combines automated processing of the complete clocking database with technical verification of integrity: adjustments, processing, gaps and patterns incompatible with spontaneous clocking. The result is reproducible claim by claim, which matters in high-volume employment litigation portfolios.
What does technology due diligence examine before an acquisition?
What the target company says it has and what it actually has: ownership of the source code, use of third-party components and their licences, commercial licensing liabilities, dependence on critical people and suppliers, and continuity risks. Hidden technology liabilities change the price of the deal, and it is cheaper to find them before signing.

See also

Computer Forensics →   For Companies →   Expert Reports and Technical Opinions →

Before the expensive decision, the technical answer

Dismissal for cause, contract termination, response to a notice, closing an acquisition: decisions like these call for evidence, not impressions. The initial consultation assesses the technical feasibility of the inquiry, on a confidential basis.

Confidential consultation
Representative cases

The level of work you are engaging

Before deciding, it is worth seeing what has already come through this laboratory: cases described without identifying the parties, in the format of challenge, method and result.

See all representative cases →

The technical evidence your case requires. The authority courts respect.

Initial feasibility consultation at no cost. Reply within 24h on business days.
Request an Examination