Crack down the crackers

Every criminal leaves some evidence behind. This is true not only in the real world, but also in its digital counterpart. More so these days, when systems are being cracked into everyday to gain illicit access to data. This is where Computer Forensics can play an important role.

This book presents the basics of computer forensics and incident response. Incident response is all about how to respond to a breach of information security. Will this book turn you into a computer forensics expert? Honestly, it won't.

The book is not a 'hands-on type' of security book as the name implies. However, it can be used as a starting point to build the basic foundation. The companion CD will also give you some of the basic software such as tools for forensic analysis, data recovery, password recovery, logging tools, etc.

A shortcoming of the book is that it focuses more on the Windows OS and less on other platforms. It also tends to focus more on the US scenario, much of which is not relevant in this country.

• Title: Incident response: Computer Forensics Toolkit
• Author: Douglas Schweitzer
• Publisher: Wiley Dreamtech India
• Pages: 323
• Price: Rs 450/-

Going mobile

As the name implies, this book is all about learning the basics of mobile and wireless technologies. And, it does a very good job of it.

The journey through the wireless spectrum starts off with basics in the first seven chapters. From the eighth chapter onwards, it's all about building smart client applications and wireless Internet applications. Topics such as Security have also been dealt with in the book.

Part four of the book is more of an introduction to information management application such as PIMs; location based services such as GPS and GIS; and technologies like Web services and M-services. Indeed this book will serve well as a quick reference guide.

• Title: Mobile and Wireless Design Essentials
• Author: Martyn Mallick
• Publisher: Wiley Dreamtech India
• Pages: 454
• Price: Rs 329/-

Internet Humour

The real meaning of Software Revision Codes

• 1.0: Also known as "one point uh-oh". We had to release because the lab guys had reached a point of exhaustion and the marketing guys were in a cold sweat of terror.
• 1.1: We fixed all the killer bugs.
• 1.2: Uh, we got a few new bugs fixing the killer bugs and so we had to fix them, too.
• 2.0: We did the product we really wanted to do to begin with. Mind you, it's really not what the customer needs yet, but we're working on it.
• 2.1: Well, not surprisingly, we broke some things in making major changes so we had to fix them. But we did a good job of testing now, so we don't think we introduced any new bugs.
• 2.2: One lousy typo error and you won't believe how much trouble it caused!
• 2.3: Some jerk found a deep-seated bug that's been there since 1.0 and we had to fix it!
• 3.0: Hey, we finally think we've got it right!
• 3.1: Of course, we did break a few little things.
• 4.0: More features. It's doubled in size now, by the way, and you'll need to get more memory and a faster processor.
• 5.0: We really need to go on to a new product, but we have an installed base out there to protect. We're cutting the staffing.
• 6.0: Since I'm leaving the company and I'm the last guy left in the lab who works on the product, I wanted to make sure that all the changes are incorporated before I go. They're talking about obsolescence planning but they'll try to keep selling it for as long as there's a buck or two to be made.