Acquire
acquire is a tool to quickly gather forensic artifacts from disk images or a live system into a lightweight container.
This makes acquire an excellent tool to, among others, speedup the process of digital forensic triage.
It uses dissect to gather that information from the raw disk, if possible.
acquire gathers artifacts based on modules. These modules are paths or globs on a filesystem which acquire attempts to gather.
Multiple modules can be executed at once, which have been collected together inside a profile.
These profiles (used with --profile) are full, default, minimal and none.
Depending on what operating system gets detected, different artifacts are collected.
The most basic usage of acquire is as follows:
user@dissect~$ sudo acquire
The tool requires administrative access to read raw disk data instead of using the operating system for file access.
However, there are some options available to use the operating system as a fallback option. (e.g --fallback or --force-fallback)
For more information, please see the documentation.
Requirements
This project is part of the Dissect framework and requires Python.
Information on the supported Python versions can be found in the Getting Started section of the documentation.
Installation
acquire is available on PyPI.
pip install acquire
Build and test instructions
This project uses tox to build source and wheel distributions. Run the following command from the root folder to build
these:
tox -e build
The build artifacts can be found in the dist/ directory.
tox is also used to run linting and unit tests in a self-contained environment. To run both linting and unit tests
using the default installed Python version, run:
tox
For a more elaborate explanation on how to build and test the project, please see the documentation.
Contributing
The Dissect project encourages any contribution to the codebase. To make your contribution fit into the project, please refer to the development guide.
Copyright and license
Dissect is released as open source by Fox-IT (https://www.fox-it.com) part of NCC Group Plc (https://www.nccgroup.com).
Developed by the Dissect Team (dissect@fox-it.com) and made available at https://github.com/fox-it/acquire.
License terms: AGPL3 (https://www.gnu.org/licenses/agpl-3.0.html). For more information, see the LICENSE file.
1 maintainer
Metadata
1 maintainer
Release files for acquire 3.22
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| acquire-3.22.tar.gz | 95.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| acquire-3.22-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 182.5 kB
Release files / acquire-3.22.tar.gz
| Download URL | acquire-3.22.tar.gz |
|---|---|
| Size | 95.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b83f95673433fb10065eb2afe3d16d0e14b77ee567b35762dc6d94614755851f
|
|
BLAKE2b-256 checksum How to use checksums |
0dd8e90c7bfbb1d010732f91cc6f738ebb4e4f5c5749f7f5ba44ce69456ec7de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 25, 2026.
Transparency logRelease files / acquire-3.22-py3-none-any.whl
| Download URL | acquire-3.22-py3-none-any.whl |
|---|---|
| Size | 87.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4025c030571db4b7e25f90a6a8ac0cf18922379672c028ad58e8abd9e71ac38c
|
|
BLAKE2b-256 checksum How to use checksums |
ca3559483058f7f62991d0b793faa66325d5b61d00c6eb3b078cf7c9bd841ee1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 25, 2026.
Transparency log
