Skip to content

Commit 8c32fc3

Browse files
committed
after 1. review V2
1 parent 9fbc272 commit 8c32fc3

File tree

1 file changed

+11
-11
lines changed
  • security/ciso-office/shared-assets/security-alarms

1 file changed

+11
-11
lines changed

security/ciso-office/shared-assets/security-alarms/README.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -135,34 +135,34 @@ After the creation of a topic, one or many subscriptions needs to be added, whic
135135
The topic creation is straightforward, as illustrated below. Within the OCI console, navigate to ```Developer Services -> Application Integration -> Notifications```
136136

137137
![create_topic_1](images/create_topic_1.png)
138-
Topic creation, step 1
138+
<small>Topic creation, step 1</small>
139139

140140
![create_topic_2](images/create_topic_2.png)
141-
Topic creation, step 2
141+
<small>Topic creation, step 2</small>
142142

143143
![create_topic_3](images/create_topic_3.png)
144-
Topic creation, step 3
144+
<small>Topic creation, step 3</small>
145145

146146
After the topic is created, a subscription is reasonable to create, the receiver of the alarm.
147147

148148
![create_topic_4](images/create_topic_4.png)
149-
Topic creation, step 4
149+
<small>Topic creation, step 4</small>
150150

151151
![create_topic_5](images/create_topic_5.png)
152-
Topic creation, step 5
152+
<small>Topic creation, step 5</small>
153153

154154
When the subscription is created, the subscriber will receive an email with a link to a confirmation.
155155
> N.B. If a different type of subscription is chosen, the receiving user will receive a confirmation through that notification channel, e.g., Slack.
156156
157157
Use the link in the notification to confirm the subscription.
158158

159159
![confirm](images/confirm.png)
160-
Confirmation link mail, step 5
160+
<small>Confirmation link mail</small>
161161

162162
The subscription will then change to Active.
163163

164164
![create_topic_6](images/create_topic_6.png)
165-
Final status after successful confirmation of the subscription
165+
<small>Final status after successful confirmation of the subscription</small>
166166

167167
# Define the alarm
168168

@@ -182,18 +182,18 @@ Ensure the fields are completed accurately:
182182
This will create an alarm that trigger if the last 5 minutes egress traffic exceed 1000000 bytes.
183183

184184
![alarm1a](images/alarm1a.png)
185-
Alarm definitions
185+
<small>Alarm definitions</small>
186186

187187
![alarm1](images/alarm1b.png)
188-
Create Alarm definition
188+
<small>Create Alarm definition</small>
189189

190190
![alarm2](images/alarm2.png)
191-
Create Alarm definition continued
191+
<small>Create Alarm definition continued</small>
192192

193193
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.
194194

195195
![alarm3](images/alarm3.png)
196-
Mail received when alarm is fired
196+
<small>Mail received when alarm is fired</small>
197197

198198
# Summary
199199

0 commit comments

Comments
 (0)