Red Hat NETSCAPE MANAGEMENT SYSTEM 6.2 - AGENT GUIDE Guida di Installazione Pagina 19

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 28
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 18
One yearly audit runs on 150,000 systems. The table does not include this value,
but it is equivalent to three yearly audits on 50,000 systems.
Two quarterly audits run on 10,000 systems.
Calculate the approximate database size:
1 Look up the corresponding values in the table under Requirements table for
database sizing, and note these results:
Database size (GB)=...running on number of systemsAudit frequency...
2842,000 systems2 weekly audits
4105,000 systems5 monthly audits
20450,000 systems (3 × 68 = 204)3 yearly audits
10910,000 systems2 quarterly audits
2 Calculate the total amount of space needed:
284 + 410 + 204 + 109 = 1,007 GB
Database storage requirements for File Integrity Monitoring
File Integrity Monitoring (FIM) allows you to designate a set of files to monitor for
changes. McAfee Policy Auditor software monitors the MD5 and SHA-1 hashes of a
file as well as the file attributes and permissions information. When a file changes,
the McAfee Policy Auditor agent plug-in notes the change and sends an event back
to the server.
The number of FIM events depends upon the number of files monitored and the
frequency of changes to monitored files. The number of events is difficult to predict,
but the impact to database storage is minimal.
Each FIM event adds approximately 3 kB to the database. If your organization
generates one million events per month, the annual database growth is:
3 kB/event × 1,000,000 events/month × 12 months/year × 0.000001 GB/kB = 36
GB/year
Database storage requirements for file versioning
The File Integrity Monitoring feature of McAfee Policy Auditor software allows you
to store up to six versions, including the file baseline, of text files from managed
systems. The software does not support versioning for non-text files.
Version database sizing chart
This chart helps you calculate the database storage requirements for versioned
files. The Monitored File Size column is the size of the file in megabytes for which
you are storing version text. The Versions row is the number of file versions that
you are storing.
65432Versions
Database requirement per 1,000 systems (GB)
Monitored File Size (MB)
0.2870.2290.1720.1150.05731
0.3740.2990/2240.1490.07472
Pre-Installation Tasks
Database considerations and support
19McAfee Policy Auditor 6.2.0 Installation Guide
Vedere la pagina 18
1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 27 28

Commenti su questo manuale

Nessun commento