Nissan North America reported a significant source code leak in January because of misconfigured Git servers. Today’s columnist, Landon Winkelvoss of Nisos, offers some advice on how security teams can safeguard source code. ykanazawa1999 CreativeCommons (Credit: BY-NC-SA 2.0)

Weak passwords and developer misconfigurations consistently lead to source code leaks from third-party repositories, even at large companies with robust security programs, such as Nissan North America. The consequences are often dramatic and long-lasting, including loss of competitive advantage and consumer confidence, depending on the nature and criticality of the source code.

While customer details may not get exposed, personally identifiable information (PII) often serves as the tip of the iceberg as previously unknown vulnerabilities and account takeover methods are revealed. Bad actors can then exploit the code in any number of ways, including creating counterfeit applications that undermine brand reputation.

Please register to continue.

Already registered? Log in.

Once you register, you'll receive:

  • News analysis

    The context and insight you need to stay abreast of the most important developments in cybersecurity. CISO and practitioner perspectives; strategy and tactics; solutions and innovation; policy and regulation.

  • Archives

    Unlimited access to nearly 20 years of SC Media industry analysis and news-you-can-use.

  • Daily Newswire

    SC Media’s essential morning briefing for cybersecurity professionals.

  • Learning Express

    One-click access to our extensive program of virtual events, with convenient calendar reminders and ability to earn CISSP credits.