Custom Backend Configuration
Introduction
Sentio utilizes a custom backend for each implementation to let Sentio know from where to stream the data from. Sentio uses CORS:
Cross-Origin Resource Sharing (CORS) is an HTTP-header based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. CORS also relies on a mechanism by which browsers make a "preflight" request to the server hosting the cross-origin resource, in order to check that the server will permit the actual request. In that preflight, the browser sends headers that indicate the HTTP method and headers that will be used in the actual request.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS
Given that browsers require a certificate, Cybersift Support typically creates these DNS records during onboarding for convenience of not having to create your own.
Self Hosting the Backend DNS Record
Should you wish to host the backend DNS record yourself, this document will explain what is required. It’s important to inform Cybersift Support, so we can remove it from our end, and avoid conflicts.
❗Highly Discouraged
We recommend you do not create an internal DNS zone for the root “cybersift.io” domain as it may result into issues.
Creation of an Internal Zone
NB this involves creating a ZONE - not a DNS A record
Zone | Host | Answer |
|---|---|---|
myCustomName-sentio.cybersift.io | @ | (Points to your SIEM e.g. 192.168.1.2) |
Once a zone is created, simply add a root DNS record (usually denoted as @ ) which points to your internal SIEM IP
Test it out using
nslookup myCustomName-sentio.io Apply Your Backend
After the Internal Zone is created, you can test it out by:
Going to sentio.cybersift.io
Add your backend
Try to login
(Ensure that local network is allowed in site settings)
tags:
Custom Backend
Internal Zone
DNS Record