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.

Application Security

12/1/2016
09:34 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Microsoft 'Father Of SDL' Named To Top Post At SAFECode

Steve Lipner, the former Microsoft security leader credited with spearheading its security development lifecycle (SDL) initiative, takes on a new role as executive director at SAFECode.

The Software Assurance Forum for Excellence in Code (SAFECode) has a new executive director with today's appointment of Steve Lipner, former chairman of the organization and former partner director of software security at Microsoft.

SAFECode was founded in 2007 by tech companies including Microsoft, Symantec, SAP AG, Juniper Networks, and EMC, with the goal of identifying and sharing best practices for building more secure hardware, software, and services.

Lipner is assuming leadership of the nonprofit after four decades in software security assurance. During his time at Microsoft, he led corporate supply chain security strategies and policies for government evaluation of Microsoft's security portfolio. He's known as the "father of SDL" at Microsoft.

"I was responsible for getting the security development lifecycle [SDL] created and accepted as a mandatory practice across the company," he explains, noting this was his largest contribution to the company.

"It basically changed what we did for customers in terms of enabling them to look to us and say they understood we were committed to security, and they were seeing the effects of that," he continues. "That was a significant change for customer security and as far as I'm concerned, it's the biggest impact I had in my career."

In his new role, Lipner will help companies develop open frameworks for evaluating software security and deliver free in-house training. While there has been progress made in establishing software security best practices, more needs to be done so all businesses adopt them.  

"One of the things I learned in 2016 is that although we have a lot of effective practices for software security, they are still not universally applied," he says. "It's important for organizations to apply secure development practices consistently and broadly."

Lipner cites SAFECode's Fundamental Practices for Secure Software Development an early effort to share best practices. The document discusses topics like safe cryptography practices and the importance of threat modeling and analysis. New information is added as new technologies become important over time; the most recent update was issued in 2014. 

This type of effort is critical at a time when most organizations can anticipate they'll be affected by a security breach.

In 1999-2000, when Lipner started at Microsoft, vulnerabilities were being discovered and reported but not routinely exploited. A few years later, there was less reporting of vulnerabilities and more malicious exploit code, which has contributed to a rise in attacks.

As cybercrime continued to grow, businesses adopted more secure software development practices. However, adoption has not been universal. Most people are unaware the software they're writing is security critical until an attack takes place.

"Perfection is hard, but you can certainly raise the bar and make attackers look somewhere else," Lipner notes. In 2017, he anticipates a mix of old and new security threats from the Internet of Things, phishing, and website attacks via SQL injection, a topic addressed in the aforementioned best practices document.

"There are organizations targeted by sophisticated attacks, but a lot are targeted by things it's possible to mitigate with best practices and paying attention," he explains.

For example, businesses must not only build secure software, but deploy it as well, to fully protect their data from attackers. If they don't adhere to administrative basics and set access control rights and manage user privilege, their oversight can have bad consequences.

Lipner officially begins his new position on Dec. 1. Current executive director Howard Schmidt, who led SAFECode for three years, will transition into a new role as executive director emeritus. 

"What I want to do is what I can to help SAFECode do a more effective job at developing and sharing secure practices appropriate to the evolving security environment and technologies, and share those with the community," he says of his goals.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
12/2/2016 | 2:30:51 AM
The Underestimated Steve Lipner
Anyone who follows Microsoft exploits has followed Steve Lipner, too.  I've been following his blog at MS and watching Microsoft's SDL evaolve and improve over the years.  Honestly, I feel Steve is one of those guys that, especially in recent years, is looked at as part of the old generation of techies; a graybeard.  But I wouldn't discount Steve, especially as someone who follows his career and work.  This is a great opportunity for SAFECode since today's InfoSec world seems to be a division between young hacker flashiness and serious BI types.  Like many of the suited graybeards, Steve has spent years focused on repeatable process, putting SDL through iterations of process improvement and all the while writing about this experience for others to learn from.  Guilty of the flashiness myself, as I get older and come close to graybeard status, I appreciate more and more people like Steve and their innovations in InfoSec process improvement.  Definitely a management move to watch and a company to keep and eye on for big changes coming down the road.   
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-24368
PUBLISHED: 2021-06-20
The Quiz And Survey Master – Best Quiz, Exam and Survey Plugin WordPress plugin before 7.1.18 did not sanitise or escape its result_id parameter when displaying an existing quiz result page, leading to a reflected Cross-Site Scripting issue. This c...
CVE-2021-31664
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-33185
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
CVE-2021-33186
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-31272
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.