Fortinet Document Library

Version:


Table of Contents

1.0.1
Copy Link

About the connector

NetBIOS (Network Basic Input/Output System) is a program that allows applications on different computers to communicate within a local area network (LAN). NetBIOS is used in Ethernet and Token Ring networks and, included as part of NetBIOS Extended User Interface (NetBEUI), in recent Microsoft Windows operating systems. It does not in itself support a routing mechanism so applications communicating on a wide area network (WAN) must use another "transport mechanism" (such as Transmission Control Protocol) rather than or in addition to NetBIOS.

 

NetBIOS provides three distinct services:

  • Name service (NS) for name registration and resolution (ports: 137/udp and 137/tcp)
  • Datagram distribution service for connectionless communication (port: 138/udp)
  • Session service for connection-oriented communication (port: 139/tcp)

This document provides information about the NetBIOS connector, which facilitates automated interactions, with NetBIOS using FortiSOAR™ playbooks. Add the NetBIOS connector as a step in FortiSOAR™ playbooks and perform automated operations, such as retrieving information about the hostname for an IP address that you have specified.

 

Version information

Connector Version: 1.0.1

Compatibility with FortiSOAR™ Versions: 4.10.3-161 and later

Compatibility with NetBIOS Versions: pysmb==1.1.22

 

Release Notes for version 1.0.1

Following enhancements have been made to the Exchange Connector in version 1.0.1:

  • Updated the parameter names in the Get Hostname operation.

 

Installing the connector

For the procedure to install a connector, click here.

 

Prerequisites to configuring the connector

  • You must install the pysmb python package.
  • You must enable NetBIOS on your machine.

 

Configuring the connector

For the procedure to configure a connector, click here.

 

Actions supported by the connector

The following automated operations can be included in playbooks and you can also use the annotations to access operations from FortiSOAR™ release 4.10.0 onwards:

 

Function Description Annotation and Category
Get Hostname Retrieves the hostname details for the IP address that you have specified. ip_lookup
Investigation

 

operation: Get Hostname

Input parameters

 

Parameter Description
IP Address IP address for which you want to retrieve the hostname details.
Port (Optional) NetBIOS-NS (Name Service) Port number.
Timeout (In Seconds) (Optional) Number of seconds the connector will wait for a response after which the operation will return None.

 

Output

The JSON output contains hostname details retrieved from NetBIOS, based on the IP address you have specified.

Following image displays a sample output:

 

Sample output of the Get Hostname operation

 

Included playbooks

The Sample - NetBIOS - 1.0.1 playbook collection comes bundled with the NetBIOS connector. This playbook contains steps using which you can perform all supported actions. You can see the bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the NetBIOS connector.

  • Get Hostname

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.

 

About the connector

NetBIOS (Network Basic Input/Output System) is a program that allows applications on different computers to communicate within a local area network (LAN). NetBIOS is used in Ethernet and Token Ring networks and, included as part of NetBIOS Extended User Interface (NetBEUI), in recent Microsoft Windows operating systems. It does not in itself support a routing mechanism so applications communicating on a wide area network (WAN) must use another "transport mechanism" (such as Transmission Control Protocol) rather than or in addition to NetBIOS.

 

NetBIOS provides three distinct services:

This document provides information about the NetBIOS connector, which facilitates automated interactions, with NetBIOS using FortiSOAR™ playbooks. Add the NetBIOS connector as a step in FortiSOAR™ playbooks and perform automated operations, such as retrieving information about the hostname for an IP address that you have specified.

 

Version information

Connector Version: 1.0.1

Compatibility with FortiSOAR™ Versions: 4.10.3-161 and later

Compatibility with NetBIOS Versions: pysmb==1.1.22

 

Release Notes for version 1.0.1

Following enhancements have been made to the Exchange Connector in version 1.0.1:

 

Installing the connector

For the procedure to install a connector, click here.

 

Prerequisites to configuring the connector

 

Configuring the connector

For the procedure to configure a connector, click here.

 

Actions supported by the connector

The following automated operations can be included in playbooks and you can also use the annotations to access operations from FortiSOAR™ release 4.10.0 onwards:

 

Function Description Annotation and Category
Get Hostname Retrieves the hostname details for the IP address that you have specified. ip_lookup
Investigation

 

operation: Get Hostname

Input parameters

 

Parameter Description
IP Address IP address for which you want to retrieve the hostname details.
Port (Optional) NetBIOS-NS (Name Service) Port number.
Timeout (In Seconds) (Optional) Number of seconds the connector will wait for a response after which the operation will return None.

 

Output

The JSON output contains hostname details retrieved from NetBIOS, based on the IP address you have specified.

Following image displays a sample output:

 

Sample output of the Get Hostname operation

 

Included playbooks

The Sample - NetBIOS - 1.0.1 playbook collection comes bundled with the NetBIOS connector. This playbook contains steps using which you can perform all supported actions. You can see the bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the NetBIOS connector.

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.