TLP:CLEAR/ Public site — no client information Remote · based in Spain · --:--Z
Home/Resources/Malware analysis and reverse engineering
Resources · Malware analysis

Malware analysis and reverse engineering

Sample intelligence, detonation environments and static analysis tooling. What you need to get from “we have something odd” to an indicator the SOC can use.

Before you detonate anything

A sample uploaded to a public service is a published sample. If it came from a client incident it may contain personal data, credentials or organisational identifiers, and uploading it can in itself constitute a notifiable breach. Analyse locally first; the public sandbox is for what is already public.

Incident response

Samples and intelligence

To find out whether somebody has already seen what you are looking at.

Detonation

Observed behaviour, with the caveats in the notice above.

Static analysis and reversing

When you have to open it up.

Environments

So you do not build it from scratch every time.

Last reviewed:

Start with the scope

A thirty-minute conversation is enough to determine whether the engagement makes sense, which type fits and what order of magnitude it carries. No cost, no commitment.

Open a conversation