About This Tool

Primary Use Case

Key Features

• Integration with Uleska DevSecOps Platform
• Trigger security scans from Jenkins pipelines
• Support for both Freestyle and Pipeline Jenkins projects
• Configuration of multiple Uleska instances
• Ability to block builds on scan failure
• Uses API tokens securely stored in Jenkins credentials
• Supports specifying application and version UUIDs for targeted scans
• Plans for future feature expansion

Insights & Recommendations

Requires a valid Uleska Platform account and API token; API token must be stored securely in Jenkins credentials. Currently, the plugin's functionality is limited to initiating scans, with plans for expanded capabilities in future releases. Users should ensure correct UUIDs for applications and versions when configuring scans.

Installation

Sign up for a Uleska Platform account at https://www.uleska.com/
Obtain an API key from the Uleska Platform via API/Swagger after authentication
Navigate to Jenkins Global Configuration (Home > Manage Jenkins > Configure System)
Scroll to Uleska Configuration and click New Instance
Enter required fields: Name, URL (with schema, no path), and API Token Secret (stored in Jenkins credentials)
Save the Jenkins configuration

Usage

Smart Usage Notes

• Integrate the plugin to automatically gate Jenkins pipelines, blocking builds on detected vulnerabilities to enforce security policies.
• Leverage the plugin's API token management with Jenkins credentials to maintain secure authentication and reduce exposure risk.
• Combine Uleska scans with other static and dynamic analysis tools in the pipeline to create a comprehensive security testing suite.
• Use scan results to feed vulnerability dashboards and trigger automated remediation workflows, enhancing DevSecOps maturity.
• Plan for future plugin enhancements to include richer scan result reporting and integration with incident response platforms.

Security Capability Profile