Thinking of Writing a #DF/IR Book? Here’s a tip that may or may not work out for you.

I am very open on my opinions about writing books, specifically DF/IR books.  I encourage anyone who is thinking about writing a DF/IR book to write away and start right away!  The longer you wait, the more likely someone else will write the book you wanted to write.

Over the years, I have been asked questions about writing and I posted a fairly detailed blog post with my opinions.  Take into account that I am no JK Rowling, nor do I have dozens of books in print, and like anyone, my opinions are my own.

So, what is the writing tip that may or may not work out for you?

The tip is to decide whether you want to tell the world about the book you started or keep the project to yourself.  Here is my experience on this, with an example for both.

2010, Experience #1: 

Some years ago, I wrote two ‘papers’ on virtual machines and forensics.  I decided to write a book on virtualization forensics and mapped out a table of contents, and started the first chapter.  Before I sent out a proposal to publishers, I came across a post on www.forensicfocus.com by Diane Barrett in which she posted that she was writing a book on the same topic that I was (Virtualization and Forensics).   Totally coincidental and an obvious case of independent-invention (we both had the same idea, independently).  So…what did I do? 

I chose to not write “my” book.  Why write what someone else already publicly announced? That's be like making a Wonder Woman movie after hearing that someone else is already making a Wonder Woman movie.

2017, Experience #2:

My fourth and current book is titled Bitcoin Forensics: Investigating Cryptocurrency Crimes.  I did my due diligence in researching to see if any other book existed (it did not) and if anyone else was working on the same topic (no one that I could find online).  To make sure I wasn’t writing something that someone else was writing, I blogged it, tweeted it, and posted to online forums.  I even reached out to anyone who would be interested in contributing to the book and am fortunate to have some fantastic volunteer contributors, along with a super co-author.  So, what happened?

Well…one of the volunteer contributors who agreed to help with the book quit, then without a peep, proposed the same book to a publisher, got a book contract, and the book immediately went to pre-sale on Amazon.  Interesting enough, he wasn’t planning to write the book in the first place until after volunteering to help with this book.

Huh?

That’s right.  It happened.….at least he changed the title from "Bitcoin Forensics: Investigating Cryptocurrency Crimes" to "Cryptocurrency Forensics"....   

So, this is a tip for future writers that could be more like a warning if it doesn’t work.   If you plan on writing a DF/IR book, you’ll have to decide to either keep it a secret or tell the world.  Keep it a secret and maybe no one else is writing the same thing.  That’s a big chance to take because I can tell you, everyone is thinking about the same book to write that you are.  Not the best thing to have two closely identical books come out at the same time to the same (fairly small) audience.  

Or, you can publicly announce your book and probably someone else won’t intentionally take your idea and write it.  However, worst case, someone could offer to to help with your book, then run off and sneak in a book contract with another publisher...good grief.

I prefer telling everyone.  Why hide what you are working on?  Why hide the research you discovered?  I believe in sharing to help push us all forward, even if just an inch forward.  This is the way I have seen others do it and actually what I prefer.  I would regret having written an entire book, or even half a book, only to find that someone else was writing the same thing, which could have been avoided by simply announcing my intentions.  Then again, this happens....

And yes, I am still writing this book.  The team of contributors, tech editor, and co-author is simply awesome.

Rate this blog entry:
1
423 Hits

DF/IR Case Studies

I've made three case studies so far and will have a fourth up this week.  From the feedback I've asked in a short survey about the case study series, here are the results:

  • The case studies are beneficial, useful, and job relevant.
  • The presentation format works (weekly to bi-weekly case studies).
  • Length is appropriate (between 30 minutes to 1 hour).
  • Printed certificates of completion are important to 90% of the respondents. 

With that, I'll keep going and adding one or two cases a week, more if I find relevant cases to recent news.  Personally, I have always benefited from case studies.  I get reminders of how investigations are done, tips on how to do them better, and sometimes learn things that I should never do in cases that go sideways.  I can tell you that after being assigned to over 100 criminal cases a year for 10 years, you can never learn enough to improve.  Some things you can learn may be small but have a huge impact on your case. 

In Case Studies #3, the case was solved in 6 months.  This was an international investigation spanning several countries and multiple states in the USA, with anonymity services used by the suspect.  I know that the investigators involved in the case used everything at their disposal to figure it out and all it took was a few little things to crack it open.  This is what case studies is all about.

I mentioned at the start of the Case Study series that I would have a short-run promo occasionally to entice more DFIRrs to start a habit of reviewing cases and continually be in some sort of training.  This time, the promo includes the Placing the Suspect Behind the Keyboard Course.  The Placing the Suspect Behind the Keyboard Course is 13-hours of the tactics, methods, and procedures to do the things that are being done in cyber cases today, in both the criminal investigation world and the private security world.  I'm giving it FREE with the Case Study series, but I'm limiting registrations to only 100 or Friday Nov 17, whichever comes first.

If you didn't need another reason for these courses, keep in mind that you should be doing case studies anyway, but when you do them by yourself, the only documentation you will have is that which you jot down on a piece of paper.  I'm keeping track of the hours you spend when you complete the each course and case study, and you can print it out for your records.  Take advantage of professional development when you can get it because you should constantly be improving your skills by doing something everyday: reading, courses, coding, practicing, teaching, something/anything. 

Register here to get the promo price of $75 for both the Case Studies Series and Placing the Suspect Behind the Keyboard course (promo code "cs-psbk"):

http://courses.dfironlinetraining.com/series/case-study-series-and-placing-the-suspect-behind-the-keyboard-training-bundle?pc=cs-psbk 

 

Rate this blog entry:
1
132 Hits

The last thing we want in DF/IR is the first thing we need in DF/IR (aka: regulations...)

    As teenagers, we never liked rules growing up. Curfews. Chores. Homework.  But we know now that the rules were good for us.   It seems like nothing has changed for those of us in the DF/IR field.  We don’t particularly want to be regulated simply because, like when we were teenagers, we know what is best for us. 

    The DF/IR field, as it stands today, is practically the Wild Wild West.  We have few regulations outside of obtaining a business license. In some states, we might need a PI license, but that is about the most regulated we get today.  It’s freewheeling at the moment without any government intervention. What a great time to be in DF/IR!

  •  Licensing requirements? Nope.
  • Training requirements? Nope.
  • Education requirements? Nope.
  • Certification requirements? Nope.
  • Experience requirements? Nope.
  • Testing requirements? Nope.
  • Annual update requirements? Nope.

    To state the point quickly, I foresee this Wild Wild West coming to a screeching halt, where we will all be (willfully) blindsided, and potentially have our careers and businesses put on hiatus until we comply with mandated regulations that will take months, if not years for each of us to comply.  I expect that some currently working in DF/IR may not be able to comply!

    Let me get to the solution before getting into the issues.  Simply copy and modify what is being done in other professions to fit the DF/IR profession, and give our ideas to the respective government regulatory agencies to implement.  In this manner, everyone can keep doing what they are doing, begin to comply with the regulations, be grandfathered in where appropriate, and have reasonable standards created by those who know best (that’s you by the way).  Pick a profession, any profession, and get started.  The medical field, accounting field, anything.  Even hair stylists are regulated with training and education standards.  Pick several and meld them together to fit DF/IR.

Brett’s Opinion on a few things

Certifications

I usually get on a soap box and rant against certifications, but I’ll make it shorter this time.  I’m not against certifications, and I believe that having a sheet of paper of classroom training completion is worthwhile.   Having that sheet of paper shows:

  •  I attended ‘x’ number of hours on "x" date and time
  • I was exposed to ‘x’ topics in those hours
  • I was taught by ‘x’ (person or organization)
  • I passed an exam (if one was given)

 

Licensing

    Licensing is inconvenient to maintain, just ask any doctor if you are curious.  But, licensing is important to prevent unqualified people from practicing a service that can have serious consequences.   We certainly trust our doctors, but part of that trust is based on a license from the state, which is based on a successful internship, which is based on the degree granted by a university, which is based on the successful passages of a specific curriculum, and so forth. 

    In the DF/IR world, all we need to do is attend a 3-day FTK class and buy a dongle.  No, all we need is just buy the dongle.  Wait a sec, actually forget the dongle, we can just download some free forensic software and get started…

    We need licensing, and a standardized process to meet those licensing requirements.  Whatever that may end up becoming is currently up to the DFIR community, but will eventually be mandated by someone else if we sit idly by.  If you are reading this and doing DF/IR work, I would imagine that grandfather clauses will be inserted in every requirement, otherwise, the entire DF/IR field will grind to a halt.  Most of those working today in the DF/IR field can probably teach DF/IR at a post-graduate level, yet not personally hold a post-graduate degree (or any degree in any IT related field)

    I can foresee licensing based on a healthcare provider licensing model.  Each different job (doctor, nurse, etc…) has its basic foundational requirements.  Additional specializations have additional requirements (heart surgeon, registered nurse, etc…).  So that,

  • DF/IR Licensed Professional (much like a family doctor in general practice)
  • DF Licensed Specialist (operating system specialization, device type specialization, etc…)
  • IR Licensed Specialist (penetration specialization, intrusion specialization, etc…)
  • And so forth.

    Imagine looking for an employee and you can instantly see what they should know based on a standardized licensing model.  Today, you may be trying to weed out the IR applicants for a DF job you have, and that is not as easy to do when you have to go line-by-line to sort it out what the applicant’s skills are.  When looking at other professions, I usually point to one example of becoming a hair stylist.  I'm not knocking hair stylists, but the majority of us getting hair cuts don't even know the licensing requirements involved.  In Washington State, it's a lot of requirements to just cut hair...

 

    Think about what it takes to cut hair the next time you argue against any licensing requirements for DF/IR work...because we don't have anything that compares.  Another benefit of licensing is getting rid of the bad apples.  An example of how this is done in the police world (at least in WA state), is the Peace Officer Certification.   If the Peace Officer Certification is revoked, then that police officer will not be able to work anywhere in the state.  The world of lawyers is similar in they can be disbarred from practicing law.  How nice would it be to de-certify a DF/IR person who falsified evidence or doesn’t meet any minimum standards?  Everyone would benefit.

 <on soapbox>

    I want to rant a bit on certifications, only because I am asked about ‘which certs should I get’ all the time.  I am not anti-certification, but I have strong feelings about some of the certifications and about how certifications are looked at by students, employers, courts, and vendors.

     I believe certifications are important to more easily show in court that you at least completed training in a certain subject especially if you are using DF/IR skills in (1) helping put someone in or keep out of jail, or (2) helping someone keep or lose their job.  It doesn’t mean you know what you are doing, just that you had training in the subject.  Otherwise, it looks like you were winging it.  **exceptions exist, I know, but bear with me as speaking generally**.

    Here are some of issues I have personally seen in courses offering certifications:

  • ·         Students sleeping in class
  • ·         Students showing up late and leaving early due to “work”
  • ·         2-hour lunches on some rarer occasions
  • ·         20-minute breaks on many occasions
  • ·         Course over by lunchtime on the last day
  • ·         Everyone passes the test with multiple attempts
  • ·         Everyone getting a certificate even if they failed the test or didn’t attend the entire course

     Here are some of the issues I have personally seen about certification perceptions:

  • ·         Only “x” certified DF/IR employees know how to use “x” software
  • ·         You must have “x” certification to apply for this job
  • ·         If you self-studied and mastered “x”, you aren’t as good as an “x” certified applicant
  • ·         The “x” certification is better than the “y” certification
  • ·         The “x” certification is more expensive because it is the best certification

    I have seen certification-junkies, where almost like an obsessive collector, the more acronyms they collect, the better they feel.  What about the Challenge Coins!  Gotta have them!  Vendors have got to love these types.  It's like the Pokemon or Furby craze.  Employers are also at a loss because the only certifications they care about are the ones that are most hyped by a vendor that gives out the most cherished acryomn. 

    As for me, if I were ever a hiring manager again, rather than look at an applicant and see that box for “x” certification exists, I’d rather make sure that the certification was (1) relevant to the job, and (2) the applicant knows the material that the certificate says.  Otherwise, I look at certs as simply a document showing the number of hours that a person completed for professional development. No more. No less.

    Speaking of number of hours in courses, I am a stickler on actual numbers.  Every statement that I have ever made of the number of classroom hours I have completed, I have cut the documented number down by at least 25%.  On paper, I may have a certain number of hours in print, but in depositions, testimony, resumes, CVs, and informal conversations, I state the lower number.  Why? Because I see classroom hours as not including the breaks or the early-outs on Friday morning.   Or when the instructor has to cut the class short to make a flight.

    I have taken courses where a 40-hour course turns out to be 60 (like SWAT training….), but I have never seen that happen in the DF/IR training world.  If you don’t believe that a 40-hour course classroom time is closer to 30 hours, crank up Excel and put in the number to your last course.  Be honest in the numbers and you will be surprised.  And be sure to put in the extra-long breaks, the days that the class started late and ended early.  And the days that the class stalled because of this-reason or that-reason.  Add the time you stepped out for a phone call (if you ever did such a terrible thing!).

 

 

     The next time you testify and are asked about your classroom (formal) hours of training, think about the actual numbers before you answer.   Lunch time is not typically going to be considered DF/IR learning time.

 <off soapbox>

    I see the future where the road to working DF/IR will be as easy to figure out as it is today if you want to be a doctor or lawyer or house builder.  Follow the path to licensing and you will be good to go.  Salaries will be much higher, the profession will advance faster than ever, and employers/clients will have an easier time of finding exactly who they need.

    The requirements and qualifications? That’s up to us to figure out, and figure out fast.  Otherwise, I can also see government making the requirements so burdensome that it will push out those who are competent and prevent those with great potential from coming in.  That is totally opposite of what we want to happen.

Rate this blog entry:
0
455 Hits

Sharing is caring

One thing about the DFIR blogs is that they tend to bounce off each other.   This is a good thing because tidbits of gold nuggets can be expanded upon with different perspectives and experiences.  Never in human history have we ever been able to instantly connect world-wide to increase our knowledge base, especially in the technology field (specifically in the DFIR field!).

With that, to expand on Harlan Carvey’s never-ending quest to push ourselves to share, I want to credit those who do share as I constantly benefit personally and professionally from the work of others. For those who do not yet share, consider the benefits you will have by putting yourself out there, even just a little.  We are all smarter only because we communicate with each other.

I have seen polar opposites of how sharing knowledge works and how hoarding knowledge does not.  As I was a Marine at 17 years old, I had an unfair advantage of the benefits of sharing.  I never heard the actual word “sharing” in the Marines, but that is what we did.  We shared knowledge and experience.  From day one in the Fleet, I was shown the way to do ‘things’.   I was given the opportunity to try, fail, try, fail, try, fail, try, succeed.  No one ever gave up on me, nor wanted me to fail.  When my turn came to lead, I did the same to the boots that came in.  I showed them the way and made sure they were competent.  Allowing the failure of a Marine was not an option.  I naively believed that was the normal way of doing business everywhere, but I was wrong.    

Enter the private sector….

I have had both similar experiences in the private sector and a completely opposite experience.  The experiences that I had that were opposite in that I never expected professionals to hoard knowledge from their peers.  Co-workers, peers, and supervisors seemed to be on warpaths to make sure the newbies failed.  Those who did not fail were allowed to stay.  Those who failed were booted out the door.  Trial-by-fire was the method of training new employees.  I have even seen the sabotage of new employees in hopes to flunk them out. 

  • When the team shares, teaches, encourages, and supports each other, the team grows and bonds together.  This team can tackle anything that comes up, without hesitation, and without worry of being left to drown by an individual in their team. Expect failures, but also expect the failures to be turned around into successes.
  • When you have individuals who are only looking out for #1, your team isn’t a team.  It is a group of individuals, each with a different agenda.  Expect failures.  Don't expect success.

Having been in both types of situations, I can say without hesitation that when people share knowledge, everyone grows and benefits including the person who is sharing.  In the world of DFIR blogging, whether you are in a one-person company or working for a Fortune 50 organization, when you share your knowledge, you benefit more than you know.  If you are being paid as a leader in your organization, under whichever term (manager, supervisor, TL, etc...), your mission is to give every opportunity to grow your team.  Some tips:

  • Teach, show, do (you are a teacher. teach your members, show them how, let them try. rinse and repeat)
  • Don't give up  (if your member keeps trying, so do you. have patience)
  • Teamwork  (team success, not individual wins, makes for success)
  • Teach your peers and subordinates to succeed individually for the group and the unit will succeed as a team.

How does this apply to a DFIR blog?

Your blog is affects everyone in the field.  It is shared. It is talked about.  It is critiqued. It is criticized. It is praised.  It initiates conversation.  And most importantly, it moves the DFIR field forward.  Whether your blog moves us an inch forward or a light-year into the future, you are a part of it.  To those who don’t believe this, you don’t have to believe it.  We reap what we sow. To everyone else, I’m merely preaching to the choir (and I bet your team rocks).

 

PS. this applies to any line of work, but when our work is 'in computers', dude, we practically work on the Internet so share your brain :)

Rate this blog entry:
0
524 Hits

A bundle of case studies and X-Ways Forensics Practitioner's Guide training

************UPDATE 10/29****************

Case studies 2 has been published.  It's the Mr Fuddlesticks case.

******************************************************

Out of the 100+ viewers of the case study I did last week, a bit more than half completed a survey with most of those including comments on the case study in regards to what they want to see.

With that, I decided to try a series of case studies with between 4 to 8 case studies added each month.  The first case study I did was longer than expected at almost an hour, but I plan for each case study to be between 15 to 45 minutes.   If you want an easy and inexpensive way to put training & education hours under your belt, this is good way to go.  Spend time reviewing case studies!

The goal in the case studies is to;

  • show how others do cases
  • show how suspects have been caught
  • show processes, techniques, and methods that suspects used to avoid being caught
  • show processes, techniques, and methods that investigators used to catch suspects
  • give insight on how to work cases with ideas and examples

As time is an issue for everyone, for each case study there is a short quiz to prove you watched the case study.  The quiz is a pre-requisite to receive a printable certificate that states the course title, date, and hours spent.  This is to make the bosses happy and add training time to your CV.  The cert is optional, as is the quiz, in case you just want to review the cases without documentation of your time.  As far as time goes to do a case study, I've broken down the case studies to bare bones important aspects of the cases.  You don't have to read every line of a 30 page affidavit to get the point of the case studies.  I'll spit it out the highlights for you with only the good stuff.  No fluff (as in, no need to read boiler plate after boiler plate).  

I want to make the case study series attractive to you because case studies are important.  If you are a student, there is no other way to watch a real case in the real world other than a case study. If you already work cases, you know that there must be a better way to do what you are doing; so case studies can give you a tip or two to get better at what you do. If you already know everything….that’s another issue (because no one knows everything).  Continually work on improving your skills and you will continually improve your skills.

I have case studies lined up already, but if you have a case you'd like an opinion on for a case study, I'll take a look and maybe add it to the series.  Just send it to me (This email address is being protected from spambots. You need JavaScript enabled to view it.). 

I’ll start the series with a short-run promo price that includes a 3-month access the Case Studies Series and also to the X-Ways Forensics Practitioner’s Guide Online Course for $95.  The regular price for the case series is $125 and the X-Ways Course is $599. 

This is short-run promo at $95 expiring on 11/11/2017 for both the

Case Studies Series and the X-Ways Forensics Practitioner's Guide Online Course.

Register here: http://courses.dfironlinetraining.com/series/case-studies-with-x-ways-forensics?pc=cs-xwf-nb 

Case Studies 2A will be posted this weekend.

 

 

Rate this blog entry:
1
455 Hits

Case studies are more helpful than you may think

**A quickly fading online course promo: read about it here: http://brettshavers.cc/index.php/brettsblog/entry/a-bundle-of-cases-and-x-ways-forensics-training **

Today’s presentation on a case study was an example of what I have been doing for many years – figuring out how other people do the job…

I first started doing case studies when I made narc detective years ago.  I can’t lay claim to having had the worst training officer in the narc world, but I would pit him up against anyone as being bottom of the barrel insofar as teaching a young narc how to do his job without getting killed in the process.  That’s when I started doing case studies.  It was a selfish attempt to save me from being killed.

I pulled as many adjudicated narc cases that I could get my hands on from the records room.  I printed off old cases from microfiche, photocopied affidavits and reports, and interviewed the detectives that ran the cases.  My sole purpose in life at the time was trying to find out how to run a case without getting killed while doing my job at the same time of having little in the way of supervised guidance.  By the time I had figured out how to do the job, I had probably put my life at unnecessary risk a dozen or so times, all the while the ‘senior’ narc standing there watching me with a cigarette dangling from his mouth.  Those were not fun days.  Some may call this ‘trial by fire’.  I called it “this sucks”.

But I learned to learn by reading the cases of what others had done.  I analyzed everything in the reports and affidavits, from the decisions made to the tactics used.  By the time I actually went through formal training for narc work, I pretty much had it figured out.  The formal training just solidified what I spent months learning by case studies.  

Fast forward to my digital forensic days.

When I started in digital forensics (“computer” forensics at the time…), my agency had a big donut as the number of forensic examiners in the agency. A big donut = 0.  My agency not only never had a forensic capability, but rarely even sent out a computer for analysis.  I think we had one forensic exam completed by a private examiner…once.  At the time, I thought I could do magic because whenever I said "computer forensics", administrators would automatically roll their eyes and talk about anything besides computers.

So, I started the first forensic unit.  Guess I how I learned to do the job…  Case studies.  By the way, it worked out fine.  I did cases.  Administration was happy.   Bad guys went to prison.  The unit grew after I left, so there's that.

The technical part of forensics is not difficult.  I believe most anyone can figure out how to pull an artifact from a storage device.  A disk is a disk is a disk.  A file is a file is a file.  But running a case, when every case is different from the last?   We have plenty of software and plenty of sources of information that tells us how to do the technical part, however we lack the documentation on how to run a case.  A solution: Case studies.

I have found a few case studies on YouTube over time, but all that I have found are those doing a case study who never actually ran a case.  Looking at a case from the outside misses a lot of important details and many assumptions have to be made.  I wouldn’t evaluate a pilot if I’ve never flown a plane.  Running a case (much like piloting a plane I would imagine) involves a lot of physical labor, organization, fortune-telling, guessing, planning, interpreting, and managing data, people, and events.  That’s how I look at case studies.  I try to look at the case from the perspective of the investigator (or special agent) in order to understand the decisions made and methods used.  Then I see if I could have done anything different or better.  Then I put what I learned to work and make sure that it does work.  It also doesn't hurt to also know the legal restrictions in running a case.  If you don't know the subtle differences between civil and legal cases, or the legal authority as a law enforcement officer or citizen, you'll be skating on thin ice every day in every case.

This is my intention with making my personal case study notes public.  Take a look at a case through the eyes of the investigator/examiner.  Watch how a case unfolds and how an investigator can take the case from start to finish.  Learn how someone else does the job and draw the best parts of it for your job.  There are few better ways to see how a case is worked other than reading the actual case and how it worked.

Interesting enough, with today’s presentation, a thriller author emailed me with a dozen questions about how computer investigations work and how to incorporate complex details into a work of fiction.  The short answer I gave was that it isn’t easy to get right if you don’t know how it works.  If I were to write a book about a pilot, it would be the worst book ever because I’d get all the details about being a pilot wrong because I have only flown and jumped out of planes, but never piloted one.  For the writers out there, I’d take a look at some case studies to see how it is done in the real world, and then bend it a little for the fictional world.

As to more case studies, I’m hoping to have feedback with a survey I added to today’s case study.  If enough people think it is worthwhile, I’ll make it a series. If not, I’ll still do the case studies, but it’ll be the same way I’ve been doing them for the past 20+ years….quietly by myself…

 

Side note:

The limited time frame for this initial online case study was done for a reason, and I totally understand many people can't make it within the short registration period.  Some of the reasoning is to limit the number of people, get a gauge on if this will be worthwhile to produce, and make a plan to support a series of case studies.  I also wanted to limit  the number of those I am practically giving away the 13-hour Placing the Suspect Behind the Keyboard course as well. 

The difference between when I do a case study by myself and when I create an hour's worth of video and slidedeck is on a scale of 1:5 in time spent, so with that, let me know if this is something of value for you.

Recent Comments
Brett Shavers
You hit on a few points. Knowing what to look for (the smoking gun) is critical in every analysis. To find the smoking gun, the ... Read More
Monday, 23 October 2017 23:51
Rate this blog entry:
0
713 Hits

Drop the mic...please.

Well...that didn't work out so well, did it?

I had a serious audio problem with the webinar today, from which I learned to mute attendees for the next time that someone doesn't mute their mic.  My fault on the audio, but on to the positive with the webinar: I'm going to make another (two more) presentations.  At the same time, I'm going to make it more in-depth, with more case studies, in more detail, at the same price of free.  Did I mention that I really feel bad about that audio problem.

Details on the upcoming presentations are at: http://courses.dfironlinetraining.com/series/case-studies-placing-the-suspect-behind-the-keyboard. In brief, I may be starting a series of Case Studies based on recent cases I find or cases of mine that I can talk about openly.  With that, this next presentation is Case Studies I - Placing the Suspect Behind the Keyboard (meaning that there most likely will be a Case Studies II, and a Case Studies III, etc...).  I'll provide case documents as I have them available for self-study into the cases that will be discussed.  My intention is to get you thinking like a detective in your cases, regardless of the type of case or importance of the case.  By important, I don't mean that any case is unimportant, but some cases are critical such as those that involve serious threats of harm to persons.  Every case is important to someone, but in some cases, people can be hurt or have been hurt in certain types of cases.

I am limiting the number of attendees to 50 per session and I'll have a promo each time for something neat.  For this upcoming session, I'm giving a promo of $45 (instead of the $799) to the full, 13-hour Placing the Suspect Behind the Keyboard course.  Next time, who knows what it will be and for what.  BTW, the sessions will not remain online past the dates presented as recordings.  These are one-time training sessions not to be repeated.

FAQ (that I've been asked so far...):

Will you keep recordings online for future reference?

Nope.  Either the presentations will be live or delivered as a recording on the day of release only.  

I missed the session, can you extend the promo for me?

Sorry.  The promotions are extremely short-lived for the few hours of the presentation time only because I'm near the point of making the course free when it goes from $799 to $45 (or so).

I missed the session.  Will it be replayed?

Nope. These will be shown once or twice at the most.

Can you put the videos on YouTube?

No Youtube for me.  I'm not a fan of Youtube 'training'.  The presentations I am giving each include a certificate of training attendance in order to give you documented training hours.  Sometimes you need to keep the mother-ship happy with training records, so I aim to help provide those records.  Also, it doesn't hurt to be able to claim training hours when you produce physical documentation instead of saying that you 'learned it on YouTube'. 

The direct link to the case study series is: http://courses.dfironlinetraining.com/series/case-studies-placing-the-suspect-behind-the-keyboard 

Rate this blog entry:
0
468 Hits

If you are a “Self-Proclaimed Hacker” looking for a job in LE…

We are almost fully into the computer-age.   In nearly every aspect of our lives and jobs, computers* in some form or another, are integrated.  This means that if you have the inclination and ability to work with computers, your time has come.  The world is your oyster as the doors are not only open with information security careers, but employers are fighting over you as their next new hire.  This is kinda true with law enforcement, but not so much. 

 <*by “computers”, I mean everything that encompasses technology from writing code to developing the devices>

 Let me give a little personal insight into one small aspect of a future career that is of interest to many: law enforcement.  I’ve never directly hired anyone into law enforcement, although I have participated in the interview process for those wanting to be hired, given my input on specific persons that I’ve known who applied to law enforcement, and I have seen people fired for doing some amazing dumb things as cops (and federal agents).  With that, here is one suggestion on increasing the odds you get hired if you work in information security.

 Be careful if you call yourself a hacker if you are not a criminal hacker.

Without clear context, calling yourself a ‘hacker’ implies calling yourself a ‘criminal’, which will cut you out the hiring process faster than a long-tailed cat running out of a room full of rocking chairs.  The primary mission of hiring in LE is to not hire criminals or anyone with the potential of committing crimes in the future.  Remember…past behavior is the best indicator of future performance and behavior.  Do not think that you will have an opportunity to spend a half hour as to why a hacker may or may not be a criminal.  Thousands of applications are submitted each month and one of the best ways to cut the workload of a background investigator is to dismiss as many applications as possible before doing too much work on them.  The easy ones are first, such as those not meeting the job requirements. Then go the ones with blatant problems (serious drugs, arrests, etc...).  Writing "hacker" on your application is a red flag.

I write this only because fairly recently, I was contacted by a background investigator for my thoughts on a police department hiring someone who is a self-proclaimed hacker on their social media. Having to explain what a hacker is, is not, or could be to someone who is not in the community is not usually productive in less than 10 minutes, especially if they are looking for an easy out to go on to the next application.

My opinion is that many times, we may call ourselves “hackers” but for all practical purposes, are actually “counter-hackers” or “anti-hackers”.   In the most commonly accepted perception of a hacker, the public sees a hacker as someone who steals their ID by hacking into their computers.  Regardless of how much you may try to explain that you are using “hacker” as a marketing slogan or that not all hackers commit crimes, it does not matter because you most likely will not be hired because of the perception and perception is reality for all intent purposes.  The liability of hiring someone into law enforcement who openly claims to be a hacker is not something a government agency will want to take on as a full-time employee.  Sure, maybe some contract work while you are escorted around the building while you work on a limited project, but not as a full-time, badge carrying, free to roam anywhere you want officer.  Do I agree with this?   It doesn’t matter because liability and the perception of future liability is what matters.

So, if you want a better chance of being hired in law enforcement, be careful with calling yourself a “hacker”.  I can promise you, without hesitation, that everything you put online, say at a conference, write in a blog, or speak to a future job reference, will be looked at by the agency that is considering hiring you.    Law enforcement needs better technically proficient cops, so get that job by marketing yourself as such.

 

Rate this blog entry:
0
490 Hits

Case study - Placing the Suspect Behind the Keyboard

Not too long ago, I read an article where the state’s largest cocaine bust happened because the driver was stopped for speeding.  The first thing I thought was, “Speeding…yeah, right”.   So, I called a good friend of mine who I worked some cool drug cases with and asked if that was his case.  But of course it was.  The article read like cases we worked together for some years.   The case is public knowledge today, but in short, a year of investigative work resulted in ‘taking off’ lots of drugs and cash using pre-textual traffic stops as wall cases to keep the core case going.  We did that a lot and it was a lot of work.

My point in the story is that when you see a simple case publicized, there is usually a lot more that has happened behind the scenes that most people will ever know.  Some of this is intentional, such as when a small part of a case is ‘walled off’ to protect the core of an investigation and other times the work is so intensive that to start talking about it will (1) bore the listener to death and (2) talk a week to flush out the details.

So here comes a really cool case I just found to illustrate these points.  In brief, this case is a cyberstalking case that was righteous in all aspects in that the cyberstalker truly needed to be caught and that the work done was awesometacular.

I’ve taken a few snippets from the affidavit to discuss some of the notable investigative aspects of the case.  As a reminder, that what you read in the affidavit is like seeing the tip of the iceberg of a case.  There is so much more in a case like this that is not in the affidavit.  Having written more search warrant affidavits than I can count, I cannot imagine how much work was done on the case based on what was included for the affidavit.  Very cool.

Side Note:  Read the entire affidavit when you get a chance.  Flesh it out.  Read it like a novel.  What would you have done differently or better?

https://www.justice.gov/opa/press-release/file/1001841/download 

 

This is a key point. Either iCloud was hacked (as in a technical hack) or someone had access to the account physically (as in, someone who knew the victim and could have accessed her devices).  Eliminating the suspects who could hackers is impossible.  Eliminating suspects who are known to the victim is possible.

The suspect, “Lin”, erred in using variations of his name in social media accounts.  It’s only a clue, but important to build upon.  In all cyber cases, keep track of user names.  Sometimes there is a reason a username was chosen and perhaps clues to other information.   For each online service, such as Instagram, also consider that accessing each service can be done using many different devices from many different locations on many different occasions.  With each connection, the suspect risks being discovered either by his mistakes or service provider.  That means for you to look at every connection of every message, text, email, or login.

 

 Not much was mentioned in how the anonymity was obtained, but again, each communication is a potential disclosure due to a suspect’s mistake.  Considering that the false flag in the Matthew Brown is known by the victim, the assumption is that the suspect is known to the victim and/or Brown.  This can narrow the list of potential suspects down.

I threw this in just as a reminder for employers (and to remind your clients!) to backup/image departing employee devices for a set time period, just in case.  This is also a reminder to employers that even if they think nothing is left on the computer, usually there is something.  I’ve come across this multiple times and in one case, the entire case was closed with a single forensic analysis on a reinstalled OS from a departing employee.

At this point, it’s easy to see that the suspect (Lin) is probably the guy.

The similarity in style and content from multiple accounts can be tied together, at least as being too similar to be a coincidence.  By itself, not enough to prove a crime/incident, but when taken in totality of all evidence, it is very important.

This would be called a “slip up” by the suspect.  When details known only to a few people are discussed, the list of potential suspects gets very short.

Again, if physical access is needed to commit a crime, the list of suspects can be shortened.

Never give up on uncovering someone because of technology being used for anonymity.   Keep at it.  Keep looking.  Keeping thinking.  Time and effort works for you.  Time works against the suspect.

Technically, this is called, “the suspect screwed up”.   But it took getting the records from Google, which required having the idea to do along with the labor to gather legal cause to request it.

 

Social engineering by the suspect.  Very creative.  However, it required the suspect to create a social media account, email account, and obtain a phone number.  Again, consider how many times he would need to connect to the Internet, from one or more devices, from one or more locations in order to do this.  Each act is a potential windfall of evidence when the suspect makes a mistake. You just have to check every connection known and find the mistake. It is there.  You have to look.

 

And yet another Internet service to add (TextNow) to your investigation.  This is a good thing.  I have heard complaints from investigators about the number of leads to add to the list of things to do in an investigation every time something else comes up.  For me, I love it.  A dozen social media accounts? Cool.   A hundred social media accounts?  Even better.

 




Like I said, the more the merrier.  Most suspects do not realize that everything they do is not separate from each act.  There is usually some connection. It might be the same device used.  Or it might be the same IP address used. Or it might be the same service provider used.  The above would make a cool timeline to visually show the connections.

Again, when you have the “same” of anything in a case, do not discount it as a coincidence.  The same IP or the same email or the same username or the same style of writing can all point to the same suspect.

Search the devices to which you have access to either confirm or rule out suspects.  In this case, searching Lin’s previous workplace computer found evidence that linked him to the crimes he was committing using other devices.

Not conclusive, but when you put all the evidence together, no one will see anything other than Lin as the suspect because of being overwhelmed with the little things, like this, that point to him.

 

Past behavior is a good indicator of future performance/behavior.  In Lin’s case, based on his past behavior, I would say that this is what he is: a cyberstalker.  Once you read the entire affidavit, you’ll see what I mean.

Here’s my take on the case. 

The timespan was lengthy, and there isn’t a lot you can do about that.  I don’t know the details of how many people or agencies worked the case, but I can imagine that there were a few (maybe one or two) who spent a lot of time on it, bantered back and forth on the best way to work it, suffered through a lot of investigative failures and wasted time*, and worked hard to get resources to put the case together.

I can imagine the number of court and administrative orders to obtain the records of all the social media services, ISP records, and phone logs being overwhelming at times.  That is the way it is, so in that aspect, don’t feel like any one case is getting you down more than another case.  I would hope that every user account that the suspect used was investigated, including the “anonymous” accounts.   Other cases have shown that even when a third-party provider promises anonymity, they don’t really mean it.  You will never know until you ask and you will never know what great evidence you can get without asking for it.

I’m not plugging the books I wrote for these types of cases, but if you get these kind of cases, check out the books for some tips.  They are in a lot of libraries, easy to buy online, and the main point I work to get across is to find the one thing that will make your case


On Oct 17, I am giving a short webinar on Placing the Suspect Behind the Keyboard.  If you stick around for the entire half hour, you’ll get a printable cert of attendance that you can take back to your employer for training credit to justify the time to join during work.   And also, if you stick it out to the end (it’s only a half hour…..), I’m giving a discount to the 13-hour online course that is the biggest I’ve ever done.  $45 for the entire $799 course.   But the promo will only be good for an hour after the webinar, and only for 100 attendees in the webinar; meaning that you’ll have to sign up right away if you want the course. 

Be sure to add your name to the webinar here: Register


If you are like me, you like to dig.  You like to find out whodidit.  You want to put together a good case.  And most importantly, you want to stop bad people doing bad things to good people.  Isn’t that the point of all this?

 *Sarcastically I said “wasted time”. I mean that time spent without a positive result may seem like wasted time, but it is not, since you have to spend time investigating and much of it results in not much forward movement of the case.  Accept the time spent feeling like you are running in circles as part of what it takes to get it done.

Rate this blog entry:
0
711 Hits

Free Webinar - Tips and Case Studies on Placing the Suspect Behind the Keyboard

I had coffee with a detective (ie...consulted on a case....) to discuss his case where tying a person to one specific device was necessary for criminal charges in an overly complex investigation.  There were a few things I learned and a few things he learned because of our talk.  I think it would beneficial to talk about some of the things we discussed in a webinar to pass along tidbits that can help others.

Not to take up a lot of your time, but how about a half hour of talking about placing a suspect behind a device?   I want the webinar to be live in order to take as many questions as I can squeeze in, while also packing in as much as I can in half an hour.  If you'd like to attend, register here: http://brettshavers.cc/index.php/events/event/23-webinar-free-placing-the-suspect-behind-keyboard-tips-and-case-studies.  SIDE NOTE:  There will be a bonus in the webinar that most likely be of interest to you.

 

The webinar is scheduled for Oct 17 at 11:00am (PST).   The webinar will be limited by virtue of the platform I'm using so if you want to get in, register early.  Given enough registrations, I may do a second webinar on the same topic afterward.  And if you do register, have some questions ready or even send them in advance (email: This email address is being protected from spambots. You need JavaScript enabled to view it.) so I can be sure to cover as many of the questions as I can.  Or just listen in.  This topic applies to both criminal and civil cases, so whether your job is to have a person arrested (or vindicated) or an employee fired (or retained), the tips apply equally.

As I have always said and believed, keep looking for that one thing that can make your case or save you minutes or even weeks of work.  Once you find that one thing, you will crush your cases as if they were Styrofoam cups.  Tip: that "one thing" is different for everyone, but we all need it to be successful.  Those are the things I want to talk about and share.


And here is one tip you can use:  Get your mind in the game.  This is easier said than done.  You can tell yourself every day to do it, but it won't work unless you know how to do it.  Just saying it doesn't work.  But once you do get your mind in the game, you will be the master of that game.  By 'game', of course I mean your job or the task at hand.  When you can create laser beam focus on a task, you will own it.   I drill this concept with the ways to do it in every talk I do.  It's that important because if your mind is in the game, you can do anything.

**** Update -Oct 17 *****

I'll have one more webinar session, limited to 50 attendees.  Details to be posted soon.

 

Rate this blog entry:
0
709 Hits