4.5.5 Guidelines for disk space requirements for backing up operation logs
The following table shows the guidelines for disk space requirements for backing up operation logs for one year (365 days).
|
Number of devices |
Required disk space (GB) |
||
|---|---|---|---|
|
All operations are logged |
Only operations closely related to information leakage are logged |
Only Web access operations are logged# |
|
|
100 |
29 |
1.3 |
14 |
|
300 |
89 |
3.8 |
42 |
|
500 |
147 |
6.2 |
70 |
|
700 |
206 |
8.7 |
98 |
|
1,000 |
293 |
13.0 |
139 |
|
3,000 |
645 |
39.0 |
408 |
#: You can reduce the amount of acquired Web access operation logs by setting a Web server address from which no operation logs need to be acquired. However, this option is not considered here.
If all operations are to be logged, the values indicated in the All operations are logged column applies as they are. Even if you change the setting of operations considered to be suspicious when all operations are to be logged, the amount of acquired operation logs does not change. This is because only the logging condition for suspicious operations is changed for all operation logs.
For example, if 300 devices are managed and all operations except for Web access operations are to be logged, you can estimate the required disk space as follows:
89 GB - 42 GB = 47 GB
Related Topics: