Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

5/19/2009
12:18 AM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Microsoft Offers Free Template For Secure Software Development Process

SDL Process Template plugs directly into development tools

Microsoft today gave developers yet another free tool for adopting its Secure Development Lifecycle (SDL) program for secure coding -- a process template for incorporating SDL into their software development program.

The the SDL Process Template integrates Microsoft's SDL directly into third-party and enterprise software development environments. "It's a process template that bolts into Visual Studio and will help organizations in the adoption of SDL," says David Ladd, principal security program manager for Microsoft's SDL team.

Microsoft first beganopening up its internal Security Development Lifecycle (SDL) framework last fall to its third-party application developers and customers in the spirit of helping promote more secure software. Its SDL Optimization Model and SDL Threat Modeling Tool have been available for free since November, when the company also officially launched its SDL Pro Network of service providers, consulting, and training organizations including Cigital, IOActive, NGS Software, n.runs AG, and Verizon Business, which help developers deploy the SDL.

In addition to the template, Microsoft today also announced SDL Version 4.1 documentation, which includes updates to prior SDL requirements and recommendations, as well as online services and line-of-business application development guidelines. The software giant also announced two new members of its SDL Pro Network, the SANS Institute and SAIC.

Meanwhile, the new Process Template can help organizations better measure security, according to Microsoft's Ladd. The template contains dashboards, up-to-the-minute views of the development process, compliance status, and it gauges the effectiveness of security tools the organization is using in the SDL process, he says. It provides a way to measure the return on investment in security, he says.

The template automatically integrates SDL's policy, process, and tools, and handles security vulnerabilities, and sets up SDL requirements as work items in the development environment. It is tied heavily to Visual Studio, but Microsoft says developers can use the company's existing SDL XML schema tools to extend the template to other development environments.

"Visual Studio is a natural home for the template," Ladd says. "There are hundreds of thousands of people using [Visual Studio] on a daily basis."

It makes sense for Microsoft to pair the template first with Visual Studio, security experts say. "In general, I'd say that you have to start somewhere, and Microsoft will likely have the best success with integration into its own tools focused on its large development community," says Jon Oltsik, senior analyst with Enterprise Strategy Group Enterprise. "If it continues to resource this effort and gains momentum in its base, it can take SDL to the broader market over time."

Oltsik says adoption of Microsft's SDL by third party application developers is still in the early stages. "Things are rolling out slowly, but this is more a function of the esoteric topic -- secure software development -- and the fact that SDL is not a Microsoft profit center [rather] than the [poor] economy," Oltsik says. Microsoft's Ladd says the key is that these SDL tools make secure coding simple. "The fact that we have simplified things allows organizations to get security gains, and not having to have all of their development teams be security experts. That's very important for us," Ladd says.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...