Security guide - Superblocks Docs

Data and network security

All traffic to and from the Superblocks is encrypted using TLS 1.2, 1.3
All data on the Superblocks platform is encrypted at rest using AES-256 encryption
Dedicated Cloud instances run on AWS infrastructure certified to SOC 2 and ISO 27001, in the primary region you choose. Dedicated Cloud supports AWS regions around the world.
Superblocks resources (Applications, APIs, Workflows, Integrations, Audit Logs) are stored in encrypted and network-protected databases with limited internal access

IP Addresses

For legacy multi-tenant Cloud customers, the following IP addresses must be added to an allowlist in order for Superblocks to connect to your configured integrations. On Dedicated Cloud and Managed BYOC, allowlist your data plane’s IP addresses instead.

NAT hostname	Current DNS	Last Recorded IPs
nat.superblocks.com	A Records	`100.24.157.155` `34.200.73.233` `34.209.17.50` `35.155.119.178` `35.86.18.137` `44.232.244.93` `54.211.180.182` `54.243.113.90`
nat.eu.superblocks.com	A Records	`13.50.50.66` `13.50.81.30` `13.51.231.18` `52.17.136.219` `54.220.65.107` `99.81.159.1`

While we do our best to never change these addresses, the best way to keep an updated allowlist is to use the current A records for the NAT hostname shown above, utilizing tools such as dig:

dig +short nat.superblocks.com | sort

or by using an API like dnsjson.com:

curl -s https://dnsjson.com/nat.superblocks.com/A.json | jq '.results.records|sort'

Superblocks deployment options

See details in the enterprise deployment overview.