Just released version 0.5.4 of XWFIM.

Changelog:

Change: Renamed Settings.bin to xwfim.bin since people seemed to run both XWFIM and XWFRT from same directory and this caused problems
Change: Updated book cover image and URL when clicking on the book image
Change: Delete any old viewer directories before unzipping a new version to avoid file inconsistencies across viewer versions

 

If you get a crash about "key not found" or similar, delete settings.bin and restart. Prior to this release, both XWFIM and XWFRT used the same file, settings.bin, to store configuration data. If you can both programs from the same directory this would cause issues.

 

This update will download automatically once you start XWFIM. Click the lower right corner of the application for details.

"This book is going to be great!  The essential, accessible answer to the impenetrable density of XWF's help file". – Craig Ball

There’s been more than few tweets about having to wait until October, but don’t worry, we are ahead of that schedule.    The most current target date for printing is September 3.



The book is now in the hands of trusted reviewers and so far, the comments have been really positive.  So much so, that even those who have used XWF for years learned tips and tricks from even the first chapters of the book.

There are a number of XWF users who started from the first versions of XWF and even went to the first XWF courses (back in ’05…).   For these XWF users, the learning curve was short.  New tool, new training by the developer, no problem.  For everyone else purchasing a dongle and trying to maneuver around a program that doesn’t look like any other they use is a different story.  I'm sure 'different' could be replaced with 'frustrating'.

But with this book, new and not-so-new XWF users will have everything needed to use XWF as their primary tool (or even as the secondary tool that always works when the others fail).

Here are some benefits from the book, maybe you fit in one or more of these.

-Non XWF user:  Haven’t tried it, like what I’m using already (even if I complain about it), and don’t have the time to learn a new tool.  I don't even want to learn another tool.  However, since there is so much talk about X-Ways, I’ll try it and check it out.

-New to forensics:  I haven’t got a clue which tool to start with, but XWF sounds like it works and fits my budget!

-Current XWF user:  I have used XWF for years and think I got it down.  Then again, I still don’t use it as a primary tool and wonder how anyone does that.  I can use some tips on how XWF does more because I'm not totally confident in using XWF.

-Forensics instructor:  I spend more time teaching the tool than forensics.  A student guide would save time in the class better spent teaching forensics instead of software use.

-Expert forensics analyst:  I want the most indepth, powerful, fastest, and configurable forensic tool available!

If you have concern that the book will be outdated soon, don't worry.  The material covers the vast majority of XWF features in detail.  Any new item that is added as an update doesn't change the information in the book, it only adds a new capability.  Once you know the tool, the updates that are put out almost monthly are awesome.

As in, the book is done, no more to add, it's all done.   It's now in the hands of the publisher to proof, print, and distribute.   Accuracy checked by Stefan Fleischmann (developer of X-Ways Forensics),  Tech Edited by Jimmy Weg (an expert X-Ways user and superb tech editor), and written by Eric Zimmerman (who I have found to be a great writer and even better X-Ways master) and myself, this is the book to have.  Refresh what you learned in an X-Ways course or learn by reading.   Having used X-Ways since the first release, this is a book I whole-hardheartedly recommend.


Order the guide now by clicking the book image.

 

We made a change with the case studies in the book, which some may not like...we didn't do the case studies chapter.

Actually, we spent a lot of time trying to write up case studies, only to find that we were spending more effort and writing on the "how to do forensics' rather than the 'how to use XWF'.   As an example, writing about malware analysis with XWF requires a book by itself.

However, we have managed to provide case flow examples with electronic discovery, consent searches/triage, live response, and a myriad of specific examples of how to use XWF in different situations that can be put to use in just about any type of case.  This is on top of going through XWF with a fine tooth comb explaining every nook and cranny to either use XWF with speed and minimal user intervention (as close to a one button approach possible) through the most granular configuration as you want to have in a forensic application.

The layout and organization is simple, to the point, and the information is easy to find (index, appendix, and lots of screenshots).    It will be a required reference book on your desk if you are a user of X-Ways Forensics, whether you started using XWF from its first release or if your first XWF dongle just arrived yesterday.  For anyone that teaches forensics using XWF, you may want to consider this book as required reading for your students to save you a lot of class time teaching 'how to use XWF' in class in order to focus on teaching forensics.

All chapters are done, the writing is over, and the XWF Guide is just a few steps away from being put on paper (proofing, setting, and printing is all that is left).



Having re-read the book, it is something I would have liked to have had when starting to use X-Ways Forensics in the beginning and while using it on cases.

Yep!  Not only is WinFE still a viable project, it is being taught in more places, more often, to more people.  For example:

The FAA: FAA78100041, (78100041) Creating a Windows FE DVD

Search at the Child Abuse and Family Summit in Oregon.


HTCIA at a training session in Washington (state).

Another HTCIA here (with instructions to build a WinFE).

And a few conferences too.

This does not include a varied assortment of in-service training on WinFE that I have been asked for help in either reviewing or creating training programs for WinFE from a few US Federal government agencies and about a dozen local/state agencies, just only during the past year.

There's also more instructions available online for creating a WinFE, like: http://4nzx.blogspot.com/2012/11/creating-winfe-boot-disc.html

http://megadeus.com/?p=91

 

and

https://www.youtube.com/watch?v=Dy27R34MDkE

So is WinFE a viable addition to your forensic toolbox?  Sure is.  Just ask anyone that uses it.  One thing to consider about WinFE is that the development of WinFE isn't in "new" features or capability.   It is only a boot disc.  The key factor that no other boot disc can compare, is that it boots to Windows...and it boots forensically.  The fact that you (or anyone you train) can use Windows, forensically, to triage or preview potential evidence is something amazing.

Linux is good too.  But when your entire department (or agency or group) works in Windows every day, as they have been for the past decade or longer, you don't have to teach a new (to them) operating system.  You only have to teach how to boot to a CD/DVD/or USB.

Because of that, virtually anyone can boot a suspect's machine (even a terrorist's computer!) and find the low-hanging fruit of evidence in MINUTES without having years of digital forensics training.  Like I've said before, Troy Larson's simple registry modification was ingeniously simple.  Creating an automated process with WinBuilder took it a step further to get it in the hands of more people. And Colin Ramsden's write protection GUI app made it easy for anyone.  What more could you ask for?

 

 

Regarding a post on twitter asking if training from X-Ways is worth it or just buy the book, I’d have to say taking the training is a good solution.  And so is buying the book.

I favor training for almost everything (easier to learn from other’s mistakes…).  I also favor reading to self-learn and as a reference when needed. 

I’ve personally taken XWF training on more than one occasion, and know others that have taken the training more than that.  Each time, there is something new that you learn, just like with any class I’m sure.  I did not regret taking the training as it did make the transition to XWF easier.  Although, if there were a book on XWF at the time, I would have bought it and still went to training.

I think it comes down to (1) time, (2) money, and (3) self-learning ability.  If you can afford the training and afford the time off from work, why not take the training?  You can still buy the book for a reference because you will most certainly like to have it when using XWF.  But, if the cost of training, loss of time (vacation or you just need to get things done at work) is too much, you will still learn a lot with the book, more than enough to competently use XWF.

We have written the book (working on the last chapter now…) in a manner that if you have not taken the training, you will be able to use XWF, in a step-by-step instruction, including how to use in specific types of cases.  It is also written as a reference guide.  Need to know what shortcut opens the directory browser window? We have a section on all shortcuts?  Need to know the different ways to create an image, or container, or skeleton image? We have a chapter on that?  Curious what a specific checkbox selection does?  We have that detailed.  Need to know how to use XWF in ediscovery? We have something on that too.  So, for those that like to tinker with software to learn how to use it, meaning…pushing buttons to figure it out, this book is for you.  Some like sitting in a class.  Some like figuring it out themselves.  As far as the training put on by X-Ways, they do a good job and you get your money's worth with the amount of information.   They do not stretch 8 hours into a week.  They cram 40 hours of information into 20 hours.

Just posted 0.0.5.3. This fixes a few issues related to checking for new versions when more than one zip file exists as they often do when it comes to prereleases.

 

If you get an error about "more than one element" on startup, dont sent the error report, do not exit, then proceed to update using the built in updating feature. Worst case just redownload it from XWF website and it should be fixed.

 

Here are some of the case studies we are working on for our current and last chapter:

• Electronic Discovery (IP theft, document collection, contract antedating)
• Consent Searches (triage/preview)
• Parole Searches (triage/preview)
• Malicious Software
• Intrusion
• Fraud
• Child Pornography
• Cell phone analysis

Several of these are being submitted by contributors, and all are to be detailed using XWF and suggested case flow processes.  Contributors to be duly noted (as much as they allow).

Here is a new X-Tension for XWF that does a few neat things, such as searching for specific files and adding them to the report table, and exporting files for external analysis: http://www.gaijin.at/en/xtmultifilefinder.php

 

We are starting the last chapter (Case Studies) and have a few contributors already for case examples.  We'll gladly take more as we want to have a wide range of case studies using X-Ways.

For everyone waiting, we are finishing the book much earlier than we had planned, only because it has been a smooth process with the authors (Brett and Eric), the Tech Editor (Jimmy), and publisher (agreeing to push up the schedule to keep up with us!).

We've also had offers of translating the book into other languages, and are visiting that topic.  So far, maybe French...suggestions for others?

Be sure to keep up on the progress of my second book (X-Ways Forensics Practitioner's Guide) at https://xwaysforensics.wordpress.com/.  Eric Zimmerman and I are on the last chapter!

After the book is done, I have a few new things to test and post about WinFE to update the old, bring in the new.

Don't get excited, there isn't a solution to Windows RT or Secure Boot and WinFE (yet!).  But for those working on it, here are two links of interest that help explain a few of the technical details.

 http://www.uefi.org/learning_center/

The UEFI secure boot specification is owned by the UEFI consortium, not Microsoft, so the consortium documentation and specification sets out the real rules of the road for working with UEFI.

http://noggin.intel.com/content/the-flow-of-booting-an-intel-architecture-system

This information was sent to me by the Yoda of WinFE.

We are WAY ahead of our planned writing schedule, mostly because of the XWF Guide writing and editing team are getting things done, fast.

With that, we are reaching the Case Studies chapter, where we will give specific case flow and XWF usage by the type of case.  That means, we have a section on "How to Use XWF on a Child Pornography Case" and "How to Use XWF in an Electronic Discovery Case", and more.



For this chapter to be of most use to the most number of readers, please give us what type of cases you want us to cover.  PLUS, if you have used XWF in a case that worked well, send us your (sanitized) case study and we will add it to the chapter.  Depending on how you'd like credit, we can credit you with the specific case ("case study submitted by ...."), or generically ("so and so" contributed to the case studies chapter), or not at all if you want to remain in the background with a case study.

Don't forget to follow us on Twitter to keep up with the book's progress.  It's going fast and you don't want to miss out.

I can also say that although I felt I was competent XWF user (since 2004!), the research, testing, and delving in XWF for this book opened my eyes to more capabilities of XWF that I never imagined.  You won't be disappointed and after reading this book, you will be using that green XWF dongle a lot!

Chapter 4 is wrapping up! We each have one more chapter to go and then we start the case studies.

The table of contents page is updated to reflect the topics of each chapter and, for the completed chapters, the page and word count of each.