Release readiness checklist
Check whether a scoped change is ready to ship and what still needs verification.
5,526,302 AI resources indexedWorking toward the world’s largest AI resource index.
Verify that filesystem integrity checking is scheduled via cron to detect unauthorized changes
--- name: cis-ubuntu-14-04-lts-1-3-2-ensure-filesystem-integr-9975a4c0d748 description: "Verify that filesystem integrity checking is scheduled via cron to detect unauthorized changes" category: "cis-os-hardening" version: "2.1.0" author: "cyberstrike-official" tags: - cis - ubuntu - ubuntu-14.04 - level-1 - scored - integrity cis_id: "1.3.2" cis_benchmark: "CIS Ubuntu Linux 14.04 LTS Benchmark v2.1.0" tech_stack: - ubuntu - linux cwe_ids: [] chains_with: - cis-ubuntu1404-v210-1-3-1 prerequisites: - cis-ubuntu1404-v210-1-3-1 severity_boost: "medium" --- # 1.3.2 Ensure filesystem integrity is regularly checked (Scored) ## Profile Applicability - Level 1 - Server - Level 1 - Workstation ## Description Periodic checking of the filesystem integrity is needed to detect changes to the filesystem. ## Rationale Periodic file checking allows the system administrator to determine on a regular basis if critical files have been changed in an unauthorized fashion. ## Audit Procedure Run the following commands to determine if there is a cron job scheduled to run the aide check: ```bash crontab -u root -l | grep aide grep -r aide /etc/cron.* /etc/crontab ``` Ensure a cron job in compliance with site policy is returned. ## Expected Result A cron job entry for AIDE should be returned showing scheduled integrity checks. ## Remediation Run the following command: ```bash crontab -u root -e ``` Add the following line to the crontab: ``` 0 5 * * * /usr/bin/aide --config /etc/aide/aide.conf --check ``` ## Default Value No AIDE cron job is configured by default. ## Notes The checking in this recommendation occurs every day at 5am. Alter the frequency and time of the checks in compliance with site policy. ## References - CIS Controls: 3.5 Use File Integrity Tools For Critical System Files ## Profile - Level 1 - Server - Level 1 - Workstation--- name: cis-ubuntu-14-04-lts-1-3-2-ensure-filesystem-integr-9975a4c0d748 description: "Verify that filesystem integrity checking is scheduled via cron to detect unauthorized changes" category: "cis-os-hardening" version: "2.1.0" author: "cyberstrike-official" tags: - cis - ubuntu - ubuntu-14.04 - level-1 - scored - integrity cis_id: "1.3.2" cis_benchmark: "CIS Ubuntu Linux 14.04 LTS Benchmark v2.1.0" tech_stack: - ubuntu - linux cwe_ids: [] chains_with: - cis-ubuntu1404-v210-1-3-1 prerequisites: - cis-ubuntu1404-v210-1-3-1 severity_boost: "medium" --- # 1.3.2 Ensure filesystem integrity is regularly checked (Scored) ## Profile Applicability - Level 1 - Server - Level 1 - Workstation ## Description Periodic checking of the filesystem integrity is needed to detect changes to the filesystem. ## Rationale Periodic file checking allows the system administrator to determine on a regular basis if critical files have been changed in an unauthorized fashion. ## Audit Procedure Run the following commands to determine if there is a cron job scheduled to run the aide check: ```bash crontab -u root -l | grep aide grep -r aide /etc/cron.* /etc/crontab ``` Ensure a cron job in compliance with site policy is returned. ## Expected Result A cron job entry for AIDE should be returned showing scheduled integrity checks. ## Remediation Run the following command: ```bash crontab -u root -e ``` Add the following line to the crontab: ``` 0 5 * * * /usr/bin/aide --config /etc/aide/aide.conf --check ``` ## Default Value No AIDE cron job is configured by default. ## Notes The checking in this recommendation occurs every day at 5am. Alter the frequency and time of the checks in compliance with site policy. ## References - CIS Controls: 3.5 Use File Integrity Tools For Critical System Files ## Profile - Level 1 - Server - Level 1 - Workstation
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.