Power BI

Content by Charles Sterling

New Team Foundation Server Template: Security Development Lifecycle

The Microsoft Security Development Lifecycle team has just announced a new offering that makes writing secure code easier! This morning they released the Microsoft SDL Process Template for Visual Studio Team System. I have had several sneak peaks at this template and this thing really does rock, it gives you all the initial work items to do a great job of securing your process and the state changes to measure your efforts- Great Job Guys!



A security owner can accelerate the task of defining security requirements by opening up a query that includes all of the default SDL requirements – ready to triage and assign! There is also a custom work item to add your own requirements or recommendations.

Below: all SDL Requirements and Recommendations pre-loaded and ready to triage


For Developers!

Developers care about security, but they want it to be intuitive. The SDL Process Template includes check-in policies that will ensure every shelveset of code is taking advantage of the SDL required compiler/linker flags and Code Analysis features already in Visual Studio. This will eliminate entire classes of security weaknesses from your code!

Below: Setting Check-in policies


Below: Check-in policies in action


For Testers!

Testers want to be able to emphasize the importance of a security bug and properly communicate the impact to their product. The default “bug” work item now has customized security fields so you can identify security severity, and security cause/effect (using STRIDE), and mark a bug as “Blocking” or “Not Blocking.” This feature allows you to track and search for security-specific bugs.

Below: Identifying a bug as a security issue


For management!

The management team wants an easy-to-read document that summarizes the security work completed. The Final Security Review Report and Security Bugs Report provide an auditable set of artifacts that details security work completed as well as deferred tasks.

· Page One: status of all bugs marked as Security Bugs

· Page Two: completion status for the SDL Requirements and Recommendations

· Page Three: security bugs found by all tools integrated with the template

Below: Page 1 of the Final Security Review


I think the SDL Team has done a great job building a custom process template to address the challenge of making your code more secure. I would encourage you to go check it out and start making security a priority in your new team projects!