MySQL Forums
Forum List  »  Security

The DBMS must maintain a separate execution domain for each executing process.
Posted by: Jason Hurst
Date: March 07, 2019 02:38PM

I'm trying to get a government system hardened and during that process I have to answer certain criteria. One of them is the below:

---------------------------------------------------------
Rule Title: The DBMS must maintain a separate execution domain for each executing process.

Discussion: Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces.

Check Text: Review the DBMS architecture to find out if and how it protects the private resources of one process (such as working memory, temporary tables, uncommitted data and, especially, executable code) from unauthorized access or modification by another user or process.

If it is not capable of maintaining a separate execution domain for each executing process, this is a finding.

If the DBMS is capable of maintaining a separate execution domain for each executing process, but is configured not to do so, this is a finding.

Fix Text: Deploy a DBMS capable of maintaining a separate execution domain for each executing process.

If this is a configurable feature, configure the DBMS to implement it.

---------------------------------------------------------------------

Anyone have any information or documentation on this?

Options: ReplyQuote


Subject
Views
Written By
Posted
The DBMS must maintain a separate execution domain for each executing process.
1229
March 07, 2019 02:38PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.