SBN

CISO Thoughts with David Lindner – April 1

Skip to content

CISO Thoughts with David Lindner – April 1

CISO Thoughts with David Lindner - April 1

Insight #1

Spring4Shell, the latest vulnerability in a Java ubiquitous library is the second major vulnerability in the last 4 months. It’s time we get focused on how we secure our open source by employing easier upgrade paths and utilizing instrumentation-based protections from attacks against 0-days.
 

Insight #2

Security should be designed as “secure by default,” especially when it comes to third-party libraries and frameworks. Requiring a developer to read the documentation to strengthen the security configurations or even to turn on security, who on average import 126+ different third-party libraries, is a bad approach. Security should be strong out of the box, adding documentation about how to tweak the configuration if needed, with detailed implications of doing so.

 

Insight #3

Security ops teams in organizations that make heavy use of SaaS-based services should be ingesting and monitoring any logs they can to detect malicious actions. Most SaaS services have a logging facility you can offload into your SIEM. Start with your highest risk systems today.

 

David Lindner, Chief Information Security Officer

David Lindner, Chief Information Security Officer

David is an experienced application security professional with over 20 years in cybersecurity. In addition to serving as the chief information security officer, David leads the Contrast Labs team that is focused on analyzing threat intelligence to help enterprise clients develop more proactive approaches to their application security programs. Throughout his career, David has worked within multiple disciplines in the security field—from application development, to network architecture design and support, to IT security and consulting, to security training, to application security. Over the past decade, David has specialized in all things related to mobile applications and securing them. He has worked with many clients across industry sectors, including financial, government, automobile, healthcare, and retail. David is an active participant in numerous bug bounty programs.

Insight #1

Spring4Shell, the latest vulnerability in a Java ubiquitous library is the second major vulnerability in the last 4 months. It’s time we get focused on how we secure our open source by employing easier upgrade paths and utilizing instrumentation-based protections from attacks against 0-days.
 

Insight #2

Security should be designed as “secure by default,” especially when it comes to third-party libraries and frameworks. Requiring a developer to read the documentation to strengthen the security configurations or even to turn on security, who on average import 126+ different third-party libraries, is a bad approach. Security should be strong out of the box, adding documentation about how to tweak the configuration if needed, with detailed implications of doing so.

 

Insight #3

Security ops teams in organizations that make heavy use of SaaS-based services should be ingesting and monitoring any logs they can to detect malicious actions. Most SaaS services have a logging facility you can offload into your SIEM. Start with your highest risk systems today.

 

*** This is a Security Bloggers Network syndicated blog from AppSec Observer authored by David Lindner, Director, Application Security. Read the original post at: https://www.contrastsecurity.com/security-influencers/ciso-thoughts-with-david-lindner-april-1