个人工具

“UbuntuHelp:FileIntegrityAIDE”的版本间的差异

来自Ubuntu中文

跳转至： 导航, 搜索
小
小
 
（未显示同一用户的2个中间版本）
第1行： 第1行：
 
{{From|https://help.ubuntu.com/community/FileIntegrityAIDE}}
 
{{From|https://help.ubuntu.com/community/FileIntegrityAIDE}}
 
{{Languages|UbuntuHelp:FileIntegrityAIDE}}
 
{{Languages|UbuntuHelp:FileIntegrityAIDE}}
−
=== Introduction ===
+
<<Include(Tag/ContentCleanup)>>
−
One of the many possible layers of security which may be applied to your Ubuntu computer is known as ''file integrity monitoring'', or ''file integrity verification''. The purpose of monitoring and/or verifying the integrity of key files including system binaries, and configuration files is to ensure the files have not been altered by unauthorized means. The unauthorized alteration of certain system files is one of the symptoms of an active attack, or compromise upon a system. Using file integrity monitoring is a pro-active means of being aware of any changes to critical system files. As with most tools, and utilities in the GNU/Linux community, there exist many different applications for use in monitoring, and verifying the integrity of files on your Ubuntu system. This guide will mention some of these tools, and go on to discuss installation, configuration, and usage of the tools on an Ubuntu system.   
+
== Introduction ==
−
=== Available Tools ===
+
One of the many possible layers of security which may be applied to your Ubuntu computer is known as ''file integrity monitoring'' or ''file integrity verification''. The purpose of monitoring and/or verifying the integrity of key files, including system binaries and configuration files is to ensure that the files have not been altered by unauthorized means. The unauthorized alteration of certain system files is one of the symptoms of an active attack or compromise upon a system.
−
While there are literally a dozen, or more solutions for monitoring, and verifying the integrity of critical files on a GNU/Linux computer system, this guide will focus only on the '''Advanced Intrusion Detection Environment''' ('''AIDE''') utility. Other possible tools, and utilities for monitoring, and/or verifying file integrity will be listed in the '''Resources''' section of this guide, however. The exploration, and use of these tools is left as an exercise for the reader of this guide.
+
Using file integrity monitoring is a pro-active means of being aware of any changes to critical system files. As with most tools, and utilities in the GNU/Linux community, there are many different applications for use in monitoring and verifying the integrity of files on your Ubuntu system. This guide will discuss the installation, configuration, and usage of some of these tools on an Ubuntu system.   
−
=== AIDE ===
+
== Available Tools ==
−
The Advanced Intrusion Detection Environment (AIDE) is a ''free'' replacement for the popular file integrity verification tool '''Tripwire'''. It creates a database from regular expression rules that it finds in a configuration file, and once this database is initialized, it can be used to verify the integrity of critical system, and user files.
+
While there are literally a dozen or more solutions for monitoring and verifying the integrity of critical files on a GNU/Linux computer system, this guide will focus only on the '''Advanced Intrusion Detection Environment''' ('''AIDE''') utility. Other possible tools, and utilities for monitoring and/or verifying file integrity will be listed in the '''Resources''' section. The exploration and use of these tools is left as an exercise for the reader of this guide.
−
AIDE uses most of the popular message digest algorithms (md5,sha1,rmd160,tiger,haval,etc.) for checking file integrity. Additional algorithms may also be added easily. All of the traditional file system attributes may also be checked for inconsistencies as well.
+
== AIDE ==
−
==== Installing AIDE ====
+
The Advanced Intrusion Detection Environment (AIDE) is a ''free'' replacement for the popular file integrity verification tool known as '''Tripwire'''. It creates a database from regular expression rules that it finds in a configuration file. Once this database is initialized, it can be used to verify the integrity of critical system and user files.
 +
AIDE uses most of the popular message digest algorithms (md5, sha1, rmd160, tiger, haval, etc.) for checking file integrity. Additional algorithms may also be easily added. All of the traditional file system attributes may be checked for inconsistencies as well.
 +
=== Installing AIDE ===
 
To install AIDE from a terminal prompt, ensure that your Internet connection is working, and enter the following command:
 
To install AIDE from a terminal prompt, ensure that your Internet connection is working, and enter the following command:
−
<code><nowiki>sudo apt-get install aide</nowiki></code>
+
<pre><nowiki>
−
Enter your password, and upon successful authentication, the AIDE package should be fetched, and installed.
+
sudo apt-get install aide
−
During installation, an '''Ubuntu Configuration''' window will appear notifying you that daily reports are mailed to the ''root'' user by default, and that this behavior may be changed by editing the <code><nowiki>/etc/default/aide</nowiki></code> configuration file. Press '''ENTER''' to acknowledge this message. You will then be asked if the AIDE database should be initialized. Select '''Yes''' here, and press '''ENTER'''. The next confirmation dialog asks you to examine <code><nowiki>/var/lib/aide/aide.db.new</nowiki></code> before replacing any existing database. If this is your first time installing AIDE on the system in question, select '''Yes''' here, and press '''ENTER'''.
+
</nowiki></pre>
−
==== Configuring AIDE ====
+
Enter your password. Upon successful authentication, the AIDE package should be fetched and installed.
 +
During installation, an '''Ubuntu Configuration''' window will appear notifying you that daily reports are mailed to the ''root'' user by default, and that this behavior may be changed by editing the <code><nowiki>/etc/default/aide</nowiki></code> configuration file. Press the '''Enter''' key to acknowledge this message. You will then be asked if the AIDE database should be initialized. Select '''Yes''' here, and press the '''Enter''' key. The next confirmation dialog will ask you to examine <code><nowiki>/var/lib/aide/aide.db.new</nowiki></code> before replacing any existing database. If this is your first time installing AIDE on the system in question, select '''Yes''' here, and press the '''Enter''' key.
 +
=== Configuring AIDE ===
 
There are two primary configuration files for AIDE:
 
There are two primary configuration files for AIDE:
 
{|border="1" cellspacing="0"
 
{|border="1" cellspacing="0"
−
|<code><nowiki>/etc/default/aide</nowiki></code>||The AIDE general configuration file
+
|<code><nowiki>/etc/default/aide</nowiki></code>||The AIDE general configuration file.
 
|-
 
|-
−
|<code><nowiki>/etc/aide/aide.conf</nowiki></code>||The AIDE rules configuration file
+
|<code><nowiki>/etc/aide/aide.conf</nowiki></code>||The AIDE rules configuration file.
−
|}
+
−
Some general settings, and behaviors for AIDE may be modified by editing the <code><nowiki>{/etc/default/aide</nowiki></code> configuration file. For example, if you would like to have all of AIDE's daily reports e-mailed to the user <code><nowiki>breandon</nowiki></code> instead of the default root user, simply use <code><nowiki>sudo</nowiki></code> with your favorite editor, and modify the line:
+
−
{|border="1" cellspacing="0"
+
−
|<code><nowiki>MAILTO=root</nowiki></code>
+
−
|}
+
−
so that it reflects your choice of user (<code><nowiki>breandon</nowiki></code> in our example) as such:
+
−
{|border="1" cellspacing="0"
+
−
|<code><nowiki>MAILTO=breandon</nowiki></code>
+
 
|}
 
|}
 +
Some general settings and behaviors for AIDE may be modified by editing the <code><nowiki>{/etc/default/aide</nowiki></code> configuration file. For example, if you would like to have all of AIDE's daily reports emailed to the user <code><nowiki>breandon</nowiki></code> instead of the default root user, simply use <code><nowiki>sudo</nowiki></code> with your favorite editor, and modify the line <code><nowiki>MAILTO=root</nowiki></code> to reflect your choice of user (<code><nowiki>breandon</nowiki></code> in our example) as in this example: <code><nowiki>MAILTO=breandon</nowiki></code>.
 
Read the comments in <code><nowiki>/etc/default/aide</nowiki></code> to see what the other configuration directives control, and change them accordingly to suit your installation's requirements.
 
Read the comments in <code><nowiki>/etc/default/aide</nowiki></code> to see what the other configuration directives control, and change them accordingly to suit your installation's requirements.
−
The other configuration file, <code><nowiki>/etc/aide/aide.conf</nowiki></code> controls the rules for the directories, files, and attributes of files which AIDE uses to determine changes when scanning. For example, in the default <code><nowiki>/etc/aide/aide.conf</nowiki></code> file, all member directories and files of the Group definition <code><nowiki>BinLib</nowiki></code> are checked for permissions, inode, number of links, user, group, size, block count, mtime, ctime, md5 checksum, and sha1 checksum (p+i+n+u+g+s+b+m+c+md5+sha1) whereas all member directories, and files in the Group definition Databases are checked only for permissions, number of links, user, and group (p+n+u+g).
+
The other configuration file, <code><nowiki>/etc/aide/aide.conf</nowiki></code> controls the rules for the directories, files, and attributes of the files AIDE uses to determine changes when scanning. For example, in the default <code><nowiki>/etc/aide/aide.conf</nowiki></code> file, all member directories and files of the Group definition <code><nowiki>BinLib</nowiki></code> are checked for permissions, inode, number of links, user, group, size, block count, mtime, ctime, md5 checksum, and sha1 checksum (p+i+n+u+g+s+b+m+c+md5+sha1), whereas all member directories and files in the Group definition Databases are checked only for permissions, number of links, user, and group (p+n+u+g).
−
The member directories of a particular Group definition are added by specifying one entry per line, in the form of :
+
The member directories of a particular Group definition are added by specifying one entry per line, in the form of:
 
{|border="1" cellspacing="0"
 
{|border="1" cellspacing="0"
 
|<code><nowiki>directory</nowiki></code> <code><nowiki>Group definition</nowiki></code>
 
|<code><nowiki>directory</nowiki></code> <code><nowiki>Group definition</nowiki></code>
第38行： 第35行：
 
|<code><nowiki>/opt/local/bin BinLib</nowiki></code>
 
|<code><nowiki>/opt/local/bin BinLib</nowiki></code>
 
|}
 
|}
−
Another example of a clever use for AIDE is to monitor the system's crontabs. System crontabs control the scheduled system activities which are executed on a schedule by the cron daemon. To ensure these files are not altered in such a way as to introduce the automatic, scheduled execution of a malicious application, simply use the <code><nowiki>sudo</nowiki></code> command to edit the <code><nowiki>/etc/aide/aide.conf</nowiki></code> file with your favorite editor and locate the following section of the file :
+
Another example of a clever use for AIDE is to monitor the system's crontabs. System crontabs control the scheduled system activities which are executed on a schedule by the cron daemon. To ensure that these files are not altered in such a way as to introduce the automatic, scheduled execution of a malicious application, simply use the <code><nowiki>sudo</nowiki></code> command to edit the <code><nowiki>/etc/aide/aide.conf</nowiki></code> file with your favorite editor and locate the following section of the file:
 
{|border="1" cellspacing="0"
 
{|border="1" cellspacing="0"
 
|<code><nowiki># Check crontabs</nowiki></code>
 
|<code><nowiki># Check crontabs</nowiki></code>
 
|}
 
|}
−
Uncomment all of the lines beginning with <code><nowiki>#/var/spool</nowiki></code> under the <code><nowiki># Check crontabs</nowiki></code> heading, and save the file.
+
Uncomment all of the lines beginning with <code><nowiki>#/var/spool</nowiki></code> under the <code><nowiki># Check crontabs</nowiki></code> heading, and save the file. You should examine the <code><nowiki>/etc/aide/aide.conf</nowiki></code> file closely, observing the commented sections in particular, for other possible uses of AIDE. Also read the <code><nowiki>aide.conf</nowiki></code> manual page, in addition to reading the HTML version of the AIDE manual, for further uses of AIDE which may be specified in this configuration file.
−
You should examine the file <code><nowiki>/etc/aide/aide.conf</nowiki></code> closely, observing the commented sections in particular, for other possible uses of AIDE, and read the <code><nowiki>aide.conf</nowiki></code> manual page, in addition to reading the HTML version of the AIDE manual for further uses of AIDE which may be specified in this configuration file.
+
After making configuration changes, issue the following command at the terminal prompt to update the AIDE configuration:
−
When you've made configuration changes, and you would like them used immediately, issue the following command at the terminal prompt to update the AIDE configuration:
+
<pre><nowiki>
−
<code><nowiki>sudo update-aide.conf</nowiki></code>
+
sudo update-aide.conf
−
Otherwise, AIDE's daily crontab will do the same thing, so if you have made changes, but do not need to run aide manually, and immediately you can be assured the configuration will be updated by the daily crontab automatically before the daily run of AIDE by the daily crontab.
+
</nowiki></pre>
−
==== Using AIDE ====
+
=== Using AIDE ===
 
To begin using AIDE, you must make sure the database is present:
 
To begin using AIDE, you must make sure the database is present:
−
<code><nowiki>ls /var/lib/aide</nowiki></code>
+
<pre><nowiki>
−
If you see the file <code><nowiki>aide.db</nowiki></code> in the output of the <code><nowiki>ls</nowiki></code> command, then proceed to the initialization step. If instead, you see the file <code><nowiki>aide.db.new</nowiki></code> then you need to rename the <code><nowiki>aide.db.new</nowiki></code> file to <code><nowiki>aide.db</nowiki></code> using this command:
+
ls /var/lib/aide
−
<code><nowiki>sudo mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db</nowiki></code>
+
</nowiki></pre>
 +
If you see the file <code><nowiki>aide.db</nowiki></code> in the output of the <code><nowiki>ls</nowiki></code> command, then proceed to the initialization step. If, instead, you see the file <code><nowiki>aide.db.new</nowiki></code>, then you need to rename the <code><nowiki>aide.db.new</nowiki></code> file to <code><nowiki>aide.db</nowiki></code> using this command:
 +
<pre><nowiki>
 +
sudo mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db
 +
</nowiki></pre>
 
Once the AIDE database is in place, you can initialize the database with the following command from a terminal prompt:
 
Once the AIDE database is in place, you can initialize the database with the following command from a terminal prompt:
−
<code><nowiki>sudo aide --init</nowiki></code>
+
<pre><nowiki>
 +
sudo aide --init
 +
</nowiki></pre>
 
At the end of this process, you should see the line:
 
At the end of this process, you should see the line:
 
{|border="1" cellspacing="0"
 
{|border="1" cellspacing="0"
第59行： 第62行：
 
|}
 
|}
 
You may run an initial check of the directories and files as defined in <code><nowiki>/etc/aide/aide.conf</nowiki></code> by entering the following command at a terminal prompt:
 
You may run an initial check of the directories and files as defined in <code><nowiki>/etc/aide/aide.conf</nowiki></code> by entering the following command at a terminal prompt:
−
<code><nowiki>sudo aide --check</nowiki></code>
+
<pre><nowiki>
 +
sudo aide --check
 +
</nowiki></pre>
 
If all is well in the directories, and files being monitored, you will see this message when the check completes:
 
If all is well in the directories, and files being monitored, you will see this message when the check completes:
 
{|border="1" cellspacing="0"
 
{|border="1" cellspacing="0"
第65行： 第70行：
 
|}
 
|}
 
AIDE will also run each day from the <code><nowiki>/etc/cron.daily/aide</nowiki></code> crontab, and the output of this run will be mailed to the user specified in the <code><nowiki>MAILTO=</nowiki></code> directive of the <code><nowiki>/etc/default/aide</nowiki></code> configuration file as detailed above.
 
AIDE will also run each day from the <code><nowiki>/etc/cron.daily/aide</nowiki></code> crontab, and the output of this run will be mailed to the user specified in the <code><nowiki>MAILTO=</nowiki></code> directive of the <code><nowiki>/etc/default/aide</nowiki></code> configuration file as detailed above.
−
=== Resources ===
+
== Resources ==
−
Additional information on AIDE, and file integrity monitoring, and verification is available via the following resources:
+
Additional information on AIDE, and file integrity monitoring and verification is available via the following resources:
−
==== Local System Resources ====
+
=== Local System Resources ===
 
{|border="1" cellspacing="0"
 
{|border="1" cellspacing="0"
−
|<code><nowiki>man aide</nowiki></code>|| System manual page for the <code><nowiki>aide</nowiki></code> command
+
|<code><nowiki>man aide</nowiki></code>|| System manual page for the <code><nowiki>aide</nowiki></code> command.
 
|-
 
|-
−
|<code><nowiki>man aide.conf</nowiki></code>|| System manual page for the <code><nowiki>aide.conf</nowiki></code> configuration file
+
|<code><nowiki>man aide.conf</nowiki></code>|| System manual page for the <code><nowiki>aide.conf</nowiki></code> configuration file.
 
|-
 
|-
−
|<code><nowiki>man aideinit</nowiki></code>|| System manual page for the <code><nowiki>aideinit</nowiki></code> command
+
|<code><nowiki>man aideinit</nowiki></code>|| System manual page for the <code><nowiki>aideinit</nowiki></code> command.
 
|-
 
|-
−
|<code><nowiki>man update-aide.conf</nowiki></code>|| System manual page for the <code><nowiki>update-aide.conf</nowiki></code> command
+
|<code><nowiki>man update-aide.conf</nowiki></code>|| System manual page for the <code><nowiki>update-aide.conf</nowiki></code> command.
 
|-
 
|-
−
|<code><nowiki>/usr/share/doc/aide/manual.html</nowiki></code>|| The AIDE manual in HTML format
+
|<code><nowiki>/usr/share/doc/aide/manual.html</nowiki></code>|| The AIDE manual in HTML format.
 
|-
 
|-
−
|<code><nowiki>/etc/default/aide</nowiki></code>|| The AIDE general configuration file
+
|<code><nowiki>/etc/default/aide</nowiki></code>|| The AIDE general configuration file.
 
|-
 
|-
−
|<code><nowiki>/etc/aide/aide.conf</nowiki></code>|| The AIDE rules configuration file
+
|<code><nowiki>/etc/aide/aide.conf</nowiki></code>|| The AIDE rules configuration file.
 
|-
 
|-
−
|<code><nowiki>/etc/cron.daily/aide</nowiki></code>|| Daily AIDE cron scripts
+
|<code><nowiki>/etc/cron.daily/aide</nowiki></code>|| Daily AIDE cron scripts.
 
|}
 
|}
−
==== Other File Integrity Monitoring and Verification Tools ====
+
=== Other File Integrity Monitoring and Verification Tools ===
−
* '''BSign''' : Corruption and Intrusion Detection using embedded hashes
+
* '''BSign''' : Corruption and Intrusion Detection using embedded hashes.
−
* '''Integrit''' : Small footprint, unattended monitoring of file integrity with cascading rulesets [http://integrit.sourceforge.net/ Integrit Website]
+
* '''Integrit''' : Small footprint, unattended monitoring of file integrity with cascading rulesets.
−
* '''Samhain''' : Standalone, or Client-Server file integrity monitoring solution [http://la-samhna.de/samhain/ Samhain Website]
+
* '''Samhain''' : Standalone, or Client-Server file integrity monitoring solution.
−
* '''Systraq''' : Monitors, and alerts on file changes [http://mdcc.cx/systraq/ Systraq Website]
+
* '''Systraq''' : Monitors, and alerts on file changes.
−
==== WWW Resources ====
+
== External Links ==
−
* [http://sourceforge.net/projects/aide AIDE Website]
+
* [http://sourceforge.net/projects/aide] - AIDE web site.
−
* [http://www.linuxsecurity.com/content/view/101882/49/ Guide on CHKROOTKIT and AIDE]
+
* [http://www.linuxsecurity.com/content/view/101882/49/] - Guide for CHKROOTKIT and AIDE.
 +
* [http://la-samhna.de/samhain/] - Samhain home page.
 +
* [http://mdcc.cx/systraq/] - Systraq home page.
 
----
 
----
−
[[category:CategorySecurity]] [[category:CategoryCleanup]]
+
[[category:CategorySecurity]]
  
 
[[category:UbuntuHelp]]
 
[[category:UbuntuHelp]]

2009年11月17日 (二) 19:07的最新版本

Geographylogo.png 文章出处: 

https://help.ubuntu.com/community/FileIntegrityAIDE

Geographylogo.png 点击翻译: 

English

请不要直接编辑翻译本页，本页将定期与来源同步。

<<Include(Tag/ContentCleanup)>>

Introduction

One of the many possible layers of security which may be applied to your Ubuntu computer is known as file integrity monitoring or file integrity verification. The purpose of monitoring and/or verifying the integrity of key files, including system binaries and configuration files is to ensure that the files have not been altered by unauthorized means. The unauthorized alteration of certain system files is one of the symptoms of an active attack or compromise upon a system. Using file integrity monitoring is a pro-active means of being aware of any changes to critical system files. As with most tools, and utilities in the GNU/Linux community, there are many different applications for use in monitoring and verifying the integrity of files on your Ubuntu system. This guide will discuss the installation, configuration, and usage of some of these tools on an Ubuntu system.

Available Tools

While there are literally a dozen or more solutions for monitoring and verifying the integrity of critical files on a GNU/Linux computer system, this guide will focus only on the Advanced Intrusion Detection Environment (AIDE) utility. Other possible tools, and utilities for monitoring and/or verifying file integrity will be listed in the Resources section. The exploration and use of these tools is left as an exercise for the reader of this guide.

AIDE

The Advanced Intrusion Detection Environment (AIDE) is a free replacement for the popular file integrity verification tool known as Tripwire. It creates a database from regular expression rules that it finds in a configuration file. Once this database is initialized, it can be used to verify the integrity of critical system and user files. AIDE uses most of the popular message digest algorithms (md5, sha1, rmd160, tiger, haval, etc.) for checking file integrity. Additional algorithms may also be easily added. All of the traditional file system attributes may be checked for inconsistencies as well.

Installing AIDE

To install AIDE from a terminal prompt, ensure that your Internet connection is working, and enter the following command: 

sudo apt-get install aide

Enter your password. Upon successful authentication, the AIDE package should be fetched and installed. During installation, an Ubuntu Configuration window will appear notifying you that daily reports are mailed to the root user by default, and that this behavior may be changed by editing the /etc/default/aide configuration file. Press the Enter key to acknowledge this message. You will then be asked if the AIDE database should be initialized. Select Yes here, and press the Enter key. The next confirmation dialog will ask you to examine /var/lib/aide/aide.db.new before replacing any existing database. If this is your first time installing AIDE on the system in question, select Yes here, and press the Enter key.

Configuring AIDE

There are two primary configuration files for AIDE:

/etc/default/aide The AIDE general configuration file.
/etc/aide/aide.conf The AIDE rules configuration file.

Some general settings and behaviors for AIDE may be modified by editing the {/etc/default/aide configuration file. For example, if you would like to have all of AIDE's daily reports emailed to the user breandon instead of the default root user, simply use sudo with your favorite editor, and modify the line MAILTO=root to reflect your choice of user (breandon in our example) as in this example: MAILTO=breandon. Read the comments in /etc/default/aide to see what the other configuration directives control, and change them accordingly to suit your installation's requirements. The other configuration file, /etc/aide/aide.conf controls the rules for the directories, files, and attributes of the files AIDE uses to determine changes when scanning. For example, in the default /etc/aide/aide.conf file, all member directories and files of the Group definition BinLib are checked for permissions, inode, number of links, user, group, size, block count, mtime, ctime, md5 checksum, and sha1 checksum (p+i+n+u+g+s+b+m+c+md5+sha1), whereas all member directories and files in the Group definition Databases are checked only for permissions, number of links, user, and group (p+n+u+g). The member directories of a particular Group definition are added by specifying one entry per line, in the form of:

directory Group definition

For example, to make the directory /opt/local/bin part of the BinLib Group definition, a line would be added in the appropriate section of the /etc/aide/aide.conf configuration file resembling the following:

/opt/local/bin BinLib

Another example of a clever use for AIDE is to monitor the system's crontabs. System crontabs control the scheduled system activities which are executed on a schedule by the cron daemon. To ensure that these files are not altered in such a way as to introduce the automatic, scheduled execution of a malicious application, simply use the sudo command to edit the /etc/aide/aide.conf file with your favorite editor and locate the following section of the file:

# Check crontabs

Uncomment all of the lines beginning with #/var/spool under the # Check crontabs heading, and save the file. You should examine the /etc/aide/aide.conf file closely, observing the commented sections in particular, for other possible uses of AIDE. Also read the aide.conf manual page, in addition to reading the HTML version of the AIDE manual, for further uses of AIDE which may be specified in this configuration file. After making configuration changes, issue the following command at the terminal prompt to update the AIDE configuration: 

sudo update-aide.conf

Using AIDE

To begin using AIDE, you must make sure the database is present: 

ls /var/lib/aide

If you see the file aide.db in the output of the ls command, then proceed to the initialization step. If, instead, you see the file aide.db.new, then you need to rename the aide.db.new file to aide.db using this command: 

sudo mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db

Once the AIDE database is in place, you can initialize the database with the following command from a terminal prompt: 

sudo aide --init

At the end of this process, you should see the line:

### AIDE database initialized

You may run an initial check of the directories and files as defined in /etc/aide/aide.conf by entering the following command at a terminal prompt: 

sudo aide --check

If all is well in the directories, and files being monitored, you will see this message when the check completes:

### All files match AIDE database. Looks okay!

AIDE will also run each day from the /etc/cron.daily/aide crontab, and the output of this run will be mailed to the user specified in the MAILTO= directive of the /etc/default/aide configuration file as detailed above.

Resources

Additional information on AIDE, and file integrity monitoring and verification is available via the following resources:

Local System Resources

man aide System manual page for the aide command.
man aide.conf System manual page for the aide.conf configuration file.
man aideinit System manual page for the aideinit command.
man update-aide.conf System manual page for the update-aide.conf command.
/usr/share/doc/aide/manual.html The AIDE manual in HTML format.
/etc/default/aide The AIDE general configuration file.
/etc/aide/aide.conf The AIDE rules configuration file.
/etc/cron.daily/aide Daily AIDE cron scripts.

Other File Integrity Monitoring and Verification Tools

  • BSign : Corruption and Intrusion Detection using embedded hashes.
  • Integrit : Small footprint, unattended monitoring of file integrity with cascading rulesets.
  • Samhain : Standalone, or Client-Server file integrity monitoring solution.
  • Systraq : Monitors, and alerts on file changes.

External Links

  • [1] - AIDE web site.
  • [2] - Guide for CHKROOTKIT and AIDE.
  • [3] - Samhain home page.
  • [4] - Systraq home page.
取自“https://wiki.ubuntu.org.cn/index.php?title=UbuntuHelp:FileIntegrityAIDE&oldid=127466”