A free, community-sourced, machine-readable knowledge base of forensic artifacts that the world can use both as an information source and within other tools.
If you'd like to use the artifacts in your own tools, all you need to be able to do is read YAML. That's it. No other dependencies. The python code in this project is just used to validate all the artifacts to make sure they follow the spec.
The ForensicArtifacts.com artifact repository was forked from the GRR project artifact collection into a stand-alone repository that is not tool-specific. The GRR developers have migrated to using this repository and make contributions here. In addition the ForensicArtifact team will begin backfilling artifacts in the new format from the ForensicArtifacts.com website.
For some background on the artifacts system and how we expect it to be used see this blackhat presentation and youtube video from the GRR team.
The term artifact (or artefact) is widely used within computer (or digital) forensics, though there is no official definition of this term.
The definition closest to the meaning of the word within computer forensics is that of the word artifact within archaeology. The term should not be confused with the word artifact used within software development.
If archaeology defines an artifact as:
something made or given shape by man, such as a tool or
a work of art, esp an object of archaeological interest
The definition of artifact within computer forensics could be:
An object of digital archaeological interest.
Where digital archaeology roughly refers to computer forensics without the forensic (legal) context.
The artifact definitions are in the definitions directory and the format is described in detail in the Style Guide.
Please send us your contribution! See the developers guide for instructions.
- ForensicsArtifacts.com ... the definitive database
- GRR Artifacts, by Greg Castle, Blackhat 2014