You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pull request to update WMS 700 and LiveLabs #3733: Be a Data Security Superhero with Oracle Data Safe (#364)
* removal of images using caps
removal of images using caps
* Updates for Cloud World 2025
* cloud world additions
* typos
* Text updates based on Bettina's feedback
* Updates after run-through test
Copy file name to clipboardExpand all lines: data-safe/access-environment/access-environment-ocw-sandbox.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ In this lab, you will:
23
23
24
24
This lab assumes you have:
25
25
26
-
-Obtained an Oracle Cloud account and signed in to the Oracle Cloud Infrastructure Console at `https://cloud.oracle.com`
26
+
-Reserved your environment for the HOL with the instructions given by the speaker.
27
27
28
28
29
29
## Task 1: View your LiveLabs Sandbox reservation information and sign in
@@ -70,7 +70,7 @@ A database registered with Oracle Data Safe is referred to as a *target* databas
70
70
3. Under **List scope**, browse to and select your compartment. Your registered target database is listed on the right.
71
71
72
72
- A target database with an **Active** status means that it is currently registered with Oracle Data Safe.
73
-
- A target database with a **Deleted** status means that it is no longer registered with Oracle Data Safe. The listing is removed 45 days after the target database is deregistered.
73
+
- A target database with a **Deleted** status means that it is no longer registered with Oracle Data Safe.
74
74
75
75

76
76
@@ -87,7 +87,7 @@ A database registered with Oracle Data Safe is referred to as a *target* databas
87
87
88
88
- In Security center, you can access all the Oracle Data Safe features, including the dashboard, Security Assessment, User Assessment, Data Discovery, Data Masking, Activity Auditing, SQL Firewall, and Alerts.
89
89
- When you register a target database, Oracle Data Safe automatically creates a security assessment and user assessment for you. That's why the **Security assessment**, **User assessment**, **Feature usage**, and **Operations summary** charts in the dashboard already have data.
90
-
- During registration, Oracle Data Safe also discovers audit trails on your target database. That's why the **Audit trails** chart in the dashboard shows one audit trail with the status **In transition**for your Autonomous Database. Later you start this audit trail to collect audit data into Oracle Data Safe.
90
+
- During registration, Oracle Data Safe also discovers audit trails on your target database. That's why the **Audit trails** chart in the dashboard shows one audit trail for your Autonomous Database. Later you start this audit trail to collect audit data into Oracle Data Safe.
Copy file name to clipboardExpand all lines: data-safe/access-environment/access-environment-sandbox.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ A database registered with Oracle Data Safe is referred to as a *target* databas
63
63
3. Under **List scope**, browse to and select your compartment. Your registered target database is listed on the right.
64
64
65
65
- A target database with an **Active** status means that it is currently registered with Oracle Data Safe.
66
-
- A target database with a **Deleted** status means that it is no longer registered with Oracle Data Safe. The listing is removed 45 days after the target database is deregistered.
66
+
- A target database with a **Deleted** status means that it is no longer registered with Oracle Data Safe. Cloud target databases are delisted after one day. Billable target databases are delisted after 45 days.
67
67
68
68

69
69
@@ -78,7 +78,7 @@ A database registered with Oracle Data Safe is referred to as a *target* databas
78
78
79
79
- In Security center, you can access all the Oracle Data Safe features, including the dashboard, Security Assessment, User Assessment, Data Discovery, Data Masking, Activity Auditing, SQL Firewall, and Alerts.
80
80
- When you register a target database, Oracle Data Safe automatically creates a security assessment and user assessment for you. That's why the **Security assessment**, **User assessment**, **Feature usage**, and **Operations summary** charts in the dashboard already have data.
81
-
- During registration, Oracle Data Safe also discovers audit trails on your target database. That's why the **Audit trails** chart in the dashboard shows one audit trail with the status **In transition**for your Autonomous Database. Later you start this audit trail to collect audit data into Oracle Data Safe.
81
+
- During registration, Oracle Data Safe also discovers audit trails on your target database. That's why the **Audit trails** chart in the dashboard shows one audit trail for your Autonomous Database. Later you start this audit trail to collect audit data into Oracle Data Safe.
6. To view details about the security assessment itself, click the **Assessment information** tab.
62
-
63
-
- Details include assessment name, OCID, compartment to which the assessment was saved, target database name, target database version, assessment date and time, schedule, name of the baseline assessment (if one is set), and whether the assessment complies with the baseline (Yes, No, or No baseline set).
64
-
65
-

66
-
67
-
7. Scroll down and view the **Assessment details** section.
61
+
6. Scroll down and view the **Assessment details** section.
68
62
69
63
- This section shows you all the findings for each risk category.
70
64
- Risks are color-coded to help you easily identify categories that have high risk findings (red).
71
65
- The high risk findings listed under **Privileges and Roles** were introduced when you ran the SQL script to populate your target database with sample data.
8. Under **Filters by risks** on the left, notice that you can select the risk levels that you want displayed. Also notice on the left that you can filter by references.
69
+
7. Under **Filters by risks** on the left, notice that you can select the risk levels that you want displayed. Also notice on the left that you can filter by references.
9. On the right, expand categories and review the findings.
73
+
8. On the right, expand categories and review the findings.
80
74
81
75
- Each finding shows you the status (risk level), a summary of the finding, details about the finding, remarks to help you to mitigate the risk, and references - whether a finding is recommended by the Center for Internet Security (**CIS**), European Union's General Data Protection Regulation (**EU GDPR**), Security Technical Implementation Guide (**DISA STIG**), and/or **Oracle best practices**. These references make it easy for you to identify the recommended security controls.
82
76
- In the example below, the **Transparent Data Encryption** finding has three references: **Oracle Best Practices**, **DISA STIG**, and **GDPR**.
@@ -86,7 +80,7 @@ This lab assumes you have:
86
80
87
81
## Task 2: Set the latest assessment as the baseline assessment
88
82
89
-
A baseline assessment shows you data for all your target databases in a selected compartment at a given point in time. However, because we are only dealing with one target database in your compartment, the baseline assessment shows data for only one target database.
83
+
A baseline assessment shows you data for all your target databases in a selected compartment at a given point in time. However, because we are only dealing with one target database in your compartment, the baseline assessment shows data for only one target database. Let’s assume that we are okay with the current configuration and we want to set it as our baseline. New assessments are then automatically compared to the baseline.
90
84
91
85
1. At the top of the page, click **Set as baseline**.
92
86
@@ -103,7 +97,7 @@ A baseline assessment shows you data for all your target databases in a selected
103
97
104
98
## Task 3: Create a risk on the target database
105
99
106
-
In this task, you issue a `GRANT` command on your target database so that later, when you refresh the latest security assessment, you can compare assessments.
100
+
In this task, you manually create a new configuration risk on your database by issuing a `GRANT` command. Later, when you refresh the latest security assessment, you can compare assessments.
107
101
108
102
1. Access the SQL worksheet in Database Actions. If your session has expired, sign in again as the `ADMIN` user.
109
103
@@ -148,12 +142,13 @@ In this task, you issue a `GRANT` command on your target database so that later,
148
142
149
143
## Task 5: Compare your assessment with the baseline
150
144
151
-
1. With the latest security assessment displayed, under **Resources** on the left, click **Compare with baseline**. Oracle Data Safe automatically begins processing the comparison.
145
+
1. With the latest security assessment displayed, under **Resources** on the left, click **Compare with baseline**.
152
146
153
-
If you navigated away from the latest security assessment, you can return to it by doing the following: Click **Security assessment** in the breadcrumb. Click the **Target summary** tab. Click **View report** for your target database.
147
+
2. From the **Baseline** drop-down list, select your baseline. Oracle Data Safe automatically begins processing the comparison.
154
148
149
+
If you navigated away from the latest security assessment, you can return to it by doing the following: Click **Security assessment** in the breadcrumb. Click the **Target summary** tab. Click **View report** for your target database.
155
150
156
-
2. When the comparison operation is completed, scroll down the page to the **Comparison with baseline** section and review the information.
151
+
3. When the comparison operation is completed, scroll down the page to the **Comparison with baseline** section and review the information.
157
152
158
153
- Review the number of findings per risk category for each risk level. Categories include **User accounts**, **Privileges and roles**, **Authorization control**, **Data encryption**, **Fine-grained access control**, **Auditing**, and **Database configuration**.
159
154
- You can identify where the changes have occurred on your target database by viewing cells that contain the word **Modified**. The number represents the total count of new, remediated, and modified risks on the target database.
@@ -174,4 +169,4 @@ You may now **proceed to the next lab**.
174
169
## Acknowledgements
175
170
176
171
* **Author** - Jody Glover, Consulting User Assistance Developer, Database Development
177
-
* **Last Updated By/Date** - Jody Glover, June 25, 2025
172
+
* **Last Updated By/Date** - Jody Glover, August 1, 2025
Copy file name to clipboardExpand all lines: data-safe/assess-database-configurations/assess-database-configurations.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ You can defer or change the risk level of a risk finding. In this task, defer th
135
135
136
136
## Task 4: Set the latest assessment as the baseline assessment
137
137
138
-
A baseline assessment shows you data for all your target databases in a selected compartment at a given point in time. However, because we are only dealing with one target database in your compartment, the baseline assessment shows data for only one target database.
138
+
A baseline assessment shows you data for all your target databases in a selected compartment at a given point in time. However, because we are only dealing with one target database in your compartment, the baseline assessment shows data for only one target database. Let’s assume that we are okay with the current configuration and we want to set it as our baseline. New assessments are then automatically compared to the baseline.
139
139
140
140
1. At the top of the page, click **Set as baseline**.
141
141
@@ -152,7 +152,7 @@ A baseline assessment shows you data for all your target databases in a selected
152
152
153
153
## Task 5: Create a risk on the target database
154
154
155
-
In this task, you issue a `GRANT` command on your target database so that later, when you refresh the latest security assessment, you can compare assessments.
155
+
In this task, you manually create a new configuration risk on your database by issuing a `GRANT` command. Later, when you refresh the latest security assessment, you can compare assessments.
156
156
157
157
1. Access the SQL worksheet in Database Actions. If your session has expired, sign in again as the `ADMIN` user.
158
158
@@ -197,12 +197,13 @@ In this task, you issue a `GRANT` command on your target database so that later,
197
197
198
198
## Task 7: Compare your assessment with the baseline
199
199
200
-
1. With the latest security assessment displayed, under **Resources** on the left, click **Compare with baseline**. Oracle Data Safe automatically begins processing the comparison.
200
+
1. With the latest security assessment displayed, under **Resources** on the left, click **Compare with baseline**.
201
201
202
-
If you navigated away from the latest security assessment, you can return to it by doing the following: Click **Security assessment** in the breadcrumb. Click the **Target summary** tab. Click **View report** for your target database.
202
+
2. From the **Baseline** drop-down list, select your baseline. Oracle Data Safe automatically begins processing the comparison.
203
203
204
+
If you navigated away from the latest security assessment, you can return to it by doing the following: Click **Security assessment** in the breadcrumb. Click the **Target summary** tab. Click **View report** for your target database.
204
205
205
-
2. When the comparison operation is completed, scroll down the page to the **Comparison with baseline** section and review the information.
206
+
3. When the comparison operation is completed, scroll down the page to the **Comparison with baseline** section and review the information.
206
207
207
208
- Review the number of findings per risk category for each risk level. Categories include **User accounts**, **Privileges and roles**, **Authorization control**, **Data encryption**, **Fine-grained access control**, **Auditing**, and **Database configuration**.
208
209
- You can identify where the changes have occurred on your target database by viewing cells that contain the word **Modified**. The number represents the total count of new, remediated, and modified risks on the target database.
@@ -223,4 +224,4 @@ You may now **proceed to the next lab**.
223
224
## Acknowledgements
224
225
225
226
* **Author** - Jody Glover, Consulting User Assistance Developer, Database Development
226
-
* **Last Updated By/Date** - Jody Glover, May 5, 2025
227
+
* **Last Updated By/Date** - Jody Glover, August 1, 2025
Copy file name to clipboardExpand all lines: data-safe/assess-database-users/assess-database-users-ocw.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Introduction
4
4
5
-
User Assessment helps you assess the security of your database users and identify potential high risk users. By default, Oracle Data Safe automatically generates user assessments for your target databases and stores them in the Assessment History. You can analyze assessment data across all your target databases and for each target database. You can monitor security drift on your target databases by comparing the latest assessment to a baseline or to another assessment.
5
+
User Assessment helps you assess the security of your database users and identify potential high risk users. This allows you to review the potential risk to your data in case any of your user accounts get compromised or go rogue. By default, Oracle Data Safe automatically generates user assessments for your target databases and stores them in the Assessment History. You can analyze assessment data across all your target databases and for each target database. You can monitor user or entitlement changes on your target databases by comparing the latest assessment to a baseline or to another assessment.
6
6
7
7
In this lab, you explore User Assessment.
8
8
@@ -35,7 +35,7 @@ This lab assumes you have:
35
35
36
36
## Task 1: Analyze users in the latest user assessment
37
37
38
-
The latest user assessment is the one that was automatically generated by Oracle Data Safe when you registered your target database.
38
+
The latest user assessment is the one that was automatically generated by Oracle Data Safe when your target database was registered.
39
39
40
40
1. In the breadcrumb at the top of the page, click **Security center**. On the left, click **User assessment**.
41
41
@@ -82,11 +82,11 @@ The latest user assessment is the one that was automatically generated by Oracle
82
82
- User name
83
83
- User profile
84
84
- User type (for example, PRIVILEGED)
85
-
- Status (for example, OPEN)
86
-
- Potential risk (for example, CRITICAL) - Hover over the **i** to view what constitutes a critical risk user.
87
-
- Last login date and time
88
85
- Date and time when the user was created
86
+
- Potential risk (for example, CRITICAL) - Hover over the **i** to view what constitutes a critical risk user.
87
+
- Status (for example, OPEN)
89
88
- Date and time when the password was last changed
89
+
- Last login date and time
90
90
- Password expiry date
91
91
- Privileged roles (the Admin roles granted to the user)
92
92
- Roles: Expand **All roles** to view all the roles granted to the user
@@ -153,11 +153,8 @@ You can select a user assessment to compare with the latest user assessment. Wit
153
153
154
154
4. From the **Select assessment** drop-down list, select the initial assessment for your target database. As soon as you select it, the comparison operation is started.
155
155
156
-
5. Review the results.
157
-
158
-
- There is a new user added and a user deleted. The new user finding is identified as a potential **CRITICAL** risk.
159
-
- There are user grants modified by the `DS$ADMIN` user. This finding is also identified as a potential **CRITICAL** risk.
160
-
156
+
5. Review the results. A new user is added and a user is deleted. The new user finding is identified as a potential **CRITICAL** risk.
0 commit comments