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
Copy file name to clipboardExpand all lines: security/ciso-office/shared-assets/security-alarms/README.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,34 +135,34 @@ After the creation of a topic, one or many subscriptions needs to be added, whic
135
135
The topic creation is straightforward, as illustrated below. Within the OCI console, navigate to ```Developer Services -> Application Integration -> Notifications```
136
136
137
137

138
-
Topic creation, step 1
138
+
<small>Topic creation, step 1</small>
139
139
140
140

141
-
Topic creation, step 2
141
+
<small>Topic creation, step 2</small>
142
142
143
143

144
-
Topic creation, step 3
144
+
<small>Topic creation, step 3</small>
145
145
146
146
After the topic is created, a subscription is reasonable to create, the receiver of the alarm.
147
147
148
148

149
-
Topic creation, step 4
149
+
<small>Topic creation, step 4</small>
150
150
151
151

152
-
Topic creation, step 5
152
+
<small>Topic creation, step 5</small>
153
153
154
154
When the subscription is created, the subscriber will receive an email with a link to a confirmation.
155
155
> N.B. If a different type of subscription is chosen, the receiving user will receive a confirmation through that notification channel, e.g., Slack.
156
156
157
157
Use the link in the notification to confirm the subscription.
158
158
159
159

160
-
Confirmation link mail, step 5
160
+
<small>Confirmation link mail</small>
161
161
162
162
The subscription will then change to Active.
163
163
164
164

165
-
Final status after successful confirmation of the subscription
165
+
<small>Final status after successful confirmation of the subscription</small>
166
166
167
167
# Define the alarm
168
168
@@ -182,18 +182,18 @@ Ensure the fields are completed accurately:
182
182
This will create an alarm that trigger if the last 5 minutes egress traffic exceed 1000000 bytes.
183
183
184
184

185
-
Alarm definitions
185
+
<small>Alarm definitions</small>
186
186
187
187

188
-
Create Alarm definition
188
+
<small>Create Alarm definition</small>
189
189
190
190

191
-
Create Alarm definition continued
191
+
<small>Create Alarm definition continued</small>
192
192
193
193
Here is an example of a mail alarm received when the egress volume exceeds 1000000 bytes within 5 min. This might indicate a potential data loss.
0 commit comments