Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to create traditional forensic images #147

Open
hiddenillusion opened this issue Jun 12, 2020 · 1 comment
Open

Ability to create traditional forensic images #147

hiddenillusion opened this issue Jun 12, 2020 · 1 comment
Labels
AWS Issues related to AWS

Comments

@hiddenillusion
Copy link

The current code/examples stop at attaching volumes to forensic instances. Since not all forensicators would be analyzing the attached volumes from within the forensic instances, having the ability to create a traditional forensic image (e.g. via dd , ewfacquire etc.) would be valuable.

There're some obvious limitations to this approach (e.g. inability to automount some attached volumes) but any help in being able to automatically handle some % of the use cases would be beneficial.

Regarding AWS, a typical scenario would be to image said attached volume then copy it to an S3 bucket, which would require #135

@giovannt0 giovannt0 added the AWS Issues related to AWS label Jun 20, 2020
@Gfuen
Copy link

Gfuen commented Oct 27, 2024

Can I get assigned to work on this issue after signing the Google Individual Contributor License Agreement for code contributors?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AWS Issues related to AWS
Projects
None yet
Development

No branches or pull requests

3 participants