Fortinet FortiWeb Cloud v1.0.0

About the connector

FortiWeb Cloud is an cloud native SaaS based web application firewall (WAF) that protects web applications & APIs from the Open Worldwide Application Security Project's (OWASP) Top 10 threats, zero-day attacks, and other application layer attacks.

This document provides information about the Fortinet FortiWeb Cloud Connector, which facilitates automated interactions, with a Fortinet FortiWeb Cloud server using FortiSOAR™ playbooks. Add the Fortinet FortiWeb Cloud Connector as a step in FortiSOAR™ playbooks and perform automated operations with Fortinet FortiWeb Cloud.

Version information

Connector Version: 1.0.0

FortiSOAR™ Version Tested on: 7.4.2-3279

Fortinet FortiWeb Cloud Version Tested on: 23.3.a

Authored By: Fortinet

Certified: Yes

Installing the connector

Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.

You can also use the yum command as a root user to install the connector:

yum install cyops-connector-fortinet-fortiweb-cloud

Prerequisites to configuring the connector

• You must have the credentials of Fortinet FortiWeb Cloud server to which you will connect and perform automated operations.
• The FortiSOAR™ server should have outbound connectivity to port 443 on the Fortinet FortiWeb Cloud server.

Minimum Permissions Required

• Not applicable

Configuring the connector

For the procedure to configure a connector, click here

Configuration parameters

In FortiSOAR™, on the Connectors page, click the Fortinet FortiWeb Cloud connector row (if you are in the Grid view on the Connectors page) and in the Configurations tab enter the required configuration details:

Actions supported by the connector

The following automated operations can be included in playbooks and you can also use the annotations to access operations:

operation: Get Incident Dashboard Details

Input parameters

Output

The output contains the following populated JSON schema:

Output schema when you choose Widget Name as Threats Timeline:

{
    "start": "",
    "end": "",
    "line_data": [
        {
            "line_name": "",
            "number": [
                {
                    "id": "",
                    "value": "",
                    "time": ""
                }
            ]
        }
    ]
}

Output schema when you choose Widget Name as Incidents Timeline:

{
    "start": "",
    "end": "",
    "line_data": [
        {
            "line_name": "",
            "number": [
                {
                    "id": "",
                    "value": "",
                    "time": ""
                }
            ]
        }
    ]
}

Output schema when you choose Widget Name as Source Country:

[
    {
        "name": "",
        "value": ""
    }
]

Output schema when you choose Widget Name as Attack Type:

[
    {
        "name": "",
        "percentage": ""
    }
]

Output schema when you choose Widget Name as High Risk:

[
    {
        "incident_id": "",
        "platform": "",
        "risk": "",
        "name": ""
    }
]

Output schema when you choose Widget Name as HTTP Host:

[
    {
        "name": "",
        "threat_count": "",
        "monitor_count": "",
        "block_count": "",
        "platform": ""
    }
]

operation: Get Incidents List

Input parameters

Output

The output contains the following populated JSON schema:

{
    "total": "",
    "result": [
        {
            "incident_id": "",
            "platform": "",
            "risk": "",
            "description": "",
            "threat_count": "",
            "block_count": "",
            "tags": [],
            "lasttime": "",
            "create_time": "",
            "blocked": "",
            "host_desc": "",
            "app_names": []
        }
    ]
}

operation: Get Incident Details

Input parameters

Output

The output contains the following populated JSON schema:

{
    "incident_id": "",
    "platform": "",
    "risk": "",
    "description": "",
    "threat_count": "",
    "block_count": "",
    "tags": [],
    "lasttime": "",
    "create_time": "",
    "blocked": "",
    "host_desc": "",
    "app_names": [],
    "comments": [],
    "attack_types": [],
    "cve_ids": [],
    "hosts": [],
    "src_countries": [],
    "firsttime": "",
    "src_ips": [],
    "http_urls": []
}

operation: Get Incident Timeline Details

Input parameters

Output

The output contains the following populated JSON schema:

{
    "start": "",
    "end": "",
    "line_data": [
        {
            "line_name": "",
            "number": [
                {
                    "id": "",
                    "value": "",
                    "time": ""
                }
            ]
        }
    ]
}

operation: Get Insight Events Summary

Input parameters

None.

Output

The output contains the following populated JSON schema:

{
    "detail": "",
    "result": {
        "summary": [
            {
                "type": "",
                "active": ""
            }
        ]
    }
}

operation: Get Incident Aggregated Details

Input parameters

Output

The output contains the following populated JSON schema:

Output schema when you choose Group By as Logs:

{
    "total": "",
    "result": [
        {
            "msg": "",
            "log_id": "",
            "threat_level": "",
            "signature_cve_id": "",
            "owasp_top10": "",
            "main_type": "",
            "http_url": "",
            "srccountry": "",
            "src_ip": "",
            "signature_id": "",
            "date_time": "",
            "sub_type": "",
            "action": "",
            "msg_id": "",
            "country_flag": "",
            "_id": ""
        }
    ]
}

Output schema when you choose some other option in Group By parameter:

{
    "total": "",
    "result": [
        {
            "name": "",
            "threat_count": "",
            "monitor_count": "",
            "block_count": "",
            "platform": ""
        }
    ]
}

operation: Get Insight Events

Input parameters

Output

The output contains the following populated JSON schema:

Output schema when you choose Event Type as Exposed Server:

{
    "detail": "",
    "result": {
        "type": "",
        "events": [
            {
                "id": "",
                "app_name": "",
                "origin_server": [],
                "exposed_dns": "",
                "direct_access": "",
                "last_updated": ""
            }
        ],
        "prev_cursor": "",
        "next_cursor": "",
        "total": ""
    }
}

Output schema when you choose Event Type as Trust IP:

{
    "detail": "",
    "result": {
        "type": "",
        "events": [],
        "prev_cursor": "",
        "next_cursor": "",
        "total": ""
    }
}

Output schema when you choose Event Type as Unprotected Host:

{
    "detail": "",
    "result": {
        "type": "",
        "events": [],
        "prev_cursor": "",
        "next_cursor": "",
        "total": ""
    }
}

Output schema when you choose Event Type as Monitor Service:

{
    "detail": "",
    "result": {
        "type": "",
        "events": [],
        "prev_cursor": "",
        "next_cursor": "",
        "total": ""
    }
}

Output schema when you choose Event Type as WAF Config Alarm:

{
    "detail": "",
    "result": {
        "type": "",
        "events": [
            {
                "id": "",
                "app_name": "",
                "configuration": "",
                "status": "",
                "last_updated": ""
            }
        ],
        "prev_cursor": "",
        "next_cursor": "",
        "total": ""
    }
}

Included playbooks

The Sample - Fortinet FortiWeb Cloud - 1.0.0 playbook collection comes bundled with the Fortinet FortiWeb Cloud connector. These playbooks contain steps using which you can perform all supported actions. You can see bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Fortinet FortiWeb Cloud connector.

• Get Incident Aggregated Details
• Get Incident Dashboard Details
• Get Incident Details
• Get Incident Timeline Details
• Get Incidents List
• Get Insight Events
• Get Insight Events Summary

Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during connector upgrade and delete.