Security
What LAB256 touches, records and sends
A tool that asks for a database password has to answer this before the trial. Here it is, with no hunting through the FAQ.
- Agentless architecture
- LAB256 is a desktop application that opens JDBC connections to the database. Nothing is installed on the database server. Close the application and the connection is gone.
- Minimum privileges
- A dedicated, read-only user. Oracle: SELECT on the V$ and DBA_* views. PostgreSQL: access to the pg_stat views and the pg_stat_statements extension. DBA actions such as ending a session only work if that user holds the privilege; LAB256 asks for nothing beyond what the screen in use requires.
- What is recorded
- Performance metrics per connection: vitals, top SQL and sessions by the minute, capacity, memory, and an hourly health check. Raw for a day, by the minute for a month, by the hour for up to a year; all three periods are configurable. Settings shows what each connection keeps, with a switch and a delete for each.
- SQL text off by default
- The history keeps identifiers (SQL_ID) and metrics. SQL text is only recorded if you switch that option on, per connection.
- Encryption at rest
- The history file is encrypted at rest. Connection credentials are sealed by an application password with no recovery path: without the password, the secrets do not open.
- What leaves your network
- Your database data never leaves your machine. The application talks to our server to validate the licence and to send usage data and error reports, which you can turn off in Settings. What is sent, field by field, is in the Privacy Policy.
- Installer integrity
- Every published installer shows its SHA-256 next to the download button. Check the hash before installing in a controlled environment.
- Offline activation
- For isolated networks, the licence is activated by QR code: the application generates the code, you validate it on any device with internet access and paste the result back. The monitored machine never has to leave the network.