Application Security

12/1/2016
09:34 AM
Connect Directly
Twitter
LinkedIn
Google+
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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
No SOPA
50%
50%
No SOPA,
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.   
Tips for the Aftermath of a Cyberattack
Kelly Sheridan, Staff Editor, Dark Reading,  4/17/2019
Former Student Admits to USB Killer Attack
Dark Reading Staff 4/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-11332
PUBLISHED: 2019-04-18
MKCMS 5.0 allows remote attackers to take over arbitrary user accounts by posting a username and e-mail address to ucenter/repass.php, which triggers e-mail transmission with the password, as demonstrated by 123456.
CVE-2019-9161
PUBLISHED: 2019-04-18
WAC on the Sangfor Sundray WLAN Controller version 3.7.4.2 and earlier has a Remote Code Execution issue allowing remote attackers to achieve full access to the system, because shell metacharacters in the nginx_webconsole.php Cookie header can be used to read an etc/config/wac/wns_cfg_admin_detail.x...
CVE-2019-11015
PUBLISHED: 2019-04-18
A vulnerability was found in the MIUI OS version 10.1.3.0 that allows a physically proximate attacker to bypass Lockscreen based authentication via the Wallpaper Carousel application to obtain sensitive Clipboard data and the user's stored credentials (partially). This occurs because of paste access...
CVE-2019-11331
PUBLISHED: 2019-04-18
Network Time Protocol (NTP), as specified in RFC 5905, uses port 123 even for modes where a fixed port number is not required, which makes it easier for remote attackers to conduct off-path attacks.
CVE-2019-9160
PUBLISHED: 2019-04-18
WAC on the Sangfor Sundray WLAN Controller version 3.7.4.2 and earlier has a backdoor account allowing a remote attacker to login to the system via SSH (on TCP port 22345) and escalate to root (because the password for root is the WebUI admin password concatenated with a static string).