Component analysis for application security

If you are into writing software you probably follow security practices to keep your application secure. Since most of the platforms are now open source we consume a lot of open source components in our projects.

It happened sometime back when a vulnerability was found in one of the popular components(log4j) and companies were clueless about the existence of any such issue as a result many kept running their software on the vulnerable version of log4j.

You may not have been impacted or attacked for that matter but never know when it's your turn, is best to have protection against scenarios where components/license used in thrid party component becomes vulnerable/outdated.

I recently stumbled upon Dependency-Track , it works in two parts:-

  • Identify the list of components in your project, which is also called the SBOM (Software bill of material). CycloneDX can be installed with just a few commands to generate SBOM.
  • Upload BOM to Dependency-Track using UI/API which then scans it against a list of the updated list of known vulnerabilities.
Once you know the issue has occurred, it gives you the upper hand and ample time to plan and fix the issue and stay ahead in the game.

To make life easy plugins are available for popular CI/CD tools like Jenkins which allows you to configure it in your pipeline. If you are not using component analysis I strongly suggest using it.

Dependency track ecosystem:-



Comments

Popular posts from this blog

Gitflow using source tree

RabbitMQ setup and cluster configuration on a windows network

Analyse log using plug and play FileBeat

Introduction to Blazor

.NET MAUI and Blazor to create windows/web and mobile application (.NET 6.0)

Clean Architecture

What Interview Is/Is Not for an interviewer

Estimation techniques

WCAG Accessibility