Software Security: How to Prioritize, Measure and Convey It To the Board
Amidst the shifting threat landscape, cloud migration and ongoing digital transformation, software security is often low or even last on the list of priorities for security leaders to address.
Yet, with the recent executive order on cybersecurity, and as headlines continue to feature high-profile breaches, board members at organizations across all industries are taking notice. Even though there are often designated technical experts on boards, there is now an increased awareness around cybersecurity – especially software security – even among the traditionally business-oriented members.
So, it’s important to prioritize software security and to tailor messages to the business functions so that they too can understand the organization’s risk posture. But communicating about software security to the board can be particularly challenging because of the ways that it differs from other security solutions. You don’t install a software security tool and count the breaches getting deflected; you change the way you develop software by building security in from the start. This is a significant pivot from traditional, reactive ways of thinking about security.
Security professionals are often faced with the following questions: How do we determine and justify the required resources for a software security program? How do we ensure – and prove – that development teams are adopting software security practices? Is our software security operating effectively? And how do we prove that?
Join ISMG’s Tom Field for an Executive Dinner Discussion featuring expert insight and case studies from Chris Wysopal, Founder and CTO at Veracode.
Yet, with the recent executive order on cybersecurity, and as headlines continue to feature high-profile breaches, board members at organizations across all industries are taking notice. Even though there are often designated technical experts on boards, there is now an increased awareness around cybersecurity – especially software security – even among the traditionally business-oriented members.
So, it’s important to prioritize software security and to tailor messages to the business functions so that they too can understand the organization’s risk posture. But communicating about software security to the board can be particularly challenging because of the ways that it differs from other security solutions. You don’t install a software security tool and count the breaches getting deflected; you change the way you develop software by building security in from the start. This is a significant pivot from traditional, reactive ways of thinking about security.
Security professionals are often faced with the following questions: How do we determine and justify the required resources for a software security program? How do we ensure – and prove – that development teams are adopting software security practices? Is our software security operating effectively? And how do we prove that?
Discussion topics will include:
- How have you approached the software security challenge – and where is it among your strategic priorities?
- How do you make the successful business case for a software security program?
- With a program in place, how do you ensure your developers are following your standards?
- How do you measure the success of your program?
- How do you communicate the metrics to your board and senior management?
Join ISMG’s Tom Field for an Executive Dinner Discussion featuring expert insight and case studies from Chris Wysopal, Founder and CTO at Veracode.
Tom Field
SVP of Editorial
ISMG
Chris Wysopal
Founder and CTO
Veracode
June 21, 2022 | 05:30 - 08:00 pm EDT | NYC (Venue TBD)
