Configuring HIBUN Connectors

This connector allows Stellar Cyber to ingest logs from HIBUN and add the records to the data lake. This connector integrates with the HIBUN SaaS API to query for log files.

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: HIBUN

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: No

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

Locating Records

Access Logs

Event Logs

Operation Logs

Syslog

msg_class:

hibun_access_log

hibun_event_log

hibun_operation_log

msg_origin.source:

hibun

msg_origin.vendor:

hibun

msg_origin.category:

endpoint

Domain

<API URL>

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

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials

  • Customer Code, Username and Password

               Let us know if you find the above overview useful.

Adding a HIBUN Connector

To add a HIBUN connector:

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

Obtaining HIBUN Credentials

Before you configure the connector in Stellar Cyber, you must obtain the following HIBUN credentials from Hitachi Solutions at https://www.hitachi-solutions.co.jp/hibun/sp/:

  • Customer Code

  • Username

  • Password

    • The password should not include non-ASCII special characters.

Adding the Connector in Stellar Cyber

To add a HIBUN 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 Endpoint Security from the Category drop-down.

  5. Choose HIBUN 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. The Interflow records created by this connector include this tenant name.

  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. Choose the API URL.

  13. Enter the Customer Code you obtained earlier.

  14. Enter the Username you obtained earlier.

  15. Enter the Password you obtained earlier.

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

  17. Choose the Log Types you would like to collect. The logs for Access Logs, Event Logs, and Operation Logs are supported.

  18. Click Next. The final confirmation tab appears.

  19. 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.

The following Stellar Cyber alert types are integrated with HIBUN:

  • Internal Account Login Failure Anomaly

  • Login Time Anomaly (with timezone set to UTC+9, Japan)