Request for a custom application connector
  • 3 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Request for a custom application connector

  • Dark
    Light
  • PDF

Overview

Connectors are software components that help in reducing the interoperability burden in heterogeneous environments. To create a custom host / device / application DNIF will provide the connector under the support program. Customers having an active support plan with DNIF need not pay additional for such connectors.

Customized Connector Requirement

  • Submit a request for custom connector requirement to your DNIF Business Account Manager

  • Once the Design approval and Cost approval is finalized, follow the steps below.

How to initiate a request

  • Raise a ticket / mail to support@dnif.it , the mail should include the following details.
  • Describe the usage of this new connector requirement:
    • To forward logs from a device to DNIF
    • Integrate as a lookup plugin
    • Integrate as a trigger plugin
    • Others please specify
  • If your product / device / application is designed to send events over http(s) or syslog, send the following details to support@dnif.it .

Device details for Integration

Field Details
Company Name
Contact Person
EMail ID
Mobile Number

Partner Details (if any)

Field Details
Business Partner
Partner Contact
Requirement ( Specify Details) Example: Integrate a new device with my DNIF Deployment (Yes/No)

DNIF Details

Field Details
Scope Name
DNIF Version
OS Name & version

Device Details

Field Details
Device Type (Firewall / AV / Proxy etc)
Device OEM
Product Name and Version
Firmware Details
Logfile if there are logs generated from the device
Reference Document (if any)
OEM Docs on SIEM Integration

Other Details

Field Details
Is the device a commercially available / FOSS technology (Yes / No)
Is the device directly forwarding logs to DNIF (Yes / No / NA)
If No, how is the device integrated / planned to be integrated with DNIF
Have you read the DNIF Integration Support Policy (Yes / No)
  • If the product / device / application is a cloud application or requires an API to fetch or collect events, send the following details to DNIF:

API Integration

Field Details
Company Name
Contact Person
EMail ID
Mobile Number

Partner Details (if any)

Field Details
Business Partner
Partner Contact
Requirement ( Specify Details)
Example: Integrate a new device with my DNIF Deployment

DNIF Details

Field Details
Scope Name
DNIF Version
OS Name & version

Device Details

Field Details
Device Type (Firewall / AV / Proxy etc)
Device OEM
Product Name and Version
Firmware Details
Logfile if there are logs generated from the device
Reference Document (if any)
OEM Docs on SIEM Integration
Website URL
Product API guide / documentation
Trial codes if available
Test - API Endpoint - URL
Test - API Authentication details - username / password / secret key
Event type with field markers and field names

Other Details

Field Details
Is the device commercially available / FOSS technology (Yes / No)
Is the device directly forwarding logs to DNIF (Yes / No / NA)
If No, how is the device integrated / planned to be integrated with DNIF
Have you read the DNIF Integration Support Policy (Yes / No)
  • You will receive a Device Integration Acceptance Mail on the estimated time/days to create a new connector.
Note
  • Integration support will be provided on normal business hours, 8 x 5 as per IST.

  • Timeline for providing the draft API Plugin shall be 15 working days from the date of receiving requisite inputs.

  • DNIF team will revert with the pre-requisites (if any) for the integration purpose.

  • DNIF team will provide you the list of URLs/IP address/Port numbers that should be whitelisted.

Note
  • In case, DNIF team doesn’t have a testing environment, request you to arrange a live testing environment on your network.

  • Please confirm the ETA, so that a call can be scheduled to integrate the device. (A DNIF Engineer will assist you with the same).

Recommendations

  • All connectors should be tried in a test environment before being used in production.

  • All required backups and alternate copies be made before deploying a connector.


Was this article helpful?