Forensics and Cyber Threat Research Area

Threat Intelligence | Insider Threat Detection | User Behavior Analytics | Cyber Threat Management | Data Security Intelligence | Cloud Security Intelligence Application Security Intelligence | Anomaly & Pattern Detection |  Security Information Event Management | Digital Forensics | Data Recovery | Malware Investigation | Packet Analytics | Packet Forensics | security operations and analytics platform architecture (SOAPA)

Computer Forensics Evidence And Capture Data Recovery

Home » Blog » Computer Forensics Evidence And Capture Data Recovery

 Posted in Digital Forensics

Computer Forensics Evidence And Capture Data Recovery

   6th December 2015  Leave a Comment on Computer Forensics Evidence And Capture Data Recovery 0 997

Computer Forensics Evidence And Capture Data Recovery

Project Name: Computer Forensics Evidence And Capture Data Recovery

Description: This blog will help all forensics investigator for Evidence Collection and Data Seizure

Author: Rohit D Sadgune

Frequently Asked Question on Computer Forensics Investigation

  • Checklist of Computer Forensics Evidence And Capture Data Recovery

 

  1. Make sure you are ready and have procedures in place for disasters like floods, tornadoes, earthquakes, and terrorism when they strike.
  2. Make sure you are ready and have a plan in place to take periodic image copies and send them off-site.
  3. Perform change accumulation to reduce the number of logs required as input to the recovery, which saves time at the recovery site. However, performing this step consumes resources at the home site.
  4. Evaluate your environment to decide how to handle the change accumulation question/problem in action/task
  5. Have procedures in place to implement your plan.
  6. Check your assets to make sure they’re ready as part of your plan.
  7. Build your recovery JCL correctly. JCL is tricky, and you need to get it exactly right. Data integrity and your business rely on this task.
  8. Clean your RECON data sets. It can take hours if done manually, and it’s an error-prone process. When your system is down, can you afford to make mistakes with this key resource?
  9. Test your plan. There’s a lot to think about. In the real world, there’s much more.
  10. Make sure your plan works before you are required to use it.
  11. Have procedures in place to deal with issues of increased availability, shrinking expertise, growing complexity, failures of many types, and the costs of data management and downtime.

GO BACK TO COMPUTER FORENSICS CHECKLIST

Author: Rohit Sadgune
Core Working Areas :- Threat Intelligence, Digital Forensics, Incident Response, Fraud Investigation, Web Application Security Technical Certifications :- Computer Hacking Forensics Investigator | Certified Ethical Hacker | Certified Cyber crime investigator | Certified Professional Hacker | Certified Professional Forensics Analyst | Redhat certified Engineer | Cisco Certified Network Associates | Certified Firewall Solutions | Certified Network Monitoring Solution | Certified Proxy Solutions
Website

Leave a Reply

Your email address will not be published. Required fields are marked *

Enter Captcha Here : *

Reload Image

Indicator of Attacks | Indicator of Compromise

Top SIEM Use Cases | Threat Hunting Hypothesis | Deep Packet Inspection | Insider Threat Hunting | Hunting Data Exfiltration | Banking Fraud | ATM Use Cases | Cross Channel Data Exfiltration | Hunting Endpoint Anomaly | Denial-of-service | Man-in-the-middle (MitM) attack | Spear phishing attacks | Drive-by attack | Eavesdropping attack | Birthday attack