Network Security
We that our customers need to be confident that they are communicating with nBold in a secure environment. This document outlines the key aspects of our network security.
Communication securityβ
Traffic encryptionβ
All the traffic from and to the nBold platform is encrypted (and HTTPS protocol enforced), usingβ―TLS v1.2, ensuring secure communication between our customers and our platform. To do so, weβre using Azure Front Door as the only entry point to the app (web apps and API).
You can review online our latest Certificate Report
You can see a detailed report of our SSL certificate using this free online service that performs a deep analysis of the configuration of our SSL:
Launch Qualys SSL Server Test
DDoS preventionβ
While we've prevented rogue traffic from accessing our servers and network, itβs still possible for external services to block anyone else from using our service by creating a distributed, denial-of-service attack.
To prevent this, we're using Azure Traffic Manager as a first level of protection.
Learn more about Azure Traffic Manager
Trusted domainsβ
Domains allow list is one of the most effective methods of ensuring this and prevents any internet traffic intended for nBold from being hijacked or rerouted to a rogue website.
Our complete portfolio of domains is outlined below to help our customers configure their corporate network security components.
This information is subject to change and we recommend that you check back quarterly for the addition of new domains.
nBold App and APIβ
- Domains/Hosts: *.salestim.io
- Justification/Purpose: nBold main web application for Microsoft Teams
nBold Documentationβ
- Domains/Hosts: *.nbold.co
- Justification/Purpose: nBold documentation embedded into the Microsoft Teams app
Microsoft Azure Application Insightβ
- Domains/Hosts:
- az416426.vo.msecnd.net
- dc.services.visualstudio.com
- Justification/Purpose: Azure service used by nBold to collect anonymous performance metrics, telemetry and application logs/traces. More infos
Microsoft Azure Blob Storageβ
- Domains/Hosts: stappsaprd.blob.core.windows.net
- Justification/Purpose: Storage used by nBold to store templates pictures/icons
Microsoft Graph APIβ
- Domains/Hosts: graph.microsoft.com
- Justification/Purpose: API used by nBold to interact with Microsoft 365 services
Intercomβ
- Domains/Hosts:
- *.intercom.com
- *.intercom.io
- *.intercomassets.com
- *.intercomcdn.com
- Justification/Purpose: Used by nBold to bring an embedded support system into the app, and connect end-users and administrators with our support team.
IP ranges allow listβ
IP ranges allow list is one of the most effective methods of ensuring this and prevents any internet traffic intended for nBold from being hijacked or rerouted to a rogue website.
Our public app and API services are exposed and protected by Microsoft Azure Front Door. Therefore our public IP ranges are publicly documented by Microsoft.
This information is subject to change and we recommend that you check back quarterly for the addition or update of IP ranges.
Manual downloadβ
To retrieve them:
- Download the Azure IP Ranges and Service Tags
json
file. - Locate the
AzureFrontDoor.Frontend
entry - Get IP ranges from the
addressPrefixes
property.
You can also automate the extraction of these IP ranges, using one of these three options.
Automate via REST interfaceβ
curl https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Network/locations/{location}/serviceTags?api-version=2020-07-01
Automate via Powershellβ
Get-AzNetworkServiceTag -Location <String>
Automate via az cliβ
az network list-service-tags --location [--subscription]