As I read the article:
Car Makers Haven’t Learned: Insecure Apps Expose Millions Of Connected Cars To Theft, Risks. I was reminded (again) that an issue for IoT devices is that their manufacturers have been slow to implement security for the software that runs on them. The focus has been on getting them out as quickly and as inexpensively as possible.
Most of our previous blogging about Dotfuscator Community Edition (CE) assumes you are doing local builds, or have a dedicated build server—but what if you want to use Dotfuscator CE within a distributed build system such as Visual Studio Team Services (VSTS) or Team Foundation Server (TFS) on-premises? Until now, you've had to do extra work to install and provision Dotfuscator CE on each build agent host in your pool. Now, we're pleased to announce a VSTS build extension for Dotfuscator CE, available in the VSTS Marketplace. It does the extra work for you, making it easy to get Dotfuscator CE into your distributed build.
PreEmptive Protection - Dotfuscator began life as the world's first .NET obfuscator; nearly fifteen years later, Dotfuscator has grown beyond just obfuscation to become the industry-standard .NET protection tool, able to protect your .NET applications against IP exposure, tampering, and unauthorized debugging.
We are pleased to announce that Visual Studio 2017 honors the tradition set by its predecessors and ships with a free copy of Dotfuscator Community (formerly Dotfuscator CE).
The most widely used .NET obfuscator – and now, much more
This morning, as we readied our latest Dotfuscator Community Edition (CE) announcement, it struck me that this remarkable piece of software has a unique story to tell. A story that can’t be expressed in a feature table or change log.
Released on September 31, 2016, Dotfuscator Professional 4.25 includes, for the first time, the ability to inject real-time detection, defense, and notification of unauthorized debugger use against production applications.
In the first "peek" into our soon to be published application risk management survey results, we shared that 58% of the respondents reported making ongoing development investments specifically to manage “application risk.” See Managing Application Vulnerabilities (an early peek into improved controls for your code and data)
I’m working on an application risk management study/survey focusing on the importance of one vulnerability exploit in particular: debugger hacks against production apps. Our initial data set already includes responses from 100+ developers targeting cloud, mobile and desktop platforms from 15+ countries.