Continued controversy over U.S. military spending makes it a useful allegory of issues that arise in allocating IT resources. In the same way that defense planners find billions for high-tech systems but fall short in simple tasks like armoring soldiers, IT planners may be constructing vast new server farms that offer up key intellectual property as a much too easy target.
Its hard enough to protect mere data in customer-facing systems: eWEEK Labs has shown, in four international hacking challenges, that theres a worldwide community of knowledgeable experts with both the tenacity and the access to online resources that are needed to find and exploit database vulnerabilities. Much more hazardous are the systems that expose applications, or actually download executable code, to client devices and their users.
“Releasing .Net and Java applications without obfuscating them is tantamount to distributing the source code,” observed Senior VP Sebastian Holst at Preemptive Solutions in response to one of my columns earlier this year—and as I said in that column, failing to take reasonable protective measures may be tantamount to yielding ownership rights. Yes, Holst has a dog in this fight: His company produces source obfuscation tools. That doesnt mean hes wrong, as anyone can independently determine by aiming any of several free decompilation tools at a companys code base.
Moreover, any issues of protecting intellectual property become even more complex as international markets become the major opportunities for sales growth—and also major centers of potential competition in commercial software development. I spoke last week with one software development executive who preferred not to have her company named, saying that theres no advantage to be gained in defying potential attackers to take them on: “We found international companies that do reverse engineering and arent really prevented from doing that,” she said, and “We found companies whose technology has been cracked and you can get the unblockers online; we found other companies whose solutions required compilation of their code into the executable, which would affect our release schedules.”
This conversation points up the role of reverse engineering, not just as a tool of attackers, but as a matter of national competitiveness. Some have argued, for example, that recent antitrust actions against Microsoft in Europe are the migration into the courtroom of a war that couldnt be won in the laboratories.
These developments shine the spotlight on todays announcement by V.i. Laboratories of Waltham, Mass., of that companys CodeArmor 2.0 technology for adding reverse-engineering protections to executable code. My conversations with V.i. developers and with the above-quoted customer of the company suggest that the product addresses an intimidating portfolio of possible attack modes, including some that Id never before considered involving code crackers use of sophisticated emulation environments.
As Ive previously observed, nothing is too hidden to hack, but the V.i. Labs customer that I interviewed last week was realistic about that. “Its a lock on the door,” she said. “It wont last for 10 years, but it will protect something for as long as it takes us to put out our next release in six months.” Thats a realistic perspective on a critical need for anyone whose code has to go out there and fight for a living.
Tell me what youre protecting, and how, at [email protected].