Skip to main content
Connect your Firebird database so Myrmex can audit its hardening and compliance, check its operational health, explore its schema, and — with approval — run SQL for you. Myrmex reaches the database over the Firebird wire protocol through a Collector on your network. Operations run live and on demand through the Integration Specialist agent — Myrmex reads only what you ask for and keeps none of your data on the Myrmex side.

​
What Myrmex Can Do

Compliance audit

Run a Security Posture audit and map findings to ISO 27001, NIST CSF, and BACEN frameworks (Firebird has no CIS benchmark).

Health checks

Review active attachments, transaction gaps, and page and cache activity.

Explore tables

List tables so you can see what the database holds.

Describe structure

Inspect columns, types, indexes, and constraints for any table.

Sensitive-data scan

Scan tables and columns for personal or sensitive data that needs protection.

Run SQL

Execute read queries any time; write statements (DDL/DML) require your confirmation.

​
Before You Start

  • A Collector on a network that can reach the Firebird server on its TCP port (default 3050). See Collector mode.
  • The Collector host must have the native Firebird client library (libfbclient.so.2) installed — it is required for remote attach, and mandatory for servers with WireCrypt = Required.
  • An audit account for Myrmex (create it in Step 1).
  • The Database field is the server-side database path or alias (e.g. /var/lib/firebird/data/app.fdb, or an alias from databases.conf).

​
Step 1 — Create the Credential in Firebird

Connect as SYSDBA, or create a dedicated user granted the RDB$ADMIN role — needed to read SEC$USERS and the full MON$ monitoring tables the audit relies on.
Use the audit account for read-only work. Provide a write-capable user only if you want the agents to run write statements (DDL/DML) through Run SQL.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Firebird, then fill in:

​
Connect

Click Connect to validate the login. The database then appears under Environment → Integrations alongside your other integrations, and you can start asking the AI about it in the Workspace.

​
Notes

  • Read-only by default. Auditing, health, schema exploration, and sensitive-data scans only need the audit account. Provide a write-capable user only if you want confirmation-gated Run SQL writes.
  • Nothing is stored. Every operation runs in real time through the Collector; results return to your Workspace and no database data is retained on the Myrmex side.
  • Wire encryption. For servers with WireCrypt = Required, make sure the native libfbclient is present on the Collector so the connection can complete.