Privileged access management (PAM) controls how people and services use accounts with elevated permissions. For Oracle Database, plan both who can obtain administrative access and what that account can do after connecting. Oracle Database Vault adds database-enforced restrictions on access to protected data and on database commands; it complements existing privileges and roles.
This guide covers access-control design for self-managed Oracle Database 26ai Enterprise Edition, with Oracle Database Vault as the database enforcement component. It is an operating-system-neutral planning guide, not an installation or policy-enablement procedure. Deployment support must be checked for your exact database release, operating system, and identity or credential-management product.
Separate identity, credentials, and database permissions
Start with three questions: Who is requesting access? How does that person or service authenticate? Which operations should the database permit? Record a separate answer for each question instead of treating a successful login as authorization for every administrative task.
Identity and access management covers the lifecycle of identities and entitlements. Identity governance includes provisioning, deprovisioning, and reviews of high-risk access. Oracle describes these responsibilities in its identity and access management overview. For a PAM design, identify the privileged subset of those accounts and the additional approval and accountability requirements you want to apply.
PAM credential stores centrally manage database or host account passwords and control who can use those accounts. Enterprise Manager Cloud Control 24.1 describes retrieving credentials from an external PAM store for jobs and other workflows in its PAM integration introduction. That integration uses Named Credentials; it is separate from Database Vault’s database policy enforcement.
Decide who may retrieve a shared administrative credential, how access is approved, and how use is attributed to an individual. Treat password rotation, session recording, and temporary access as evaluation requirements for your chosen product, not features supplied by Database Vault. Check the provider’s exact version and integration requirements before choosing it.
Inside the database, Database Vault evaluates its controls after the existing system or object privilege checks. It augments grants and roles rather than replacing them. For example, a broad system privilege can authorize access that a Database Vault realm subsequently restricts. See About Oracle Database Vault, section 1.1.1.
Inventory privileged access before choosing controls
Before evaluating software or changing policies, assemble an inventory with the DBA team, application owners, and security administrators. Include the database edition and release, CDB and PDB layout, authentication methods, and the administrative tasks that must remain available.
- List human administrators, application owners, service accounts, and shared administrative accounts. Assign an accountable owner to each.
- Record the privileges and roles used for routine work, the sensitive objects each account can reach, and the approved connection paths.
- Separate routine maintenance from access to application data. Identify cases where the same person needs different accounts for different responsibilities.
- Document emergency access, approval ownership, access-review intervals, and the evidence needed to trace an administrative action.
- Identify automated jobs and application dependencies that could be affected by a permission or credential change.
The expected result is an access matrix: account, owner, task, container, permitted data, approval rule, and evidence source. Keep credentials out of this matrix. Use it to specify policy requirements and test cases.
Match database controls to the task
Database Vault provides realms, command rules, rule sets, and factors. A realm protects a defined set of schemas, objects, or roles. A command rule controls whether a database statement may run. Rule sets evaluate conditions, and factors supply attributes that can be used in those conditions. These components are described in Database Vault access control components, section 1.3.1.
Use the access matrix to distinguish the controls you need:
- For an administrator who maintains infrastructure but should not read application data, evaluate realm protection around the relevant application objects.
- For a permitted operation that should run only under defined conditions, evaluate a command rule and its rule set.
- For changes to security policies or user accounts, assign the appropriate security or account-management responsibility rather than relying on one shared administrative identity.
Oracle documents DV_OWNER and DV_ADMIN for creating and managing Database Vault policies, and DV_ACCTMGR for managing user accounts. Its privilege prerequisites, section 1.2, also require backup accounts during registration and recommend maintaining them. Plan trusted ownership and continuity before enabling controls.
Realm mode affects the access boundary. With regular realms, object owners and direct object grantees can query data or perform DML without realm authorization; DDL still requires authorization. Mandatory realms also require authorization for owners and object grantees. Oracle explains the distinction in About Realms, section 4.1.1.
Include relevant views and grants to PUBLIC in the evaluation. Protecting a table does not automatically protect a view of that table. Public object grants can allow data access through a regular realm; the documented mandatory-realm behavior differs. Also keep policy administrators trusted: users with DV_OWNER or DV_ADMIN can add themselves to realm authorization. See How Realms Work, section 4.9, and realm authorization, section 4.7.
Include CDB and PDB boundaries
In a multitenant deployment, configure and enable Database Vault in the container database before configuring it in individual pluggable databases. Database Vault can be enabled in selected PDBs. Operations control offers a separate CDB-level control over common privileged users’ access to non-Oracle-maintained schema data in PDBs, without requiring Database Vault to be enabled in those PDBs.
Oracle describes these combinations in Database Vault in a multitenant environment, section 1.8. Record whether a requirement concerns a common container administrator, a local PDB administrator, or an application account. Check the intended policy in every affected container.
Strict mode is an availability consideration: PDBs with Database Vault disabled operate in restricted mode when the CDB uses strict mode. Read/write opening requires configuring and enabling Database Vault in the PDB or disabling strict mode in the CDB. Review regular and strict mode, section 1.8.5, before selecting that configuration.
Validate allowed work and denied access separately
Use an isolated non-production environment and synthetic data to evaluate the design. The following is a test plan, not a claim of completed testing:
- Establish the expected outcome for each account and task in the access matrix.
- Confirm that an approved administrator can perform the required maintenance work through the intended connection path.
- Check that an account without the relevant authorization cannot read the protected test data. Test direct grants, grants to
PUBLIC, relevant views, and object-owner access separately against the documented behavior of the selected realm mode. - Repeat the checks for common users and local PDB users in the affected containers.
- Review the evidence for policy changes and denied operations. Confirm who owns investigation and how the records will be retained.
- Evaluate emergency access and recovery arrangements before approving production rollout.
Database Vault configuration views provide status and component information. Policy changes, violation attempts, and configuration changes can be monitored through the unified audit trail. Oracle describes the available monitoring paths in Reporting and Monitoring Tools, section 1.3.4. Verify the records relevant to your controls; do not treat a running administration interface as proof that access restrictions work.
Simulation mode logs realm violations without blocking the operation. Use it to study workload effects, but validate denied access with enforcement enabled in the test environment. Oracle describes this boundary in Guidelines for Designing Realms, section 4.14.
If permitted work is blocked, compare the account, container, realm authorization, command rule, and rule-set conditions with the intended access matrix. If protected data remains accessible, check the actual protected objects, realm mode, and account authorization. Resolve the policy mismatch in the test environment before expanding access in production.
Enabling access controls can interrupt administrative or application work. Before implementation, preserve the current policy configuration, confirm a database backup and recovery plan, maintain the documented backup administrator accounts, and select the supported configuration and recovery procedures for your release. This guide supplies no commands to enable, disable, or bypass a policy.
Check licensing and adjacent security responsibilities
For self-managed Enterprise Edition and Enterprise Edition on Engineered Systems, Database Vault is an extra-cost option. The licensing guide states that enabling it in the CDB root requires a Database Vault license; the license covers the entire CDB, not individual PDBs. Merely installing or configuring it in the root does not trigger that stated enablement requirement. Licensing metrics must match the Enterprise Edition metrics. See the Oracle Database Vault entry in Oracle Database 26ai Licensing Information. Review your contract and deployment rights before enablement.
PAM also has organizational dependencies. Our historical discussion of identity-management challenges covers hosted and mobile identity administration, a broader subject than privileged database access. Our historical database firewall overview discusses SQL traffic controls, a separate enforcement layer. Neither article is a current PAM deployment guide.
Approve the design when you can identify the owner of each privileged account, explain its allowed tasks, demonstrate the required access boundaries, and retrieve the evidence needed for review. Keep the credential-management system, identity lifecycle, and database policy responsibilities explicit in the operating plan.
