{"id":518,"date":"2022-01-12T16:47:46","date_gmt":"2022-01-12T15:47:46","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/2022\/01\/12\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/"},"modified":"2023-06-20T10:06:51","modified_gmt":"2023-06-20T08:06:51","slug":"oracle-21c-security-diagnostics_control-and-enable-diagnostics","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/","title":{"rendered":"Oracle 21C Security : diagnostics_control and enable diagnostics"},"content":{"rendered":"

By Mouhamadou Diaw<\/strong><\/p>\n

Some debug-events and debug-actions are not safe and should be exposed to users with caution. In previous releases, privilege control for the usage of these diagnostics was not sufficient.<\/p>\n

With Oracle 21c, regular users can be blocked from using these diagnostics to better support separation of duty.<\/p>\n

Indeed with Oracle 21c, we have a new mechanism to control the debug-events and debug-actions through ALTER SESSION and\/or ALTER SYSTEM. This mechanism is implemented by two new features
\n-ENABLE DIAGNOSTICS system privilege
\n-DIAGNOSTICS_CONTROL initialization parameter<\/p>\n

Let\u2019s see how these features work
\nAs the DIAGNOSTICS_CONTROL is set to IGNORE, The default behavior is that every user can perform diagnostic tasks without error if he has ALTER SESSION PRIVILEGE<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n<\/td>\n
\n
\n
SQL> show parameter diagnostics_control<\/code><\/div>\n
<\/div>\n
NAME<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TYPE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VALUE<\/code><\/div>\n
------------------------------------ ----------- ------------------------------<\/code><\/div>\n
diagnostics_control\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 string\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code>IGNORE<\/code><\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Let\u2019s consider the user EDGE with the following privileges<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n<\/td>\n
\n
\n
SQL>\u00a0 <\/code>select<\/code> privilege <\/code>from<\/code> dba_sys_privs <\/code>where<\/code> GRANTEE=<\/code>'EDGE'<\/code>;<\/code><\/div>\n
<\/div>\n
PRIVILEGE<\/code><\/div>\n
----------------------------------------<\/code><\/div>\n
CREATE<\/code> TABLE<\/code><\/div>\n
ALTER<\/code> SESSION<\/code><\/div>\n
CREATE<\/code> SESSION<\/code><\/div>\n
<\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The user EDGE can execute following query<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n<\/td>\n
\n
\n
SQL> show con_name<\/code><\/div>\n
<\/div>\n
CON_NAME<\/code><\/div>\n
------------------------------<\/code><\/div>\n
PDB1<\/code><\/div>\n
SQL> show <\/code>user<\/code><\/div>\n
USER<\/code> is<\/code> \"EDGE\"<\/code><\/div>\n
SQL> <\/code>ALTER<\/code> SESSION <\/code>SET<\/code> EVENTS <\/code>'10046 trace name context forever, level 8'<\/code>;<\/code><\/div>\n
<\/div>\n
Session altered.<\/code><\/div>\n
<\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Let\u2019s now set the DIAGNOSTICS_CONTROL to WARNING<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n<\/td>\n
\n
\n
SQL> <\/code>alter<\/code> system <\/code>set<\/code> diagnostics_control=WARNING;<\/code><\/div>\n
<\/div>\n
System altered.<\/code><\/div>\n
<\/div>\n
SQL> show parameter diagnostics_control<\/code><\/div>\n
<\/div>\n
NAME<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TYPE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VALUE<\/code><\/div>\n
------------------------------------ ----------- ------------------------------<\/code><\/div>\n
diagnostics_control\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 string\u00a0\u00a0\u00a0\u00a0\u00a0 WARNING<\/code><\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And let\u2019s retry the SET EVENTS action with the user EDGE<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n<\/td>\n
\n
\n
SQL> show con_name<\/code><\/div>\n
<\/div>\n
CON_NAME<\/code><\/div>\n
------------------------------<\/code><\/div>\n
PDB1<\/code><\/div>\n
SQL> show <\/code>user<\/code><\/div>\n
USER<\/code> is<\/code> \"EDGE\"<\/code><\/div>\n
SQL><\/code><\/div>\n
<\/div>\n
<\/div>\n
SQL> <\/code>ALTER<\/code> SESSION <\/code>SET<\/code> EVENTS <\/code>'1357 trace name context forever, level 2'<\/code>;<\/code><\/div>\n
<\/div>\n
Session altered.<\/code><\/div>\n
<\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The action is executed but we have an entry in database alert log<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
2022-01-12T12:56:22.136454+01:00<\/code><\/div>\n
PDB1(3):<\/code>User<\/code> 'EDGE'<\/code> has <\/code>set<\/code> the following debug-event(s) <\/code>on<\/code> the event-<\/code>group<\/code> 'session'<\/code>:<\/code><\/div>\n
PDB1(3):<\/code>'1357 trace name context forever, level 2'<\/code><\/div>\n
PDB1(3):<\/code>To<\/code> disable such messages, refer <\/code>to<\/code> documentation about parameter <\/code>'diagnostics_control'<\/code>.<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now let\u2019s put the DIAGNOSTICS_CONTROL to ERROR<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n<\/td>\n
\n
\n
SQL> <\/code>alter<\/code> system <\/code>set<\/code> diagnostics_control=ERROR;<\/code><\/div>\n
<\/div>\n
System altered.<\/code><\/div>\n
<\/div>\n
SQL> show parameter diagnostics_control<\/code><\/div>\n
<\/div>\n
NAME<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TYPE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VALUE<\/code><\/div>\n
------------------------------------ ----------- ------------------------------<\/code><\/div>\n
diagnostics_control\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 string\u00a0\u00a0\u00a0\u00a0\u00a0 ERROR<\/code><\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And let\u2019s try again the SET EVENTS action with the user EDGE<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n<\/td>\n
\n
\n
SQL> show con_name<\/code><\/div>\n
<\/div>\n
CON_NAME<\/code><\/div>\n
------------------------------<\/code><\/div>\n
PDB1<\/code><\/div>\n
SQL> show <\/code>user<\/code><\/div>\n
USER<\/code> is<\/code> \"EDGE\"<\/code><\/div>\n
SQL> <\/code>ALTER<\/code> SESSION <\/code>SET<\/code> EVENTS <\/code>'1357 trace name context forever, level 2'<\/code>;<\/code><\/div>\n
ERROR:<\/code><\/div>\n
ORA-01031: insufficient <\/code>privileges<\/code><\/div>\n
ORA-49100: Failed <\/code>to<\/code> process event statement [1357 trace <\/code>name<\/code> context forever,<\/code><\/div>\n
level<\/code> 2]<\/code><\/div>\n
<\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

We can see that the statement is not executed and that we get an error.<\/p>\n

We can conclude than using the parameter DIAGNOSTICS_CONTROL, we can control which users can perform diag events. One can see following in Oracle documentation<\/a><\/p>\n

ERROR: If a user who does not have the SYSDBA or ENABLE DIAGNOSTICS privilege attempts to enable a diagnostic, then the attempt will fail and an ORA-01031: insufficient privileges error appears.
\nWARNING: A user who does not have the SYSDBA or ENABLE DIAGNOSTICS privilege will be able to enable a diagnostic, but a warning message is written to an alert log. The warning message is similar to the following:
\nIGNORE: The user can perform the diagnostic task without any error messages appearing. This setting is the default.<\/em><\/p>\n

But how if I want to set the parameter to ERROR and want to allow some non-DBA users to perform diag events? Just grant them the new system privilege ENABLE DIAGNOSTICS.
\nLet do a test.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n<\/td>\n
\n
\n
SQL>\u00a0 <\/code>select<\/code> privilege <\/code>from<\/code> dba_sys_privs <\/code>where<\/code> GRANTEE=<\/code>'EDGE'<\/code>;<\/code><\/div>\n
<\/div>\n
PRIVILEGE<\/code><\/div>\n
----------------------------------------<\/code><\/div>\n
ENABLE DIAGNOSTICS<\/code><\/div>\n
CREATE<\/code> TABLE<\/code><\/div>\n
ALTER<\/code> SESSION<\/code><\/div>\n
CREATE<\/code> SESSION<\/code><\/div>\n
<\/div>\n
SQL> show parameter diagnostics_control<\/code><\/div>\n
<\/div>\n
NAME<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TYPE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VALUE<\/code><\/div>\n
------------------------------------ ----------- ------------------------------<\/code><\/div>\n
diagnostics_control\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 string\u00a0\u00a0\u00a0\u00a0\u00a0 ERROR<\/code><\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And now let\u2019s do a diag event<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n<\/td>\n
\n
\n
SQL> show con_name<\/code><\/div>\n
<\/div>\n
CON_NAME<\/code><\/div>\n
------------------------------<\/code><\/div>\n
PDB1<\/code><\/div>\n
SQL> show <\/code>user<\/code><\/div>\n
USER<\/code> is<\/code> \"EDGE\"<\/code><\/div>\n
<\/div>\n
SQL> <\/code>ALTER<\/code> SESSION <\/code>SET<\/code> EVENTS <\/code>'1357 trace name context forever, level 2'<\/code>;<\/code><\/div>\n
<\/div>\n
Session altered.<\/code><\/div>\n
<\/div>\n
SQL><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

As now EDGE has the privilege ENABLE DIAGNOSTICS, he can perform diag events even if the DIAGNOSTICS_CONTROL is set to ERROR.<\/p>\n

Conclusion<\/h3>\n

This new feature can be very useful to limit the users who can perform diag actions. More information can be found in the Oracle documentation<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw Some debug-events and debug-actions are not safe and should be exposed to users with caution. In previous releases, privilege control for the usage of these diagnostics was not sufficient. With Oracle 21c, regular users can be blocked from using these diagnostics to better support separation of duty. Indeed with Oracle 21c, we […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198,59],"tags":[136,137,138,25],"type_dbi":[],"class_list":["post-518","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","category-oracle","tag-diagnostic","tag-oracle-21c","tag-oracle-21c-new-features","tag-security"],"acf":[],"yoast_head":"\nOracle 21C Security : diagnostics_control and enable diagnostics - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle 21C Security : diagnostics_control and enable diagnostics\" \/>\n<meta property=\"og:description\" content=\"By Mouhamadou Diaw Some debug-events and debug-actions are not safe and should be exposed to users with caution. In previous releases, privilege control for the usage of these diagnostics was not sufficient. With Oracle 21c, regular users can be blocked from using these diagnostics to better support separation of duty. Indeed with Oracle 21c, we […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-01-12T15:47:46+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-20T08:06:51+00:00\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Oracle 21C Security : diagnostics_control and enable diagnostics\",\"datePublished\":\"2022-01-12T15:47:46+00:00\",\"dateModified\":\"2023-06-20T08:06:51+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/\"},\"wordCount\":421,\"commentCount\":0,\"keywords\":[\"Diagnostic\",\"Oracle 21C\",\"Oracle 21c New features\",\"Security\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/\",\"name\":\"Oracle 21C Security : diagnostics_control and enable diagnostics - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2022-01-12T15:47:46+00:00\",\"dateModified\":\"2023-06-20T08:06:51+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle 21C Security : diagnostics_control and enable diagnostics\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Oracle 21C Security : diagnostics_control and enable diagnostics - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/","og_locale":"en_US","og_type":"article","og_title":"Oracle 21C Security : diagnostics_control and enable diagnostics","og_description":"By Mouhamadou Diaw Some debug-events and debug-actions are not safe and should be exposed to users with caution. In previous releases, privilege control for the usage of these diagnostics was not sufficient. With Oracle 21c, regular users can be blocked from using these diagnostics to better support separation of duty. Indeed with Oracle 21c, we […]","og_url":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/","og_site_name":"dbi Blog","article_published_time":"2022-01-12T15:47:46+00:00","article_modified_time":"2023-06-20T08:06:51+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Oracle 21C Security : diagnostics_control and enable diagnostics","datePublished":"2022-01-12T15:47:46+00:00","dateModified":"2023-06-20T08:06:51+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/"},"wordCount":421,"commentCount":0,"keywords":["Diagnostic","Oracle 21C","Oracle 21c New features","Security"],"articleSection":["Database Administration & Monitoring","Database management","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/","url":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/","name":"Oracle 21C Security : diagnostics_control and enable diagnostics - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-01-12T15:47:46+00:00","dateModified":"2023-06-20T08:06:51+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-21c-security-diagnostics_control-and-enable-diagnostics\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle 21C Security : diagnostics_control and enable diagnostics"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/518","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=518"}],"version-history":[{"count":3,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/518\/revisions"}],"predecessor-version":[{"id":26123,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/518\/revisions\/26123"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=518"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=518"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=518"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=518"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}