The Rules Engine

Introduction to the Rules Engine

The rules engine lets you create custom rules for importing, categorizing, and combining findings from different plugins.

This feature is available to all Admin users and Authors can be given permission to access or manage the Rules Engine.

With the rules engine you can tag incoming findings, replace the body text of findings with an entry from your IssueLibrary, de-duplicate findings coming in from multiple scanners, and much more. Set up custom triggers so that these actions are applied when and where you need them.

What should trigger this rule?

Think of this section as the IF part of the classic if/then statement. The trigger determines when or if the action (described more in the next section) will be applied.

If you're dealing with multiple triggers, make sure to toggle the If ___ these statements apply selector to choose whether the trigger should occur when either all or any of the statements apply.

What actions should be performed?

If the trigger is the IF, the action is the THEN counterpart of the classic if/then statement. The trigger is the cause, the actions are the effect.

After establishing your triggers, it's time to outline what you want the Rules Engine to do every time that trigger condition is met.

Next help article: Condition: Match All →

Streamline InfoSec Project Delivery

Learn practical tips to reduce the overhead that drags down security assessment delivery with this 5-day course. These proven, innovative, and straightforward techniques will optimize all areas of your next engagement including:

  • Scoping
  • Scheduling
  • Project Planning
  • Delivery
  • Intra-team Collaboration
  • Reporting and much more...

Your email is kept private. We don't do the spam thing.