Trickest Modules Onboarding

​

Introduction

Modules are tools that help automate specific security tasks. Whether it’s discovering assets (like hostnames), enriching asset details such as port scanning IP addresses, or running vulnerability scans, modules handle the heavy lifting. They take care of the implementation details, evolving methodologies, maintenance, scalability, and low-level resource management, allowing you to focus on what needs to be done rather than how to do it.

​

Getting Started

Modules are available in the Trickest library alongside tools and scripts. Find them under the Modules section in the library sidebar or search for specific ones using the search bar.

To use a module, simply drag and drop it into the workflow canvas.

Next, connect your inputs as needed.

You can also add more modules, tools, or scripts to extend your workflow.

Once you’re happy with the workflow, you can run (or schedule) it on as many machines as you need.

And there you have it! You’ve condensed what might have taken tens of hours of research, experimentation, and maintenance into minutes.

To give you a clearer picture of the benefits of adding modules to your toolkit, let’s explore their key features:

​

Modules are Refined

A great security testing methodology is rarely about one big idea—it’s about refining the small details. Each module is built on years of experience and hundreds of hours of fine-tuning to ensure every process is done precisely.

For more details on each module’s features and to understand why they often provide greater value compared to public tools, check out their individual descriptions (and feel free to do your own testing!)

​

Modules are Updated

The security research scene is always evolving, with new techniques, discoveries, and tools coming out regularly. While this keeps the industry moving forward, it can be tough to stay up-to-date. Keeping up usually means spending a lot of time reading, experimenting, and deciding which updates to incorporate and how to apply them.

Instead, you can count on our team to handle this for you. We stay on top of the latest research, refine new techniques into reliable tools, conduct extensive testing, and integrate this knowledge into modules. This way, your workflows automatically benefit from the latest and greatest research without any extra effort on your part.

​

Modules are Maintained

Automation aims to save time, but it also brings its own time commitments. These include keeping dependencies updated, monitoring performance, and ensuring that new updates and integrations don’t cause any adverse effects.

To manage this, all modules undergo rigorous and ongoing testing. This ensures that updates are integrated smoothly, compatibility is maintained, and performance remains consistent.

​

Modules are Scalable

Scalability in automation workflows involves managing several factors: the total number of inputs to process, the machines available, the maximum number of inputs each step can handle, and the minimum number needed before adding significant overhead. You must also consider potential performance bottlenecks.

Modules simplify this complexity by letting you focus only on the number of machines you want to use. They handle all other variables, perform the necessary calculations, and partition the data based on the specific needs of each step. This ensures your automation runs smoothly and efficiently, without burdening you with intricate and error-prone calculations.

​

Modules are Interoperable

While modules abstract away lots of details, no one understands your infrastructure, threat model, and organizational needs better than you. That’s why modules are not standalone entities; they are integrated into the Trickest workflow ecosystem. This integration allows you to use them alongside tools (whether public or private) and scripts (whether standard or custom).

Modules are also designed with output formats that facilitate easy integration with other components. They often support multiple outputs, each providing a natural integration point for various use cases. Their output files are always standardized, consistent, and documented.