OLTP

Online Transaction Processing (OLTP) databases — SQL Server, MySQL, Oracle, PostgreSQL, MongoDB, and Apache Cassandra — lack the native policy framework that ALTR uses to enforce controls directly on Snowflake or Databricks. ALTR integrates with OLTP databases through 2 independent customer-deployed components instead: a sidecar that sits inline in the query path for access control and monitoring, and agents that connect to or poll a database on their own schedule.

In this section

• Repositories — Register a database and its users as a repository in ALTR’s control plane, whether it’s accessed through the sidecar or an agent.
• Sidecar Integration — Deploy the ALTR sidecar to apply real-time access control and capture query activity on a repository.
• Agent Integration — Deploy the classification agent or Security Intelligence Scout to scan or monitor a repository independently of the sidecar.

Onboarding Sequence

Setting up OLTP integration follows one of two paths, depending on which components you deploy. Both paths share the repository-registration step.

Sidecar path (access control and activity monitoring through the sidecar):

1. Register a repository for the database.
2. Register a sidecar to obtain the identifiers its container needs, then install the sidecar container using those identifiers.
3. Register a listener port and bind it to the repository.
4. Register repository users for impersonation, if data consumers will connect that way.
5. Connect to the repository and create an Impersonation Policy or Access Management Policy to enforce.

Agent path (classification or activity monitoring through an agent, independently of the sidecar):

1. Register a repository for the database, if it isn’t already registered.
2. Register a repository service user for the agent to retrieve at runtime — see Repository Users and Repository Service Users.
3. Deploy Data Classification with Agents or Database Activity Monitoring with Agents.