Guide to Secure AI agent Idira SIA PostgreSQL setup

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Secure Infrastructure Access
6 min read
L0 Member
No ratings

How the SIA Strong Account Enables Secure Access to PostgreSQL

 

Idira Secure Infrastructure Access (SIA) provides Zero Standing Privileges (ZSP) for PostgreSQL by dynamically creating and deleting temporary (ephemeral) database users for each session. This eliminates persistent privileged accounts and ensures every connection has exactly the least privilege required.

The mechanism relies on two closely linked components:

 

  1. The PostgreSQL Strong Account Role (Example: sia_strong) This is a privileged  role you would create directly inside PostgreSQL. It is not a user that people log in with — it is a backend credential that SIA uses automatically to perform administrative actions.

Key privileges (minimum required):

    • LOGIN — allows SIA to connect to PostgreSQL as this role.
    • CREATEROLE — allows SIA to create new roles, grant permissions to them, and drop them.
    • CONNECT on a system database (typically postgres) — allows SIA to execute the provisioning commands.

This role never needs table-level access (SELECT, INSERT, etc.). It only manages roles (users). No end-user ever authenticates as sia_strong.

 

  1. The Strong Account in Idira SIA This is a configuration object you create in the SIA portal (under Strong accounts → Databases). It is not a new user in PostgreSQL — it is simply a secure reference to the existing PostgreSQL role.

Example SIA Strong account fields:

    • Platform: PostgreSQL
    • Secret name : SIA-postgDB_Target01_strong [user defined]
    • Username: sia_strong [account created in PostgreSQL]
    • Password: [the exact password from the PostgreSQL role]
    • Database (optional): postgres
    • Port (optional)
    • DNS (optional)

How They Work Together – The Full Session Flow

 

  1. User requests access You (or another authorized user) click Connect to the PostgreSQL target in the Secure Access portal.
  2. SIA authenticates & authorizes SIA verifies your identity (ISPSS credentials, MFA) and checks the active recurring access policy for allowed privileges (e.g., read-only via weather_reader role).
  3. SIA retrieves the Strong account SIA looks up the configured Strong account entry for this target → gets the username sia_strong and password.
  4. SIA logs in to PostgreSQL as the strong account role Using the provided credentials, SIA connects to PostgreSQL as sia_strong (using the CONNECT privilege on postgres).
  5. Provisioning – Ephemeral user creation SIA uses the CREATEROLE privilege to:
    • Create a temporary role: CREATE ROLE temp_ephemeral_abc123 WITH LOGIN PASSWORD 'temp-pass';
    • Grant the policy-defined roles: GRANT weather_reader TO temp_ephemeral_abc123;
    • (Optional additional grants based on policy)
  6. Session proxy SIA proxies your connection. You now appear to PostgreSQL as the ephemeral user temp_ephemeral_abc123, with only the privileges granted (read-only in this case).
  7. Session cleanup When you disconnect (or session times out):
    • SIA reconnects as sia_strong
    • Runs DROP ROLE temp_ephemeral_abc123;
    • No trace of the temporary user remains

This entire process is fully audited in SIA session diagnostics.

Steps

Step 1: Create the Strong Account Role in PostgreSQL

 

Why this step is needed SIA needs a privileged PostgreSQL role to act as the "provisioner." This role logs in to PostgreSQL and uses its CREATEROLE privilege to create, configure, and delete temporary (ephemeral) users for each session. No end-user or AI agent ever logs in as this role — it exists only for SIA automation.

 

  1. Open pgAdmin (or psql) and connect as a superuser (e.g., postgres or your admin user) to any database (preferably postgres or your main DB).
  2. Run the following script from the Query tool:

SQL

CREATE ROLE sia_strong WITH LOGIN PASSWORD 'ReplaceWithVeryStrongPasswordHere!2026';

ALTER ROLE sia_strong CREATEROLE;

GRANT CONNECT ON DATABASE postgres TO sia_strong;

 

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJZni.png

  • Replace the password with a strong, unique value.
  • If your main/system database is not named postgres (e.g., postsgres), change the last line accordingly.
  1. Verify the role was created correctly:

SQL

SELECT

    rolname,

    rolcanlogin,

    rolcreaterole,

    rolsuper

FROM pg_roles

WHERE rolname = 'sia_strong';

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJgdu.png

Expected output:

  • rolcanlogin = true  → can log in
  • rolcreaterole = true → can create/drop roles (required for SIA ephemeral user provisioning)
  • rolsuper = false → not superuser (good – least privilege)

 

Step 2: Add PostgreSQL Resource via Resource Management in SIA

 

Why this step is needed SIA must know about your PostgreSQL server/instance so it can apply policies, test connectivity, and route sessions through your connectors. Without onboarding, the target won't appear in policy wizards or Secure Access.

 

  1. In the Idira portal, go to Resource management → Add resource → Database.
  2. In the Onboard a database instance wizard:
    • Database: PostgreSQL
    • Location: On premises
    • Service: PostgreSQL
    • Authentication method: Local user
  3. Database details:
    • Database name: postsgres (or your actual DB name — optional)
    • Port: 5432
    • Read and write address: target01.cyberarklab.local (or IP 192.168.142.132)
  4. Strong account details:
    • Strong account name: SIA-postgDB_Target01_strong (select from dropdown)
  5. TLS Certificate: Leave disabled (until first tests are successful)
  6. Click Onboard.

Expected result

 

  • Success message
  • The target appears in Resource management → Databases with healthy status

 

eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hK7iv.jpg

eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hK7fh.jpg

eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJeXI.jpg

eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJv9u.jpg

Step 3: Add a Strong Account for PostgreSQL in SIA

 

Why this step is needed: This tells SIA which PostgreSQL credentials to use when provisioning ephemeral users for this target. It links the PostgreSQL role (sia_strong) to SIA securely.

 

  1. Go to Strong accounts → Databases tab → Add a strong account
  2. Choose Stored in the SIA Service
  3. Fill in:
    • Platform: PostgreSQL
    • Secret name SIA-postgDB_Target01_strong
    • Username: sia_strong
    • Password: [the password from step 1]
    • Address (optional): target01.cyberarklab.local
    • Database (optional): postsgres
    • Port (optional): 5432
  4. Click Create

Expected result

  • Strong account appears in the list
  • Status is normal (no errors)

eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hK7hJ.jpg

eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJnFa.jpg

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJTGs.png

Step 4: Add an Access Policy in SIA

 

Why this step is needed: The policy defines who can access the database and what privileges the ephemeral users receive (e.g., read-only). Enabling ZSP triggers the use of your strong account to create/delete temporary users.

 

  1. Go to Recurring access policies → Create policy
  2. Step 1: Details
    • Policy name: e.g., "PostgreSQL DB Read-Only"
    • Next
  3. Step 2: Assets
    • Click +Add next to PostgreSQL
    • Select your onboarded target (target01.cyberarklab.local / postsgres)
    • Apply → Next
  4. Step 3: Access rules
    • Rule name: e.g., "Read-Only Ephemeral"
    • Members/Identities: Add yourself (search your name/email)
    • Privileges/Roles: Enter  (the read-only role you created)
    • Zero Standing Privileges: Enable (toggle ON)
    • Session length: 2 hours max (default is fine)
    • Idle timeout: 10 minutes
    • Create rule → Activate policy

Expected result

  • Policy status: Active
  • Target now visible in Secure Access for connection testing

 

Secure AI Agent Setup (PostgreSQL) in Claude Desktop

 

Step 1 Resister AI Agent

Agent Name:

Agent Type:

Save and continue to connect

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJt3G.png

Step 2 Copy the URL and credentials into your AI agent’s configuration

 

This setup will use the paid version of Claude Desktop. Only the paid version has access to MCP.

 

Step 3 Claude Settings>Connectors>Add custom connectors

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hK3c6.png

Copy the information from the Idira Connect AI agent’s window to Claude’s Add custom connector

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hK7e5.png

Figure 1 Idira Connect AI agent

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJ9Rq.png ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hK7m9.png

Figure 2 Claude's Add customer connector

 

 

Click Connect on the custom connector

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hK7kX.png

Redirection to CyberArk’s Identity should come up. If it does not connect after a bit you might get the following error. Just try again in a min or so. If you have already authenticated with Idira Identity, it may take a bit for Claude to get the tools it needs from CyberArk’s MCP.

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJDH0.png

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJfZm.png

 

Once it makes the connection Claude will show the following message and the custom connector will now say Configure.

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hK2Pu.png

Click on configure will show the configuration along with the tools it can use

ka3Vy00000BaxXtIAJ__eid=ka3Vy00000BaxXt&feoid=00N2J000009R3kv&refid=0EMVy00000hJdL5.png

 

You should now be able to open a new Claude chat window and ask it questions related to the database.

 

 

Rate this article:
  • 1118 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:46 AM
Updated by: