-
|
Dear digital forensics enthusiasts! I found out about IPED from an Interpol newsletter. I work for the State Police of Latvia and I demonstrated the capabilities of IPED to my colleauges and everyone was very impressed. We all would like to send a big thank you to everyone involved in this project, thank you for making something like this possible. I know you guys are not techsupport but I do not know whom else to ask, so I am really hoping that you could help us out a little bit. I am examining couple of servers with IPED. I finished the 1st server, gave the portable case to investigators and they were super happy I still have 5 servers to go. Since there is Hyper-V Replication enabled on these servers I want to process the next server using the hashes from the previous one to ensure that more or less unique information is included in the new portable case. So far I have tried the following:
java -jar ~/Apps/IPED/target/release/iped-3.17.1/iped.jar -d /media/RAID/1.Apskates/XXXX_serveri/XXXX/vhdx_to_vhd/XXXX-data.vhd -l /media/Skyhawk10TB/1.Apskates/XXXX_serveri/XXXX_srvs_keywords_v2.txt -o /media/Skyhawk10TB/1.Apskates/XXXX_serveri/XXXX/iped_XXXX_vol1 -tz GMT+2 -profile forensic -importkff /root/Documents/hash_base_XXXX/NIST_NSRL/NSRLFile.txt ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. I am using a Linux system and I am comfortable working with the commandline, however I am fairly new to forensics. I will greatly appreciate any help on how I can get IPED to recognize my hashes and ignore them Kind regards and wishing you all a wonderful day ahead, Dāvis |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 5 replies
-
|
Hi @reacan, thank you for your interest in IPED tool! No problem asking here for now, currently we don't have a user channel, possibly we will create an user mailing list so the community could help users. Did you read the wiki about importing NSRL hashset format? It must be done alone before processing: https://github.com/lfcnassif/IPED/wiki/User-Manual#NIST-NSRL You should give your hashset a "ProductName" in NSRLProd.txt file (just this and NSRLFile.txt file are used in importing step). Finally, go to IPEDConfig.txt and turn excludeKffIgnorable on. Actually conf/KFFTaskConfig.txt lists alert product names, not ignorable, you don't need to edit it. Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, Luis, for getting back to me. I did not read that manual page, but now that I have, it starts to make sense :) I will try my luck with getting it to work! I think soon more and more people will start using IPED. The tool is very powerful. Recently I processed an image containing an APFS FileVault encrypted partition providing the password in the processing options and IPED handled it very well to say the least :) |
Beta Was this translation helpful? Give feedback.
-
|
You are welcome! |
Beta Was this translation helpful? Give feedback.
-
|
I managed to get it to work, the instructions were perfectly clear, thank you very much. I also managed to add my own hash database, however the solution is not elegant at all. I wrote this oneliner:
then I created a corresponding NSRLProd.txt and it worked, got the hashbase imported. I am wondering which columns in the NSRLFile.txt are not critical for IPED to be able to perform known hash look up? I only have MD5 enabled in the processing options, if I create my NSRLFile.txt with static information in all the other fields except MD5, FileName, FileSize, will IPED be able to correctly ignore known hashes? The columns in the NSRLFile.txt are: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @reacan, reading the (old) source at https://github.com/lfcnassif/IPED/blob/master/iped-engine/src/main/java/dpf/sp/gpinf/indexer/process/task/KFFTask.java Tip: you can search for or group by (in metadata tab) kffgroup property, your known files will have the value specified in NSRLProd.txt file |
Beta Was this translation helpful? Give feedback.
-
|
Hi @lfcnassif, thank you for the insight! I'll do some testing today and I'll report back on what I come up with, maybe it will be useful for someone. |
Beta Was this translation helpful? Give feedback.
-
|
Closing for now. If you still have problems with NSRL importing, please reopen. |
Beta Was this translation helpful? Give feedback.
Hi @reacan, thank you for your interest in IPED tool! No problem asking here for now, currently we don't have a user channel, possibly we will create an user mailing list so the community could help users.
Did you read the wiki about importing NSRL hashset format? It must be done alone before processing: https://github.com/lfcnassif/IPED/wiki/User-Manual#NIST-NSRL
Let me know if the docs are not clear.
You should give your hashset a "ProductName" in NSRLProd.txt file (just this and NSRLFile.txt file are used in importing step). Finally, go to IPEDConfig.txt and turn excludeKffIgnorable on.
Actually conf/KFFTaskConfig.txt lists alert product names, not ignorable, you don't need to edit it.
H…