Configuring Indusface Connectors

This connector allows Stellar Cyber to ingest logs from Indusface and add the records to the data lake.

Connector Overview: Indusface

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: No

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

Locating Records

Attack Info

Syslog

msg_class:

indusface_attack_info

msg_origin.source:

indusface

msg_origin.vendor:

indusface

msg_origin.category:

waf

Domain

<Host>

where <Host> is a variable from the configuration of this connector

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials

  • Host, API ID, and API Key

               Let us know if you find the above overview useful.

Adding an Indusface Connector

To add an Indusface connector:

  1. Obtain Indusface credentials
  2. Add the connector in Stellar Cyber
  3. Test the connector
  4. Verify ingestion

Obtaining Indusface Credentials

Follow guidance on Indusface documentation to obtain the API ID, API key, and URL for Stellar Cyber API calls.

  1. Login as an administrative user to the Apptrana portal.

  2. Navigate to the User Profile drop-down.

  3. Choose Manage API Key.

  4. Note the API ID, Key, and Redirection URL in the dialog box. The Redirection URL is the Indusface host URL, for example: https://tas.indusface.com.

  5. Click Save.

Adding the Connector in Stellar Cyber

With the access information handy, you can add an Indusface connector in Stellar Cyber:

  1. Log in to Stellar Cyber.

  2. Click System | Integration | Connectors. The Connector Overview appears.

  3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

    The asterisk (*) indicates a required field.

  4. Choose Web Security from the Category drop-down.

  5. Choose Indusface from the Type drop-down.

  6. For this connector, the supported Function is Collect, which is enabled already.

  7. Enter a Name.

    This field does not accept multibyte characters.

  8. Choose a Tenant Name. This identifies which tenant is allowed to use the connector.

  9. Choose the device on which to run the connector.

  10. (Optional) When the Function is Collect, you can create Log Filters. For information, see Managing Log Filters.

  11. Click Next. The Configuration tab appears.

    The asterisk (*) indicates a required field.

  12. Enter the URL of the Indusface Host using the information you noted above. The Indusface host URL has the following format: https://<variable>.indusface.com, for example, https://tas.indusface.com.

  13. Enter the API ID you noted above.

  14. Enter the API Key you noted above.

  15. Choose the Interval (min). This is how often the logs are collected.

  16. Choose the Content Type. The logs for Attack Info are supported.

  17. Click Next. The final confirmation tab appears.

  18. Click Submit.

    To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

The new connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

For connectors running on a sensor, Stellar Cyber recommends that you allow 30-60 seconds for new or modified configuration details to be propagated to the sensor before performing a test.

  1. Click System | Integrations | Connectors. The Connector Overview appears.

  2. Locate the connector that you added, or modified, or that you want to test.

  3. Click Test at the right side of that row. The test runs immediately.

    Note that you may run only one test at a time.

Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful test indicates that you entered all of the connector information correctly.

To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the test fails, you can select the  button from the same row to review and correct issues.

The connector status is updated every five (5) minutes. A successful test clears the connector status, but if issues persist, the status reverts to failed after a minute.

Repeat the test as needed.

ClosedDisplay sample messages...

Success !

Failure with summary of issue:

Show More example detail:

 

Verifying Ingestion

To verify ingestion:

  1. Click Investigate | Threat Hunting. The Interflow Search tab appears.
  2. Change the Indices to Syslog. The table immediately updates to show ingested Interflow records.