Comments on: BIO http://mobileforensics.wordpress.com Cell Phone Forensic Tips, Tricks and Tutorials Wed, 11 Nov 2009 22:57:20 +0000 http://wordpress.com/ hourly 1 By: J. Oquendo http://mobileforensics.wordpress.com/bio/#comment-957 J. Oquendo Sun, 12 Oct 2008 19:38:21 +0000 http://mobileforensics.wordpress.com/bio/#comment-957 FYI, you may want to re-word this on your "Blackberry Forensics" blog: I recommend making a working copy and a archive copy. Now reseal and store your exhibit. Recommend? That's a mandate period. "After you've made a working copy and an archive, reseal and store your exhibit" Remember, the key is to keep evidence as taint free as possible while obtaining bit by bit copies for analysis afterwards. Your message can be misinterpretted by newcomers to forensics where one small mistake such as working on a live copy can render that evidence useless. Sincerely Jesus Oquendo http://www.linkedin.com/in/voipsec FYI, you may want to re-word this on your “Blackberry Forensics” blog:

I recommend making a working copy and a archive copy. Now reseal and store your exhibit.

Recommend? That’s a mandate period.

“After you’ve made a working copy and an archive, reseal and store your exhibit”

Remember, the key is to keep evidence as taint free as possible while obtaining bit by bit copies for analysis afterwards. Your message can be misinterpretted by newcomers to forensics where one small mistake such as working on a live copy can render that evidence useless.

Sincerely
Jesus Oquendo
http://www.linkedin.com/in/voipsec

]]> By: Javier Martinez http://mobileforensics.wordpress.com/bio/#comment-906 Javier Martinez Tue, 11 Mar 2008 20:44:29 +0000 http://mobileforensics.wordpress.com/bio/#comment-906 Michael, We fixed the bug you identified in your blog. Can you please make the necessary corrections in the blog. It is stating we have not taken care of this bug. Susteen acted immediately to correct the issue and solved it within 72 hrs once we knew of the issue. Thank you, Javier Michael,
We fixed the bug you identified in your blog. Can you please make the necessary corrections in the blog. It is stating we have not taken care of this bug. Susteen acted immediately to correct the issue and solved it within 72 hrs once we knew of the issue.

Thank you,

Javier

]]>