#023Technical4 min

Prepare PostgreSQL or MySQL for an authorized audit

Set up dedicated read-only access, connect the right database, and recognize limits caused by unavailable checks.

Hackaiz team · updated 21/11/2026

Illustration: a person sets up an account on a laptop.
Illustration: a person sets up an account on a laptop. Illustrative photo, not a screenshot.

01Prepare a catalog audit, not a data export

The “Live Postgres and MySQL” panel connects to a database to inspect accounts, privileges and server settings. Hackaiz describes this as one read-only connection: it does not read business table contents or write changes. Prepare access for that purpose rather than exporting customer records or sending a database dump. PostgreSQL and “MySQL / MariaDB” have separate engine choices in the interface.

Before entering credentials, confirm that you own the database and have the right to permit this verification. Identify the host, port, database name and intended engine with the database administrator. A production database and a staging copy can have different roles and settings even when their schema looks the same. Record which environment you intend to assess so that a finding about a permissive account is not attributed to the wrong system.

02Create a dedicated account with limited rights

Ask your database administrator to create a dedicated read-only account and decide which system metadata it may inspect. Do not use the application’s normal write-capable login or an all-powerful administrator account just to make a check succeed. Account and privilege catalogs can themselves have restricted visibility; a failed check should be investigated as a permission or execution limit, not solved by granting every privilege without review.

The database must be reachable through the supported connection path. Hackaiz rejects private or reserved network targets, and the interface explains when a private database cannot be reached. Do not expose an internal production server broadly to make the audit work. Have the administrator review the provider’s network controls and encrypted-connection requirements first. If safe connectivity cannot be established, stop rather than weakening the database perimeter for convenience.

03Enter the connection address in the protected form

From the database selection flow in Connect, open “Choose a database”. In the live database panel, select “PostgreSQL” or “MySQL / MariaDB”. The form expects a connection URL containing the account, password, host, port and database, for example postgres://audit_reader:REDACTED@db.example.com:5432/app or mysql://audit_reader:REDACTED@db.example.com:3306/app. Replace every placeholder with your approved values; these examples are not working credentials.

The address field is masked. The interface states that the address is encrypted and never shown back to you. Tick “I own this database and allow Hackaiz to check it.”, then choose “Save”. Keep the real connection string out of support messages, screenshots and shared notes. A refused-credentials message calls for checking the account details with the administrator; a no-response message instead calls for investigating connectivity.

  1. 1Choose the correct engine and enter the dedicated account’s connection URL.
  2. 2Read and tick the ownership authorization, then save the database.
  3. 3In selection mode, choose the saved database for the analysis; in the standalone panel, “Check my database” starts its verification.

04Read incomplete coverage and remove access deliberately

The PostgreSQL checks include privileges granted to everyone, powerful login roles and tables without row protection that other roles can read. Row protection means rules that restrict which records a role may access. MySQL checks include anonymous accounts, accounts usable from any host and server-wide privileges assigned to an application account. These examples concern structure and configuration, not an inspection of individual customer records.

Read both the reported issues and the number of checks not run. A check that could not inspect a protected catalog is not evidence that the corresponding risk is absent. Analyses use credits; in the combined analysis, unticked checks are neither executed nor billed. Database findings do not trigger automatic changes to accounts or permissions. Review any remedial SQL with your administrator and test it before applying it yourself.

Use “Change database” to replace the saved connection or “Remove access” to remove it from Hackaiz. Revoke the dedicated account at the database as well when it is no longer needed, following your own access-management process. Removing a stored connection should not be confused with deleting the actual database account. Website checks, if also needed, require separate domain ownership proof and authorization; database credentials do not authorize a website audit.

Frequently asked questions

Was this article helpful?

Related articles