Skip to content

Cybersecurity Insights with Contrast CISO David Lindner | 11/24

By David Lindner, Chief Information Security Officer

November 24, 2023

incident response malicious actors regulatory

    
Cybersecurity Insights with Contrast CISO David Lindner | 11/24

Insight #1

It's the holiday season, and malicious actors are primed to take advantage of all the amazing deals you may be trying to purchase over the next few weeks. Listen to your intuition: If a deal is too good to be true, you are most likely right.

Insight #2

Are your incident response plans up to date? While lots of people shut down for the holidays, the attackers do not. What can you do now to prepare for another Log4j-like (PDF) incident over the holidays?

Insight #3

Are you always working to improve your security posture? If so, what drives this? Is it compliance or regulatory reasons, wanting to do the right thing, or a combination? If not, do you feel your security journey is already completed? 
incident response malicious actors regulatory
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.

Previous

Let’s talk stats: Why AppSec’s running on broken math
Next

Don’t throw good AppSec money after bad