implementing-pam-for-database-access

Deploy privileged access management for database systems including Oracle, SQL Server, PostgreSQL, and MySQL. Covers session proxy configuration, credential vaulting, query auditing, dynamic credentia

Jump to install

Repository: xalgord/xalgorix
Last source activity: June 6, 2026 at 16:41
Detected SKILL.md language: English
Stars: 813
Forks: 146

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/xalgord/xalgorix --skill implementing-pam-for-database-access

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

exploiting-http-request-smuggling

Detecting and exploiting HTTP request smuggling vulnerabilities caused by Content-Length and Transfer-Encoding parsing discrepancies between front-end and back-end servers.

2026-07-20

exploiting-oauth-misconfiguration

Identifying and exploiting OAuth 2.0 and OpenID Connect misconfigurations including redirect URI manipulation, token leakage, and authorization code theft during security assessments.

2026-07-20

exploiting-subdomain-takeover-vulnerabilities

Identifying and exploiting dangling DNS records pointing to unclaimed cloud services, enabling subdomain takeover for phishing, cookie stealing, and authentication bypass during authorized penetration tests.

2026-06-19

View all from this repository

Implementing PAM for Database Access

Overview

When to Use

When deploying or configuring implementing pam for database access capabilities in your environment

When establishing security controls aligned to compliance requirements

When building or improving security architecture for this domain

When conducting security assessments that require this implementation

Common Misconfigurations & Verification

Database PAM is routinely bypassed because the direct network path to the DB stays open:

Proxy vaulting but direct port still reachable: credentials are vaulted and a session proxy exists, yet DBAs connect straight to 1521/1433/5432/3306 with their own logins, bypassing audit entirely. Verify the DB host firewall/listener only accepts connections from the PAM proxy IP, then attempt a direct connect from a workstation — it must be refused. Cross-check DB-native audit (pg_stat_activity / SQL Server sys.dm_exec_sessions / Oracle V$SESSION) and confirm every client_addr is the proxy.

Shared DBA accounts not vaulted / no per-user attribution: confirm sa, SYS, postgres, root@% are checked out through PAM and that proxy logs map each session to a named human, not a shared login.

No automatic rotation after checkout: if the vaulted password is not rotated on check-in, a DBA who memorized it retains direct access. Confirm one-time-use / rotate-on-checkin is enabled and test that the previous password fails.

Query auditing captures connect but not statements: verify the proxy logs actual SQL (not just session start/stop) and that privileged statements (GRANT, DROP, bulk SELECT on PII) trigger alerts.

Least-privilege roles bypassed via direct superuser grant: confirm vaulted accounts use scoped roles, not blanket DBA/sysadmin/SUPERUSER.

Dynamic credential users left orphaned: if using dynamic DB creds, confirm expired users are dropped (no accumulating v-* roles) and SIEM receives all PAM session events.