Skip to content

Latest commit

 

History

History
 
 

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

Exploitable path using CxSCA Resolver

  • Author: Pedric Kng
  • Updated: 22-Jul-21

This article describes the usage of CxSCA Resolver in a Jenkins declarative pipeline.


Overview

CxSCA is an on-premise package resolver to capture open source package in a project working in sync with the installed package managers, and sent the signatures/manifest to CxSCA cloud for analysis capability.

Additionally, CxSCA Resolver also provides capability to correlate with CxSAST to trace exploitable path from your proprietary source codes invoking vulnerable functions in open source packages. This helps in speedy triaging and prioritization of of CxSCA results.

Pre-requisites

Setup

The sample Jenkinsfile includes 4 stages;

  1. Cleanup -- Clean-up workspace
  2. Checkout -- Checkout source from git repository
  3. Build -- Execute maven build
  4. CxSCA -- Download CxSCA resolver, and execute scans

Miscellenous

CxSCA Resolver can also be dockerized as a base image for extension to include the relevant package managers, refer to dockerfile.

References

CxSCA Resolver [1]