Skip to content
Learn › Security and compliance overview: open the docs menu

Data security

This page is for IT administrators and security reviewers. It covers how Mammoth protects credentials and sessions, where your data is stored, and the network ports data sources must allow.

Credentials

Credentials you give Mammoth for connectors, such as database passwords and API secrets, are encrypted with RSA public-key encryption (PKCS1-OAEP). The private key is stored separately from the encrypted values.

Sessions

Browser sessions use HTTP-only, Secure cookies, so the session cookie is only sent over HTTPS and is not readable by JavaScript. See Sign-in and authentication for session lifetime and CSRF protection.

Data location

By default, customer data is stored in AWS Ireland (EU).

Network requirements

For Mammoth to connect to your data sources, the source must be reachable from Mammoth on its standard port:

TrafficPort
Mammoth services (HTTPS)443
PostgreSQL5432
MySQL3306
SQL Server1433

If your database listens on a non-default port, allow that port instead. IP allowlisting and VPC deployment are available on the Enterprise plan.

Report an issue · support@mammoth.io