Supply chain security risks are not new, but recent headlines are a reminder for consumers to re-examine their security practices. The story about the guy who hit his mule between the eyes with a 2×4 to “get his attention first” so the beast would then obey his gently whispered commands is memorable because it uses humor to make a serious point: Don’t wait to get clobbered before you pay attention to exhortations about what you ought to do.

The number of open source vulnerabilities discovered each year never seems to stop growing, emphasizing the importance of developers addressing them quickly and efficiently. However, simply identifying vulnerabilities is insufficient; their sheer scale makes it necessary to have an intelligent way of understanding which ones need to be fixed first to decrease the risk of a breach. For development teams in this environment, remediation prioritization and broad vulnerability coverage are critical.

Video game security risks are on the rise. Building security into your software development life cycle can help protect your reputation and customers. You’re supposed to have fun and relax when you’re playing video games—maybe with a bit of self-generated competitive stress. What you’re not supposed to do is have to worry about a hacker stealing your personal and financial information.

Fallback protocols could be causing slower tests when running with code coverage. Defining protocol implementations can improve the speed. Hi, I’m Philip Ross, a developer working on Tinfoil API Scanner at Synopsys Software Integrity Group. A few months ago, I sped up one of our test suites from about 6 minutes to around 20 seconds.

CVE-2020-27223 is a denial of service vulnerability discovered in the Eclipse Foundation’s popular Jetty web server.

The convenience of keyless entry systems can come at a price: your security. Learn how key fob hacks happen and why proactive security measures are a vital part of stopping them. With increased connectivity capabilities and larger and more complex software in automotive systems, modern vehicles are becoming more susceptible to cyber security attacks.

Fuzzing can be dangerous. After all, you’re trying to break things. In fuzzing, you deliver deliberately malformed inputs to software to see if the software fails. If it does, you’ve located a vulnerability and can go back to the code and fix it. It’s an excellent, proactive method for software development organizations to fix security weaknesses. And it should be no surprise that fuzzing is also the preferred method for attackers who want to locate zero-day vulnerabilities.

Application security testing tools help developers understand security concerns, but having too many tools can do more harm than good. Good tools are essential for building just about anything. But maybe that needs a bit more clarification: Not just good tools. They also have to be the right tools. Because the old cliché, “if all you have is a hammer, everything looks like a nail,” is a warning that using the wrong tool can mess everything up.

Selecting the perfect IAST solution for your organization’s needs can be difficult. Learn about the eight must-have features of any good IAST tool. Interactive application security testing (IAST) has quickly gained momentum in the application security (AppSec) space. According to Gartner, there was a 40% increase in inquiry volume around IAST in 2019. Why is IAST one of the fastest-growing AppSec tools?