OsecT

SamurAI [Local] CollectorSamurAI [Cloud] Collector
Picture1.svgPicture1.svg

OsecT is an OT network visualization and threat detection service. Depending on your OsecT type, logs are forwarded to SamurAI using either a SamurAI Cloud Collector (HEC) or a SamurAI Local Collector:

OsecT typeTransportSamurAI Collector
OsecT BasicHTTPSSamurAI Cloud Collector (HEC)
OsecT SRAHTTPSSamurAI Cloud Collector (HEC)
OsecT EdgeSyslogSamurAI Local Collector

Follow the section that matches your OsecT type:

OsecT Basic / OsecT SRA

OsecT Basic and OsecT SRA forward logs to a SamurAI Cloud Collector (HEC). To complete this Integration you will need to:

1) From the SamurAI Portal:

2) From OsecT:

Connectivity Requirements

You must ensure the following connectivity requirements are available:

SourceDestinationPortsDescription
OsecTSamurAI Cloud Collector (HEC)TCP/443 (HTTPS)For log transmission

Create a SamurAI Cloud Collector (HEC)

OsecT Basic and OsecT SRA push events to a SamurAI Cloud Collector using the Splunk HTTP Event Collector (HEC) protocol. Create a Cloud Collector in the SamurAI Portal to obtain the API URL and Token required by OsecT.

  1. Login to the SamurAI Portal

  2. Click Telemetry and select Collectors from the main menu

  3. Click Create collector

  4. Select the Cloud collector tab

  5. Enter the following information:

    • Collector name - The name will appear in the SamurAI Portal for you to easily reference
    • Description - Optional but if completed will appear in the SamurAI Portal for you to easily reference
  6. Set Provider to Splunk HTTP Event Collector (HEC)

  7. Click Create collector

  8. Record the connection details presented for use when configuring OsecT:

    • API URL - the Cloud Collector (HEC) API URL (required for OsecT SRA)
    • Token - entered as the SIEM Authentication Token in OsecT (required for OsecT Basic and OsecT SRA)

Configure OsecT (Basic / SRA)

  1. (OsecT SRA only) Connect to OsecT via SSH and run the following command to configure log transmission to the SamurAI Cloud Collector (HEC):

    osect siem set --https_enable True --https_url <API URL>
    

    Replace <API URL> with the full API URL recorded in Create a SamurAI Cloud Collector (HEC) (for example, https://hec.<region>.mdr.security.ntt).

  2. Log in to the OsecT portal in your browser.

  3. From the menu on the left, click Learning & Detection Settings.

    OsecT Dashboard

  4. From the tabs at the top of the screen, click the Cooperation tab and select SIEM from the sub-menu.

    OsecT Learning & Detection Settings - Cooperation

  5. In the SIEM Authentication Token field, enter the Token recorded in Create a SamurAI Cloud Collector (HEC).

    OsecT SIEM Integration Settings

  6. Click Register to save the settings.

This completes the OsecT Basic / OsecT SRA integration configuration.

OsecT Edge

This guide describes the steps required to configure OsecT Edge to send syslog events to a SamurAI Local Collector deployed on your network.

Connectivity Requirements

You must ensure the following connectivity requirements are available:

SourceDestinationPortsDescription
OsecTSamurAI Local CollectorTCP/514 (syslog)For log transmission

Configure OsecT Edge

  1. Connect to OsecT via SSH.

  2. Run the following command to configure syslog forwarding to the SamurAI Local Collector:

    osect siem set --syslog_enable True --syslog_host <Local Collector IP address> --syslog_port 514
    
    • Set --syslog_host to the IP address of the SamurAI Local Collector deployed on your network.
    • Set --syslog_port to 514.

For integrations that utilize a Local Collector where we ingest syslog only, you do not need to follow specific steps in the SamurAI MDR portal as we auto detect the vendor and product. The only reason you need to use the SamurAI MDR portal is if you need to determine the Local Collector IP address. Of course you will still need to ensure the integration is functioning! See Integrations for more information on checking status.

Our Integration guide was accurate at the time of writing but vendors change things frequently! If you find errors or anything is outdated, let us know by raising a request in the SamurAI MDR Portal and we shall get it updated.