Fortinet white logo
Fortinet white logo

Administration Guide

Automation

Automation

Automation features in FortiWeb can significantly enhance the security posture of your application by providing comprehensive monitoring and response capabilities.

In an Automation stitch, you can combine a trigger (e.g. High CPU, HA failover, FortiWeb Log, etc.) and several actions (e.g. Notifications, CLI Script, etc.) together, so that FortiWeb will take actions when certain trigger occurs. This stitching of triggers and actions ensures immediate responses to critical events, reducing downtime and enhancing security.

To create a stitch, you need to follow these steps:

  1. Create a Trigger: Define the event that will initiate the automation. See Creating a trigger.
  2. Set up an Action: Specify the action you want the system to perform when the trigger is activated. This could be sending a notification, running a CLI script, etc. See Creating an action.
  3. Stitch Everything Together: Integrate the trigger and actions into a stitch. This step effectively binds the trigger event with the specified actions. See Creating a stitch.
The Automation pages are only available under Global ADOM.

Refer to the following use cases to better understand the Automation feature:

Automation

Automation

Automation features in FortiWeb can significantly enhance the security posture of your application by providing comprehensive monitoring and response capabilities.

In an Automation stitch, you can combine a trigger (e.g. High CPU, HA failover, FortiWeb Log, etc.) and several actions (e.g. Notifications, CLI Script, etc.) together, so that FortiWeb will take actions when certain trigger occurs. This stitching of triggers and actions ensures immediate responses to critical events, reducing downtime and enhancing security.

To create a stitch, you need to follow these steps:

  1. Create a Trigger: Define the event that will initiate the automation. See Creating a trigger.
  2. Set up an Action: Specify the action you want the system to perform when the trigger is activated. This could be sending a notification, running a CLI script, etc. See Creating an action.
  3. Stitch Everything Together: Integrate the trigger and actions into a stitch. This step effectively binds the trigger event with the specified actions. See Creating a stitch.
The Automation pages are only available under Global ADOM.

Refer to the following use cases to better understand the Automation feature: