Pluggable Database Lockdown Profiles for Per-Database Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In database consolidation, existing technologies fail to distinguish and manage individual pluggable databases within a container database, leading to security issues and inability to enforce per-pluggable-database restrictions, as the operating system and network remain unaware of the specific database involved in requests and communications.
Innovation Solution
Implementing pluggable database lockdown profiles within the container DBMS to restrict operations at the per-pluggable-database level, allowing for secure management of interactions with the operating system and network, and setting database options on a per-pluggable-database basis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If database consolidation is implemented with multiple pluggable databases in a single container database, then resource utilization and productivity are improved, but security control and management precision deteriorate because the operating system and network cannot distinguish individual pluggable databases
Solution Approach 1:
The patent segments security control into two layers: container database level (visible to OS/network) and pluggable database level (internal management). The lockdown profile mechanism divides security policies into container-level profiles that the OS can enforce and PDB-level restrictions that provide fine-grained control within each pluggable database, resolving the contradiction between consolidated resource management and individual security control.
Solution Approach 2:
The patent introduces lockdown profiles as an intermediary layer between the container database management system and individual pluggable databases. These profiles act as mediators that translate OS/network security requirements into PDB-specific restrictions, enabling security control at multiple levels without requiring OS or network awareness of individual PDBs.
2Ease of operation
If the container DBMS appears as a single monolithic entity to the operating system and network, then ease of operation is improved, but the ability to enforce per-pluggable-database restrictions deteriorates
Solution Approach 1:
The patent segments restriction enforcement into container-level and PDB-level mechanisms. Container-level lockdown profiles maintain the monolithic appearance to the OS for ease of operation, while PDB-level restrictions provide the adaptability to enforce specific policies on individual pluggable databases through the lockdown profile framework.
Solution Approach 2:
The patent applies local quality by allowing different lockdown profiles to be assigned to different pluggable databases within the same container. Each PDB can have customized security restrictions tailored to its specific requirements while the container maintains a unified interface to external systems.
3Ease of operation
If database options are set at the container database level, then ease of operation is improved through centralized management, but the ability to customize options for individual pluggable databases deteriorates
Solution Approach 1:
The patent segments database option management into container-level defaults and PDB-level overrides. Centralized management at the container level provides ease of operation for common configurations, while the lockdown profile mechanism enables per-PDB customization when specific databases require different options or restrictions.
Solution Approach 2:
The lockdown profile framework serves multiple functions: it provides container-level centralized management for default options, enables per-PDB customization when needed, and maintains a unified interface for both container and PDB administration. This multi-functionality resolves the contradiction between centralized management and individual customization.
Data Source
AI summary
Techniques are described herein for allowing a container DBMS to impose restrictions, on a per-pluggable-database basis, on operations based on the pluggable database to which the users that request the operations belong. In one embodiment, lockdown profiles can be created and mapped to pluggable databases. Lockdown profiles specify PDB-wide restrictions on operations. The restrictions may apply to all operations of a given type, may apply to specific features, may require use of specific parameter values, etc. All users that belong to a pluggable database are restricted by the restrictions specified in the lockdown profile to which their pluggable database is mapped, unless the lockdown profile has a user-specific exemption for them. Bitmaps and/or hash tables may be used to more quickly determine, at query runtime, whether a query violates any profile-specified restrictions. Execution of queries that violate any profile-specified restrictions is prevented.