What is one specific practice or architectural choice you recommend organizations adopt to stay ahead of rapidly emerging software vulnerabilities?

Most answers emphasize proactive, continuous, and automated security measures integrated early in development, while a few focus on inventory, limiting risk exposure, and openly sharing security tools.

14 answers

Answers

  • Nikesh Arora

    Chairman CEO · Palo Alto Networks

    Virtual Patching

    Nikesh Arora recommends virtual patching, saying his company writes signatures and puts a bandage around the perimeter so attackers cannot get in while customers patch underlying systems over time.

    David Senra · Watch on YouTube
  • Dave Bittner

    Producer & Podcast Host · N2k | Cyberwire

    Redesign Privileged Action Verification

    Dave Bittner is not shown giving this answer in the passage; the recommendations are attributed to Cynthia Kaiser, so no line can be written for Bittner.

    N2K Networks · Watch on YouTube
  • Casey Ellis

    Principal · Tall Poppy Group

    Limit Blast Radius

    Casey Ellis recommends that organizations identify the systems they rely on but can't patch or support, and have a plan to mitigate access to them, such as limiting blast radius, because attackers will target that class of risk and the cavalry isn't coming as quickly for it.

    Security Weekly - A CRA Resource · Watch on YouTube
  • James J Azar

    Chief Information Security Officer · Artera Services

    Expire Temporary Exceptions

    James J Azar recommends putting expiration dates on every "temporary" exception, arguing that trust must be measurable, scoped, and revocable by design.

    CISO Talk by James Azar · CISO Talk by James Azar · Read
  • Hari Mulackal

    Co-Founder & CEO · Cantina

    Self-Attack Testing

    Hari Mulackal recommends that organizations attack themselves in a safe way, simulating an attacker from the external surface, and then fix all the ways the simulated attack finds to breach them.

    The answer starts at 21:26.

    Bankless · Listen on Apple Podcasts
  • Dane Knecht

    CTO · Cloudflare

    Security in Every SDLC Step

    Dane Knecht says the software development life cycle will need to change, with security built into the process at every step, since we are patching 70 years of software and must keep pace going forward.

    No Priors: AI, Machine Learning, Tech, & Startups · Watch on YouTube
  • Tyler Shields

    Chief Marketing Officer · Allstacks

    AI-Driven Code Reviews

    Tyler Shields does not give this answer in the passage; the mention of AI-driven source code reviews comes from the other speaker, Dustin, not Shields.

    N2K Networks · Watch on YouTube
  • Alex Olivier

    Co-founder & CPO · Cerbos

    Fully Automated Risk Reduction

    Alex Olivier argues organizations should focus on reducing risk in a fully automated way to mitigate problems until patching is possible, rather than relying on patching speed, since he says fast patching isn't feasible.

    Security Weekly - A CRA Resource · Watch on YouTube
  • Joe Lonsdale

    General Partner · 8vc

    Openly Share AI Security Tools

    Joe Lonsdale recommends that organizations openly share AI security tools, arguing that lots of people should use intelligence to challenge everything rather than a single group working in secret.

    Joe Lonsdale · Watch on YouTube
  • Shardul Shah

    Partner · Index Ventures

    Continuous Security

    Shardul Shah recommends that organizations evolve quickly to continuous security, arguing that the older periodic model of security testing, where reports may or may not lead to action, no longer works going forward.

    TechCrunch · Watch on YouTube
  • Rob Allen

    Chief Product Officer · Threatlocker

    Asset Inventory

    Rob Allen names asset inventory as the first of three things he took from the conversation, saying organizations have been "horrible" at knowing who is running what agents and what data they hold.

    Security Weekly - A CRA Resource · Watch on YouTube
  • Bogomil Balkansky

    Partner · Sequoia Capital

    Secure-by-Default

    Bogomil Balkansky recommends organizations move to a secure-by-default posture, putting time and effort into building software that doesn't have vulnerabilities rather than building it and then scanning for flaws, since the scan-and-patch cycle takes months and is a road to nowhere.

    Technovation with Peter High (CIO, CTO, CDO, CXO Interviews) · Technovation with Peter High (CIO, CTO, CDO, CXO Interviews) · Listen at 35:19
  • Steve Stemmer

    Sr Account Executive · Chainguard

    Integrate Security Early

    Steve Stemmer says security needs to be built into the process early in the cycle, not treated as an afterthought at the end of development, and made part of the team's culture from the start.

    Fed Gov Today · Watch on YouTube
  • Joshua Corman

    Executive in Residence - Public Safety & Resilience · Institute For Security And Technology (Ist)

    Identify Network Assets

    Joshua Corman recommends organizations identify what's on their network, saying that if they lack that ability they should get it soon.

    Security Weekly - A CRA Resource · Watch on YouTube

More Cyber Security questions

View all →