|
Written by Jason Briody
|
|
Wednesday, 18 November 2009 16:00 |
|
In August of 2007, the Texas Department of Public Safety's Private Security Bureau clarified how they believe Private Investigator licensing should apply to both computer forensic and e-discovery vendors practicing within their state. An excerpt from their clarification follows:
"First, the distinction between "computer forensics" and "data acquisition" is significant.
...For example, when the service provider is charged with reviewing the client's computer-based data for evidence of employee malfeasance, and a report is produced...[they have] provided a regulated service.
On the other hand, if the company simply collects and processes electronic data (whether in the form of hidden, deleted, encrypted files, or otherwise), and provides it to the client in a form that can then be reviewed and analyzed for content by others (such as by an attorney or an investigator), then no regulated service has been provided." (emphasis added)
Click for the full article (and click the "Computer Forensics" link after the jump).
Though this clarification is from 2007, it's a good example of what other states have still failed to publish, and what lawmakers (even in Texas) have failed to put clearly into law. Many states have vague statutes in the books that leave computer forensic and e-discovery practitioners in an uncomfortable limbo, unsure of the legality of performing their services in (or for) that state. We'll keep you updated. |
|
Written by Jason Briody
|
|
Wednesday, 18 November 2009 10:09 |
|
The disposable cartridge in your portable label maker might contain a perfect copy of every label it's ever printed.
...You...you haven't just been throwing them out, have you?

Recently, our portable label maker (the "Brother P-touch PT-1830 Electronic Labeling System") ran out of labeling tape. After putting in another label cartridge (specifically, the "TZ-231 12mm 1/2 inch Laminated White") and continuing to print, I decided to pop the old, disposable cartridge open with a flathead to see what was inside.
First, a word on the label maker itself. It's a well-made label maker, but it's relatively "low-frills." Most importantly, it doesn't have a "history" function (that is, you can't "recall" all your previous printings), though you can save up to five of your most commonly printed labels with one of the "Favorites" buttons. You'd probably assume the label maker wouldn't keep an electronic log of what was printed unless told to do so with the press of a "Favorites" button, since having it do otherwise would be burdensome and relatively useless.
That "lack of logging" assumption makes sense based on experience with how and why computers log (generally only logging what is crucial to the smooth operation of the software they run or what's important to and/or requested by the user). And since the item's manual doesn't mention any such logging functionality, it's probably a safe assumption to make.
But when you think "logs," don't just think "electronically stored." Because for a machine that's only partially electronic, you'd only be partially right.

The above picture is what's contained inside every cartridge of this type: a physical "negative" copy of every label that it has successfully printed on a single, long, film-like tape. It's not created for logging purposes, per se; it stores these "copies" merely because it has nowhere else to put the rest of the black film-covering that would have become the letters, numbers, and designs you normally print out. So what happens when you throw out your cartridge? To a malicious someone in the know, it's an easy-to-spot cassette with everything you've ever printed wrapped neatly around a spool.
You're probably thinking that you don't print anything too sensitive on your portable label makers. But if you label folders with client names or print IP addresses, usernames and passwords to display on servers or computers (it happens), you're using the label maker for a somewhat sensitive purpose. As for data as sensitive as full names with social security numbers, few would likely ever have to a need to print such information with a label maker, but I can think of at least some situations where it's plausible (such as on HR records, or a person tasked with filling out a number of forms that repeatedly ask for their name, social, DOB, etc.).
Security concerns stemming from the use of printing devices certainly aren't a new phenomenon. Typewriters that use single-strike carbon typewriter ribbon, for example, store every character a user types. Every time a user presses a key, the "type hammer" with the character corresponding to the key the user pressed swings forward, striking both a ribbon of carbon paper and your document. This is necessary to create the printed character on the page. But unbeknownst to some is what's left behind: an imprint of the character you just typed at that location on the carbon paper, which then advances along and is saved on its spool even after you remove your typed document.
Just like the cartridge in our label maker, this ribbon sticks around on a spool merely because it has nowhere else to go; quite the opposite of most computer software's "discard unless instructed to keep" mentality. Of course, this mentality makes sense on a machine that's able to control the transience of the information it processes, unlike a single-use, self-contained label cartridge or carbon typewriter ribbon where that information literally has nowhere to go.
In fact, government employees that worked on sensitive documents in the days of the typewriter were required to lock their typewriter ribbons in a safe at the end of the day (much like we (hopefully) secure our computer data with encryption). Once the typewriter ribbons used by these employees reached the end of their spool, they were burned.
Devices that read and transcribe typewriter ribbons (such as the Ribbon Analysis Workstation by Envisage Systems) are still in use today in government agencies such as Immigration and Customs Enforcement (ICE), according to this article in Government Security News Magazine. The FBI's Questioned Documents Unit(QDU) also has the ability to "examine and analyze typewriter ribbons," and as of 2006, they too maintained a ribbon analysis workstation.
While label makers might not have the same amount or type of data on them as typewriters, the risk is still present when using them in certain scenarios. The next time you're switching the cartridge in your label maker, think about what you've been labeling and determine if you need a more secure method of destruction than simply throwing it in the trash. (Or just pop it open and check for yourself!)
For those interested in further reading on printing privacy concerns, check out this interesting PC World article on how some documents printed with many standard printers reportedly contain information, including their printer's serial numbers (an effective way to tie documents back to a single, physical printer), encoded in barely-visible dots on the printed page. Then head over to the Electronic Frontier Foundation for a number of resources, including a preliminary research paper with detailed information and examples of these "printer dots" in action.
As soon as you commit information to a medium other than your memory, it's very easy to lose positive control over that information. This will happen almost instantly unless you are able to understand and control every facet of the both the commission to, and the storage of, that medium. Keep that in mind.
But don't write it down. |
|
Written by Ryan Lerminiaux
|
|
Thursday, 29 October 2009 14:02 |
|
The data collection process begins before your EDD vendor ever sets foot on site with the preservation requests you deliver to your clients. Data preservation seems to be one of the biggest issues in most e-discovery disputes, so make sure that your client is well aware of what a legal hold means. Be careful not to define the hold too narrowly, because further review of collected data may bring additional custodians into an e-discovery collection. Data that is deleted during a legal hold (regardless of relevance) will negatively affect your client's image.
After determining which custodians are involved, begin communicating with your client. Find out what electronic devices your custodians possess and where they store data. Do they use a laptop or a desktop? Do they have an external hard drive or thumb drive that may contain relevant data? Do they use any kind of webmail for business-related communication? Anything that is left out of a collection could be brought up later by opposing counsel to show that someone was attempting to hide something.
If you feel that custodians are going to be cooperative, let them know what is happening. You can be somewhat vague on details, but can let them know what your EDD vendor is going to be doing, and when their computers need to be available for collection. The more a custodian knows, the more likely they will be cooperative. If you think the custodians are going to be uncooperative, you can collect the computers for "maintenance" purposes or to "check if the computer is capable of software upgrade ‘X.'" Either way, have a game plan in place and execute it before your vendor arrives on-site. Without a plan, the possibility for confusion and missed evidence increases (along with your total cost). Also remember that an informed EDD vendor means a better, less expensive collection with less time spent on site.
(Need to catch up? Start at Part 1) |
|
Written by Administrator
|
|
Thursday, 29 October 2009 13:53 |
|
Employees with Mobile Computers
The more time that your vendor spends on site, the more money you will have to pay in the end. Sometimes the simplest hurdles can make what should be a smooth operation into a really bumpy adventure. If your collection targets specific employees' computers, it is important to make sure those people (or at least their computers) are present when your vendor arrives. Now that people are frequently using laptops as their primary computers, it is not uncommon for them to be taken out of the office. In our experience, there is at least one laptop or laptop owner that cannot be located for nearly every project. Users may be working from home that day, on vacation, or inexplicably absent.
"Hostile" Employees
Employees occasionally see a collection as an invasion of their privacy. They can be uncooperative, act as if they are too busy to be bothered, or may even become combative. It is common for computers to "suddenly" stop working as soon as the EDD vendor gets their hands on them. The employee then blames the EDD vendor for what are usually pre-existing issues with their computer. Hostile employees might also begin deleting files that they don't want people to know that they had. These files are often unrelated to your discovery project (such as copyrighted music and movies or pornography) but mass deletion of any files does not look good during data preservation efforts. Make sure that your client is aware of this fact.
The Company IT Person
Most companies employ an IT person or department. These personnel can be very beneficial to a collection if they are cooperative with attorney and EDD vendor requests. Unfortunately, this isn't always the case. The IT person may feel that the EDD vendor is there because they did something wrong. IT may also feel left out of what they believe to be their business, and will try to direct the collection (i.e., "You don't need to duplicate that system."). Some IT people are also very protective of "their" computers and don't like outside entities touching what they perceive to own.
So what can you do to avoid these and other collection pitfalls? Read our final blog in this series to find out.
(Need to catch up? Check out Part 1.)
|
|
Written by Brian E. Dykstra
|
|
Friday, 11 September 2009 16:54 |
|
(Need to catch up? Click here for "Data of Mass Destruction: Part I.")
We've finally reached the first stage of destruction: degaussing. Degaussing is a process where magnetic media is exposed to a powerful, alternating magnetic field of sufficient intensity to completely saturate the media. Let me start by saying all degaussers are not created equal.
All of the degaussers we used were rented from the fine people at Data Devices International (www.datadev.com) out in San Marino, CA. Renting a degausser for a destruction project probably makes sense for most people as the purchase price for a degausser ranges from $3,500-$25,000. You'd have to be performing a lot of destruction on a regular basis to make that kind of purchase pay back.
The Bad: We started the project with a Verity System V660 EVO hard drive degausser with infrared remote control. The V660 is a table top style degausser that supposed to generate 6,600 gauss of energy and be suitable for server and PC hard drives but not tapes. Having some experience with degaussers, the V660 seemed like a good choice with a high energy output and claims of one pass, five second degauss cycles.
As a computer forensic/e-discovery professional, I'm always suspicious of hardware and software vendor claims, so of course we decided to test a few hard disks after degaussing to ensure they were properly degaussed. Testing a degaussed hard disk drive is a bit of a tricky scenario and far from perfect. Degaussing may leave a hard disk in a condition where it won't spin or function properly when connected to a computer but could still contain data on the internal hard drive platters. This is usually caused by the degaussing process corrupting the "servo tracks" on the hard disk drive that tell the computer how to communicate with the hard drive. In very general terms it is usually a good sign that the hard disk drive was successfully degaussed if the "servo tracks" were scrambled. Short of a clean room review of the platters from a hard drive damaged in such a manner, there isn't a good in-house testing option. Our much simpler test was to simply connect the degaussed hard disk drive to a computer running Linux. We checked for the following:
1. Does the hard disk drive spin-up when powered? 2. Is the hard disk drive successfully detected by the Linux host computer? 3. Does the Linux host computer detect a file system on the hard disk drive? 4. Is there reviewable data on the hard disk after degaussing?
Generally if you can answer yes to any of the four questions above the hard disk in question was not completely degaussed. After carefully following the degaussing instructions included with the Verity Systems V660 degausser we performed our four-step checking procedure. To our surprise not only did the first three drives we tested all spin-up properly, but the file systems on the hard disks were successfully detected and data was reviewable. We decided that something must be wrong with our process so after double-checking the degausser's manual, we degaussed the hard disk drives again and retested. After a 2nd, 3rd and 4th run through the V660 we were still able to review data on the hard disks. Next we decided to check line voltage where we plugged the degausser in to make sure it was providing enough power for the degaussing process. After checking everything we could think of, speaking with tech support at Data Devices International and unsuccessfully degaussing the hard disk several more times we decided the V660 must have been damaged during shipping.
Data Devices International overnight shipped a brand new, replacement Verity Systems V660 to us and we started the whole procedure over again. To our surprise the new V660 also failed to properly degauss the hard disks. In the end we found that a process of running the hard disks through the V660 eight times for 30 seconds at a pass (changing drive orientation each time) was the only way to successfully degauss a single hard disk drive. If you add that up, it means we had to actively degauss each hard drive for a total of 4 minutes to produce acceptable results. The problem with this extended-run, multiple-pass process is that both the hard disk drives and the Verity Systems V660 become very hot. The metal casing of the hard disk drives was actually heated to the point that the operator had to wear heavy gloves to prevent burning his hands. This heating problem also cased the V660 to overheat and trip the automatic shut-off/cool-down after degaussing four to eight hard disk drives. To make matters even worse, the hard disk drives vibrated so loud, even when secured in the drive holder with the lid closed, that the operator had to wear hearing protection.
To summarize, our experience with two Verity Systems V660s was very bad and we would not recommend this degausser to anyone.
For the second part of our destruction project we decided to select a degausser that used a new technology, specifically, capacitive discharge degaussing, rather than copper coil used in older degaussers like the Verity Systems V660. A capacitive discharge degausser stores up energy in large capacitors and then releases the energy in a powerful electromagnetic burst. The capacitive discharge process produces very little heat and the degausser can be run almost continuously. Capacitive discharge degaussers are also known as "pulse degaussers".
The Good: Data Devices International provided us with one of their new Garner HD-3WXL Continuous Duty Drive and Tape degaussers. One of the first things that we noticed about the new HD-3WXL degausser was that it seemed lighter, and was smaller and easier to move around because of carrying handles. During a careful read-through of the instruction manual we noticed that there was a warning about electromagnetic energy from the degausser being measurable up to twelve inches away from the unit during operation. We always recommend removing sensitve magnetic media such as cell phones, USB thumb drives, electronic keys and credit cards when working with any degausser. It is probably unlikely that these items would be adversely affected but why risk a pocket full of wiped credit cards?
The Garner HD-3WXL degausser worked even better than we expected. The degausser ran quiet, cool and quick. We didn't experience any drives that failed to degauss after a single 10 second pass. We also liked the little voltmeter on the side of the HD-3WXL that let us know it was actually pulsing the hard disk drives. There is a short little video of the HD-3WXL degausser doing its job at http://www.datadev.com/degausser-hard-drive-data-security-lto-hd3.html . Unlike a lot of other tools we've used, it performed exactly as advertised on YouTube.
The final phase of the destruction project was to take all of the freshly degaussed hard disk drives and various other bits of storage media to a physical destruction facility. We selected the oddly-named Back Thru The Future Computer Recycling, Inc. (BTTF) in Ogdensburg, New Jersey. You can securely send drives to BTTF in locking security containers that they will send to you, but we chose to deliver the hard disk drives in person. An important step in this final phase is to securely pack all of the hard drive for delivery to the physical destruction facility. We recommend using a heavy-duty banker box and not putting more than 30-40 hard drives in each box because of the weight. It is also important to make an exact count of how many hard drives are placed in each box. Here we recommend writing the number of drives in each box on the outside of the box and securely sealing it with packing tape for delivery. It is probably overkill but we like to treat every piece of digital media provided to us by a client as evidence until it is no longer our responsibility, therefore I recommend initialing each banker box where the tape and box meet as would normally be done for evidence. This extra little step makes tampering with any of the boxes obvious should anything unfortunate happen during delivery.
Once the hard disk drives are delivered to BTTF expect to spend some time with one of their employees recounting all of the hard drives to make sure nothing got lost in transit. From there the good people at BTTF will take control of the hard disk drives and generate another list by serial number of each piece of magnetic media before grinding everything into little metal shreds.
BTTF also has an excellent YouTube video on their web site of hard disk drives going into the shredder at http://www.backthruthefuture.com/index.php. The hard drive shredder is a lot of fun to watch after all the careful work that goes into a properly performed data destruction project. Once everything has been completely shredded, BTTF will provide a full set of their own certificates of destruction. The final step is combine the two sets of certificates of destruction into a final set and store it with other archived corporate documents. |
|
|
Written by Brian E. Dykstra
|
|
Monday, 31 August 2009 13:19 |
|
Jones Dykstra and Associates was recently asked to assist in the secure destruction of over 650 pieces of digital media containing Electronically Stored Information (ESI) for over 60 million individuals. Because a data destruction project of this scope doesn't come along every day we wanted to capture the entire process from beginning-to-end to help others contemplating a large destruction project.
All well-run projects start with careful planning. When dealing with large data projects involving sensitive data, prior planning is even more critical.
As I've discussed in other articles, the GLBA and the FTC's Safeguard and Disposal Rules are really intended to address the responsibilities of "financial institutions", but I believe they are excellent policies for almost every organization. The FTC has created clear and concise documentation that is designed with enough flexibility that even the smallest company could implement a safeguard and disposal program without great difficulty or expense. Under the Safeguard Rule the FTC defines personal data as:
- Names
- Addresses
- Phone numbers
- Bank and credit card account numbers
- Income and credit histories
- Social Security numbers
Once everyone had agreed that the digital media must be accounted for and destroyed we were able to move to the logistics of the project. We started the process by re-inventorying all of their computer systems and moving all non-critical computer systems to a secure area that was under 24-hour video surveillance. We insisted upon inspecting all previously used offices for commonly overlooked portable digital media such as floppy disks, USB drives and CD and DVD media. Not only did the careful inspection result in the discovery of over 100 additional pieces of portable digital media, we also discovered several computer and hard disks that had gone unnoticed in boxes and closets.
Next we began a two-part process. Part one was the preservation of all data discovered on computers and portable digital media discovered during our inspection of the mothballed offices. Each of the items was fully inventoried and forensically duplicated, and the forensic images were written to backup tape for long term retention. The second part of the process was to remove hard disks from each of the computers carefully matching it to each of the previous inventories (to ensure we had a forensic image of the data) and then re-inventorying it for destruction. Due to the amount of personal information contained on the magnetic media and the quantity of magnetic media involved it was prudently decided that all of the magnetic media would be degaussed prior to leaving any of the facilities for physical destruction. While removing the hard disks and physically destroying them lowered the potential resale value of the computers involved, it ensured that no personal information would ever be accidentally disclosed or lost.
Certificates of destruction were created for each piece of magnetic and optical media. The certificate of destruction itself is not a complicated document. The following information should be recorded on a certificate of destruction:
- Item Number
- Description of the magnetic/optical media
- Manufacturer of the magnetic/optical media
- Model of the magnetic/optical media
- Serial number of the magnetic/optical media
- Date of inventory
- Date of destruction
- Method of destruction
- Location of destruction
- Printed name of the 1st witness
- Signature block for the 1st witness
- Printed name of the 2nd witness
- Signature block for the 2nd witness
- Comments (optional)
How you record the data for the certificates of destruction isn't really that important. We like spreadsheets with macros, but you could just as easily use a database with forms or text documents if you like. We do recommend having some sort of master summary sheet of all of the certificates of destruction for easier review.
The next thing to do is remove hard disks from computers. The hard disk removal process doesn't take as long as you would expect even on hundreds of computers. Don't forget to check CD-ROM, DVD-ROM and tape backup drive bays for portable media. The slow part of the process is the recording of all the information from the hard disks onto the certificates of destruction and item-numbering them. We recommend the use of a portable bar code scanner to make the inventory process faster and less prone to error. Almost all hard disks and computers have identifying manufacturer bar codes for serial numbers, model and part information. This data can be scanned right into your certificate of destruction, eliminating the need for lots of squinting at little serial numbers and the inevitable occasional typo. Each hard disk should be tagged and item-numbered to so that its status is easily tracked during the disposal process. We recommend using small, round, colorful adhesive labels that you can get at any office supply store to mark the media. By using differently colored stickers you can visually track the status of a piece of magnetic media and computers. For example:
- Red sticker - indicates the magnetic media is accounted for and ready to be degaussed
- Green sticker - indicates the magnetic media has been degaussed
- Blue sticker - indicates the magnetic media was not found on previous inventories and must be duplicated
- Yellow sticker - indicates that a computer has had all magnetic media removed
I cannot stress enough how important two-person control is during each part of the disposal process. Errors and mistakes creep into any system when people are performing repetitive tasks. The disposal process is very repetitive and there is a very human tendency to rush to finish an unpleasant task. To combat the tedium of the process we recommend allotting a reasonable number of computer systems and magnetic media to be inventoried and recorded each day. Personnel should take scheduled breaks to help ward off complacency due to boredom. Each computer should be checked by two personnel to ensure that all magnetic media has been removed before it is cleared to move on.
In next week's post, I'll cover the degaussing and physical destruction process (and fill you in on which degausser you should avoid at all costs). |
|
Written by Jason Briody
|
|
Monday, 24 August 2009 10:19 |
|
According to the Carnegie Mellon University study "Predicting Social Security numbers from public data," the predictability of your SSN depends on a few factors, but in up to 44% of cases, the first five digits of your nine-digit social can be guessed on the first try.
Specifically, if you were born between 1989 (when people nationwide first began to receive SSNs at birth) and 2003, and your birth date and location are available, Alessandro Acquisti and Ralph Gross claim that forty-four percent of these people could have the first five digits of their social security numbers accurately predicted in a single attempt.
The full study is interesting, but lengthy (six pages of small-font, single-spaced, double-column text) Below I've outlined a few plain-English questions you might have about the study, its results, and some of my own thoughts about how this information can affect you and what you can do about it.
How did they predict the SSNs, and how did they know they were able to predict them correctly?
The researchers used data in a publicly-available file known as the Death Master File (DMF). According to the researchers, the DMF lists "...SSNs [social security numbers], names, dates of birth and death, and states of SSN application..." The file is used to curb the fraudulent use of deceased persons' socials.
The researchers then applied information made publicly available by the Social Security Administration (SSA). They explain that the first three digits of a SSN are assigned "based on the zipcode of the mailing address provided in the SSN application form" (which is why the researchers require a birth location to predict a social). The next two digits of a SSN and are assigned "in a precise but nonconsecutive order between 01 and 99" (which is why the researchers require a birth date to predict a social).
By correlating the data in the DMF with the information made available by the SSA regarding how socials are assigned, the researchers were able to establish the patterns the SSA uses to assign the first five digits of social security numbers. Once the researchers established a pattern, they tried to predict the SSNs of others in the DMF and used the full SSNs listed in the DMF as a check to see if they were "guessing" correctly.
What good are the first five digits without the last four?
Not much good. According to the study, it would take a high number of attempts to guess the last four.
So how could an attacker get those last four digits, then?
There are a number of ways, the most common of which is probably dumpster diving (going through your trash) for documents that contain your social.
What types of documents contain the last four digits of my SSN?
These vary, but anything from paychecks to college paperwork to bank and medical records. If not properly disposed of (e.g. micro cross-cut shredded), dumpster diving for these last 4 digits can be very effective.
If the first five digits can be predicted correctly by ID thieves using the researchers' methods, and then they obtain the last four by looking through your trash, they've got your full social. A full social can be used for a number of harmful and malicious activities, one of the most common being applying for new lines of credit in your name.
Aren't SSNs nowadays almost always partially redacted when you get them, just like how your ATM receipts only give a few digits of your account number? Do they redact the last four digits?
Yes, SSNs are partially redacted, but only the first five digits are obscured. The last four digits are visible. (i.e. XXX-XX-2071) The first five digits are the predictable ones; the last four are much more difficult to guess. Unfortunately, these four are the ones that are usually visible and used as identifiers.
So if birth data is all that's needed to predict partial SSNs, how do I know if my birth data is publicly available?
First, let's cover the most obvious ways it can be made available; you publish it. Many people have their birth dates and approximate birth locations on sites like Facebook and other social networking sites.
While this information can be easily hidden in privacy settings (Facebook, for instance, allows you to choose between publishing your full birthday, only the month and day, or not publishing your birthday at all) birth dates and locations can also be found elsewhere relatively easily. Just think about all the other records that may contain your birth information: voter, divorce, vital, DMV, correctional records and more.
If you don't believe that info is out there, you can easily check for yourself. Run a search for your full name at the free (but weak) BirthDatabase.com or zabasearch.com, or the powerful (but ~$2 per record) PeopleFinders.com. Your info is likely already out there for the dedicated ID thief.
I shred all sensitive documents, including those that contain just the last four digits of my social. Aside from dumpster diving, how can someone get those last four digits to complete my social?
The study mentions targeted phishing as another possibility. If someone sent you an email with the first five of your social visible and the last four redacted, and it looked official, you might feel safe responding to a request with your full social and other information (though you shouldn't). After all, if they have the first five digits, you might assume, they must have the last four digits as well and are just redacting them in the email for your privacy.
I also remember a radio contest a few years ago that used the last four digits of SSNs to pick winners, and people would call up and tell people their name, location, and the last four digits of their social, all on the air. I bet that contest would have turned out differently if those contestants knew the rest of their socials could be predicted with relative ease.
So what can I do to protect myself?
First, conceal information that could assist attackers from obtaining your birth data from sources you control (social networking, blogs, etc.). Securely file or cross-cut shred all documents containing Personal Identifying Information (PII), including the last 4 digits of your social. If your social is used as an identifier at college, work, or elsewhere, ask them to use a different identifier, if possible. And for more specific tips on how to lock down your information and not fall victim to ID thieves' common practices, read our tips on how to protect yourself in JDA's "PII Quest" (under the "Protect Yourself" pull-down). |
|
Written by Ryan Lerminiaux
|
|
Wednesday, 05 August 2009 09:44 |
|
As an attorney, you're fluent in legalese, but many of the folks you work with during e-discovery seem to only speak "IT." This third entry in the EDD Dictionary is set up just like the first (here); each common, EDD-related word is followed by its definition, the "attorney equivalent," and an example sentence. This entry focuses on IT-related acronyms that you may hear used often during an e-discovery or computer forensics case.
RAM
-noun: Acronym that stands for Random Access Memory. This is a dynamic type of data storage that requires power to maintain the data it stores (which means that, unlike a hard drive, once the computer is powered off, the information in RAM is effectively "erased" shortly thereafter). This type of storage allows data stored in RAM to be accessed in any order (unlike CDs and hard drives, on which data is stored on a specific physical location), and this increases data access speeds. Think of RAM as a desk that you can have papers lying on during the day but that are cleared off when you leave at night (as compared to a hard drive, which is more like a filing cabinet that remains untouched whether the lights are on or off in your office). Leaving papers on your "desk" means you can shuffle them around and access them really quickly, but unless you file them, they're gone when you shut the lights, just as RAM is gone when you shut off a computer.
Attorney Equivalent: memory, computer memory.
Example:
1. I need to add some more RAM to my home computer so I can run more than one program simultaneously without it freezing up.
2. We found a few items in memory before the computer was shut down that help prove that a virus was erasing files.
CD-ROM
-noun: Acronym that stands for Compact Disk-Read Only Memory. A thin disc made of plastic and a layer of aluminum. CD-ROMs are a form of optical disk storage (which means that data is written to the disc in a way that's visible; a laser burns tiny peaks and valleys into the surface of the disk). Anything from documents to audio and video files can be stored on these disks. CDs can normally hold around 700 megabytes of data.
Attorney Equivalent: compact disks, CDs, disks.
Example:
1. Can you pass me that CD-ROM? It has some important spreadsheets on it that I need to review.
DVD-ROM
-noun: Acronym that stands for Digital Versatile Disk or Digital Video Disk Read Only Memory. These disks are similar in appearance to CD-ROMs, except that DVDs can hold about six times as much data: roughly 4.7 gigabytes.
Attorney Equivalent: DVDs, disks.
Example:
1. I made you a DVD with all of our vacation photos on it.
FAT
-noun: Acronym that stands for File Allocation Table. Today FAT is a file system that is commonly used by thumb drives and external hard drives, the most common type being FAT32. FAT was also used as the file system for many versions of Windows until it was replaced by NTFS. The name "FAT" refers to a centralized table that contains information for all of the files stored in the system, such as file size and physical location (similar to how a written directory posted on a very large filing cabinet would give you details on where to find files and info on the files themselves.) If a thumb drive is FAT instead of the newer NTFS, very large files (4 gigabytes and up) cannot be stored and you will receive errors when trying to save or copy files. Even some new thumb and external drives come formatted with the FAT file system by default; they can be reformatted, however, if you plan on storing large files.
Attorney Equivalent: a file system.
Example:
1. Is this thumb drive formatted FAT16 or FAT32? |
|
Written by Jason Briody
|
|
Wednesday, 22 July 2009 13:31 |
|
There are a good amount of computer forensic myths out there, many of them brought about and reinforced by shows like CSI, Law and Order, and especially 24. Ryan Lerminiaux pointed out a number of these myths in an earlier post, "7 Myths about Computer Forensics." I ran into a new one the other day.
I was talking with someone while they were sitting at their computer, and suddenly, the program they were using crashed. The user cursed, hit the desk, and then said to me, "I bet this stuff never happens to you." "Why do you say that?" I asked. "Well, it's not like your forensic stuff crashes, right?"
MYTH: Computer forensic software is impervious to errors, glitches, and crashing.
FACT: Forensic software can be just as buggy as everything else.
A sizable part of our job as EDD and forensic consultants is troubleshooting items, pouring over log files, looking up error messages, finding software and hardware workarounds, and double-checking output. TV makes it look like we're all working on 54 inch flat panels, utilizing 100% visual software and breaking decryption in seconds, but that's just not the reality. Take this PDF troubleshooting document from AccessData, maker of one of the top forensic tools in the industry, Forensic ToolKit (FTK), for example.
The PDF shows how to "skip" processing on a certain file that repeatedly causes FTK to crash. I've experienced frustrations with FTK crashing all too often, and know that, as they say in the PDF, "you will need to reprocess the case when FTK crashes or hangs on a particular file." What this doesn't tell you is the amount of time it takes to "reprocess the case." Processing cases, depending on what options you choose, can take between 2-12 hours for the average laptop drive. So, if you had set up all the parameters, hit "start," and left for the night expecting to be able to work on a case in the morning, you just might be out of luck when you get to work.
But the difference lies in what happens after a program crashes. The person who wished he worked with forensic software merely clicked "Don't Send" on the "Please tell Microsoft about this problem" dialogue box that popped up and then reopened the program. But think about it; if Microsoft Office didn't recover your work (the tough reality with some forensic software), wouldn't you want to know what the issue was so it never happened again? With the time we invest, and a need to ensure that everything has been collected / copied / processed / analyzed (lest the smoking gun is simply overlooked), our first instinct is to get to the bottom of the problem. The best way to do that is often just to look at the log files that describe the crash, or at least describe the moments just before the crash.
Log files are like a real-time journal that a computer system writes in either time- or event-triggered intervals. Even if you're not aware of it, there are a great number of things being logged right now, as you read this sentence; the pages you're viewing with your Web browser, how long you've been editing those open Word documents, files checked by your virus scanner, the model number of your thumb drive, and much, much more. Next, we take action on what we find in that log file, whether it's patching a program, coming up with a workaround, or (depending on the software and the rarity of the problem) calling the developers and talking out the issue with them.
So, the next time a program of yours crashes, if the inconvenience warrants the time, do some investigating of your own and try checking out a log file and researching the error. You might find others who had the same issue or advice on a patch or workaround so you can avoid the problem in the future. Finding the problem won't be as awesome as TV makes it look, but if you're able to figure it out, you just might experience that sense of satisfaction that comes hand-in-hand with solving a problem. And that's something even CSI's Gil Grissom gets right; that sense of satisfaction that comes with a case rightly closed. |
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>
|
|
Page 1 of 7 |