Fortinet FortiRecon ACI v1.1.0

About the connector

FortiRecon is a Digital Risk Protection Service (DRPS) product that provides an outside-the-network view to the risks posed to your enterprise.The Adversary Centric Intelligence (ACI) module leverages FortiGuard Threat Analysts to provide comprehensive coverage of dark web, open source, and technical threat intelligence, including threat actor insights. This information enables administrators to proactively assess risks, respond faster to incidents, better understand their attackers, and protect assets. This connector facilitates the automated operations related to ACI

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

Version information

Connector Version: 1.1.0

FortiSOAR™ Version Tested on: 7.4.0-3024

Fortinet FortiRecon ACI Version Tested on:

Authored By: Fortinet

Certified: Yes

Release Notes for version 1.1.0

Following enhancements have been made to the Fortinet FortiRecon ACI Connector in version 1.1.0:

• Data ingestion capability now helps threat intel report module fetch reports from FortiRecon ACI for the Threat Intel Management Solution Pack

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-fortirecon-aci

Prerequisites to configuring the connector

• You must have the URL of Fortinet FortiRecon ACI server to connect and perform automated operations and credentials to access that server.
• The FortiSOAR™ server should have outbound connectivity to port 443 on the Fortinet FortiRecon ACI 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 FortiRecon ACI 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 IOCs

Input parameters

Output

The output contains the following populated JSON schema:

{
    "hits": [
        {
            "ioc": "",
            "ioc_type": "",
            "report_id": "",
            "report_title": ""
        },
        {
            "ioc": "",
            "ioc_type": "",
            "report_id": "",
            "report_title": ""
        }
    ],
    "page": "",
    "size": "",
    "total": ""
}

operation: Get Leaked Cards

Input parameters

Output

The output contains the following populated JSON schema:

{
    "hits": [
        {
            "bank_name": "",
            "base_name": "",
            "bg_code": "",
            "bin": "",
            "brand_name": "",
            "category": "",
            "city": "",
            "country": "",
            "expiry": "",
            "holder_name": "",
            "index_ts": "",
            "org_id": "",
            "price": "",
            "shop_name": "",
            "state": "",
            "type": "",
            "unique_id": "",
            "zip": ""
        }
    ],
    "page": "",
    "size": "",
    "total": ""
}

operation: Get Widgets

Input parameters

Output

The output contains the following populated JSON schema:

{
    "hits": [
        {
            "id": "",
            "name": ""
        },
        {
            "id": "",
            "name": ""
        },
        {
            "id": "",
            "name": ""
        }
    ],
    "page": "",
    "size": "",
    "total": ""
}

operation: Get OSINT Feeds

Input parameters

Output

The output contains the following populated JSON schema:

{
    "hits": [
        {
            "content_snippet": "",
            "is_latest": "",
            "link": "",
            "publish_date": "",
            "tags": [
                "",
                ""
            ],
            "title": "",
            "widget_id": "",
            "widget_name": ""
        }
    ],
    "page": "",
    "size": "",
    "total": ""
}

operation: Get Reports

Input parameters

Output

The output contains the following populated JSON schema:

{
    "hits": [
        {
            "adversary": [
                ""
            ],
            "geography": [
                ""
            ],
            "industry_tags": [
                ""
            ],
            "information_date": "",
            "information_reliability": "",
            "motivation": "",
            "publish_date": "",
            "relevance_rating": "",
            "report_id": "",
            "report_title": "",
            "report_type": "",
            "source_category": "",
            "source_name": "",
            "source_reliability": "",
            "status": "",
            "summary": "",
            "threat": [
                "",
                ""
            ],
            "tlp": ""
        }
    ],
    "page": "",
    "size": "",
    "total": ""
}

operation: Get Reports With IOCs

Input parameters

Output

The output contains the following populated JSON schema:

{
    "adversary": [
        ""
    ],
    "category": "",
    "customer_tag": "",
    "geography": [
        ""
    ],
    "industry_tags": [
        ""
    ],
    "information_date": "",
    "information_reliability": "",
    "ioc": [],
    "motivation": "",
    "publish_date": "",
    "relevance_rating": "",
    "report_id": "",
    "report_title": "",
    "source_name": "",
    "source_reliability": "",
    "status": "",
    "summary": "",
    "tags": [
        "",
        ""
    ],
    "tlp": "",
    "type": ""
}

operation: Get Stealers Log

Input parameters

Output

The output contains the following populated JSON schema:

{
    "hits": [
        {
            "affiliated_domains": "",
            "country": "",
            "discovery_date": "",
            "isp": "",
            "last_updated": "",
            "marketplace": "",
            "org_id": "",
            "price": "",
            "sites": "",
            "state": "",
            "stealer_name": "",
            "vendor": ""
        }
    ],
    "page": "",
    "size": "",
    "total": ""
}

Included playbooks

The Sample - Fortinet FortiRecon ACI - 1.1.0 playbook collection comes bundled with the Fortinet FortiRecon ACI 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 FortiRecon ACI connector.

• FortiRecon ACI Report > Fetch
• FortiSOAR Threat Feeds Using FortiRecon ACI Report > Create
• Get FortiRecon ACI Report IOC
• On Create > Map Adversary to MITRE Groups/Techniques/Software
• On Update > Map Adversary to MITRE Groups/Techniques/Software
• Map Adversary to MITRE Groups/Techniques/Software
• Get IOCs
• Get Leaked Cards
• Get OSINT Feeds
• Get Reports
• Get Reports With IOCs
• Get Stealers Log
• Get Widgets

NOTE: In the Threat Intel Management Solution Pack's Threat Intel Report module we fetch reports containing indicators whose source category is Technical Intelligence.

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.

Data Ingestion Support

Use the Data Ingestion Wizard to easily ingest data into FortiSOAR™ by pulling reports from Fortinet FortiRecon ACI. Currently, reports in Fortinet FortiRecon ACI are mapped to Threat Intel Management in FortiSOAR™. For more information on the Data Ingestion Wizard, see the Connectors Guide in the FortiSOAR™ product documentation.

Configure Data Ingestion

You can configure data ingestion using the Data Ingestion Wizard to seamlessly map the incoming FortiRecon ACI reports to Threat Intel Management in FortiSOAR™.

The Data Ingestion Wizard enables you to configure scheduled pulling of data from FortiRecon ACI into FortiSOAR™. It also lets you pull some sample data from FortiRecon ACI using which you can define the mapping of data between FortiRecon ACI Reports and FortiSOAR™. The mapping of common fields is generally already done by the Data Ingestion Wizard; users mostly require to only map any custom fields that are added to the FortiRecon ACI reports.

1. To begin configuring data ingestion, click Configure Data Ingestion on the FortiRecon ACI connector's Configurations page.
   Click Let's Start by fetching some data, to open the Fetch Sample Data screen.
   
   Sample data is required to create a field mapping between FortiRecon ACI reports and FortiSOAR™ Threat Intel Management. The sample data is pulled from connector actions or ingestion playbooks.

2. On the Fetch Data screen, provide the configurations required to fetch reports from FortiRecon ACI. You can specify the Pull Reports Created in Past X Hours reports from FortiRecon ACI. The fetched data is used to create a mapping between the FortiRecon ACI reports and FortiSOAR™ Threat Intel Management.
   
   Once you have completed specifying the configurations, click Fetch Data.

3. On the Field Mapping screen, map the fields of a FortiRecon ACI reports to the fields of Threat Intel Management present in FortiSOAR™.
   
   For more information on field mapping, see the Data Ingestion chapter in the Connectors Guide in the FortiSOAR™ product documentation. Once you have completed mapping fields, click Save Mapping & Continue.

4. (Optional) Use the Scheduling screen to configure schedule-based ingestion, i.e., specify the polling frequency to FortiRecon ACI, so that the content gets pulled from the FortiRecon ACI integration into FortiSOAR™.
   On the Scheduling screen, from the Do you want to schedule the ingestion? drop-down list, select Yes.
   In the Configure Schedule Settings section, specify the Cron expression for the schedule. For example, if you want to pull data from FortiRecon ACI every 5 minutes, click Every X Minute and in the minute box enter */5. This would mean that based on the configuration you have set up, data, i.e., indicators will be pulled from FortiRecon ACI every 5 minutes.
   
   Once you have completed scheduling, click Save Settings & Continue.

5. The Summary screen displays a summary of the mapping done, and it also contains links to the Ingestion playbooks. Click Done to complete the data ingestion and exit the Data Ingestion Wizard.