Resources
Resources

Adding A Custom Tool

Uleska can accommodate many different tools - dynamic testing, static analysis, AWS, GCP etc. It allows you to be specific to the types of...

Find out more

Uleska Tool Library

For you to easily create custom tools, Uleska has Python libraries in open source, which you can find here.

Find out more

Step 1 - Create a Script

This script conducts security checks. It could be calling other security tools, open source tools, calling APIs, it can be whatever you need it to...

Find out more

Step 2 - Wrap Script in Docker

In order to get the script working with a docker image, we need to supply some additional information. We need a requirements.xml file with the...

Find out more

Open Source Security Testing Tools

See our open source security testing tools

Find out more

Step 3 - Configure Uleska to Pick Up Docker

Go to the Uleska UI. We want to put the docker information into Uleska so it can have the custom tool and be able to run it through any CI/CD...

Find out more

Passing Schema and Hostname

We mentioned previously that SCHEMA and HOSTNAME information can be passed to the tool. This is done when setting up a test via the Applications...

Find out more

Using the Uleska CLI

To ease integration with CI/CD and similar systems, Uleska provides a Command Line Interface to invoke testing, extract and compare results, and...

Find out more

Help Text

 

Find out more

CLI Usage

    Parameters

Find out more
3 4 5 6 7