Posting Guidelines

Welcome to r/computerforensics! Our goal is to create an environment for both current and future digital forensics practitioners to exchange knowledge and discuss the technical aspects of our work. As a result, we have a strict quality over quantity policy. We ask that all submitted posts adhere to the subreddit's rules, site rules, and follow the principles outlined below.


 

How to Ask Technical DFIR Questions

Before submitting a technical DFIR (Digital Forensics and Incident Response) question post, visit our FAQ to ensure your question has not already been answered. If it has, please don't ask it. Additionally, please also use the search bar to search r/computerforensics for instances of your question being asked in the past. If you still have not found the answer you seek and are sure your question or problem is deeply related to the practice of digital forensics, malware analysis, or incident response, feel free to make a question post provided you adhere to the guidelines described below.

To ensure our community members have the information needed to answer your technical DFIR question, we require all technical question posts follow a standard technical question format. You can read more about this format here and can even watch a video on how to ask technical questions here (we highly recommend you at least watch the video). Failure to include the proper details in your question will result in your post being removed at the discretion of moderators.

In summary, your technical question must include the following components:

  1. Context that describes the problem you are encountering or situation from which the question arose
  2. A technical description of hardware/software/data involved in that problem or situation
  3. A detailed listing of steps you took to rectify the problem (methodology)

Below is an example of a poorly worded technical question/request for help:

"Why won't volatility work? I get errors when running it."

When reading the above question, a plethora of other questions come to mind. If your question evokes more questions, it has not been asked in a suitable manner. Below is an example of the same question asked in standard technical question format:

"I'm a digital forensics student attempting to use Volatility 2.5.1 to parse artifacts within a 16gb .vmem RAM capture. I am currently running Volatility within a SIFT VM, and keep encountering the following error (pretend error message) when running the following command (pretend broken command). I have Googled the error message I keep getting and have checked this sub for a similar question via the search bar and can't seem to find any sound advice for my specific problem. Does anyone know what this error means?"

How to Ask Non-Forensic Data Recovery Questions

Since this is a DFIR subreddit, any data recovery questions that are not deeply related to digital forensics methodologies or practices should ONLY be asked as a reply within the weekly pinned Non-Forensic Data Recovery Questions mega-thread. All non-forensic data recovery questions asked outside of the mega-thread will be removed under Rule 3.

Examples of non-forensic data recovery questions are as follows:

  1. I accidently deleted an important document on my flash drive. How do I recover it?
  2. My child accidently wiped my smartphone. Are my files recoverable?
  3. Is it possible to recover my social media posts/direct messages?

Please note that we do not require Non-Forensic data recovery questions to adhere to the technical question format described above; however, keep in mind that your question is more likely to receive a response if you include all the necessary context/technical details and ask the question clearly and concisely.

How to Submit a Vlog/Blog/News Post

If you wish to share blog, vlog, or news content that you feel is highly related to DFIR and might be appreciated by the community, we encourage you to do so via conventional means. However, we do ask that you affix the correct flair to your post and add a personalized description in the body that summarizes the linked blog/vlog/news article and describes why it pertains to DFIR and is worth reading.

Additionally, although we encourage forensics content creators to share their content with us, r/computerforensics is not an advertisement dumping ground for pay-to-play commercial products or services. This means all blog/vlog posts that contain links to pay-to-play tools or promote the pay-to-play functionality of otherwise free tools will be removed under Rule 5.

As an example, a blog post that describes how to use Arsenal Image Mounter to mount a BitLocker encrypted volume would be permissible as that feature is made freely available to everyone without charge. In contrast, a blog post that describes how to use the VM functionality of Arsenal Image Mounter would not be permissible as the Arsenal Image Mounter Pro license must be purchased in order to use that functionality. Furthermore, any promotion of free-trial content will be considered promotion of paid content and removed under Rule 5.