openstack/openstack-manuals
Code Issues Proposed changes

Small minor edit to ch058_forensicsincident-response

Browse Source 
“a” changed to “an”

Change-Id: I750a085fef297f9f218bfd4bf093d2e64d76623e
This commit is contained in:
Shilla Saebi 2014-01-28 12:24:41 -05:00
parent 0227a30bca
commit 480bc906a2
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/security-guide/ch058_forensicsincident-response.xml
View File

@ -10,7 +10,7 @@
<section xml:id="ch058_forensicsincident-response-idp60511">
<title>Monitoring Use Cases</title>
<para>Monitoring events is more pro-active and provides real-time detection and response.  There are several tools to aid in monitoring.</para>
<para>In the case of a OpenStack cloud instance, we need to monitor the hardware, the OpenStack services, and the cloud resource usage. The last stems from wanting to be elastic, to scale to the dynamic needs of the users.</para>
<para>In the case of an OpenStack cloud instance, we need to monitor the hardware, the OpenStack services, and the cloud resource usage. The last stems from wanting to be elastic, to scale to the dynamic needs of the users.</para>
<para>Here are a few important use cases to consider when implementing log aggregation, analysis and monitoring. These use cases can be implemented and monitored through various commercial and open source tools, homegrown scripts, etc. These tools and scripts can generate events that can then be sent to the administrators through email or integrated dashboard. It is important to consider additional use cases that may apply to your specific network and what you may consider anomalous behavior.</para>
<itemizedlist><listitem>
<para>Detecting the absence of log generation is an event of high value. Such an event would indicate a service failure or even an intruder who has temporarily switched off logging or modified the log level to hide their tracks.</para>