The days when developers would create programs and "throw them over the wall" to deployment teams and admins are not that far behind us. More often these days, code reviews bring admins into the project earlier in the project cycle. That is because the World Wide Web has opened up corporate systems to the Whole Wide World.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Troubles have been plentiful in the Microsoft development space, but progress is being made. SearchVB.com recently conducted a Webcast with John Carpenter, DevPartner SecurityChecker product manager, Compuware Corp., who told us formal processes must be adopted to focus on the problem of analyzing vulnerabilities and managing risk in the ASP.NET environment.
Carpenter admits that the main developer concerns have long been features, functionality, and performance, while the QA testing crew has focused on function and load. But if teams do not adapt to the new reality of 'nefarious hackers at the gates,' all their best efforts will go up in smoke when they least expect it.
With a process in place, the solution is within reach. The steps are simple, although a lot goes into learning how best to minimize the attack surface and how to code securely. But Carpenter, in a worthwhile overview, points the way. The Webcast is available on-demand beginning Dec. 20. Sign up now!