the problem
Afick is a tool that detects uncontrolled system modifications.
One of the fundamental pillars of IT security is installing updates offered by publishers/distributions,
but these modifications generate false positives, increasing the investigation workload for administrators/the system.
the solutions
solution 1
For perfect security, it would be necessary, with each update
- Launch Afick to get a clean "before update" state and analyze the changes.
- launch the update
- Restart Afick in update mode and ignore the detected changes.
i
This solution has several drawbacks.
- It is difficult to automate.
- false positives appear in the reports
solution 2
This solution relies on the fact that package managers under Linux (rpm, deb) implement checksums.
These are calculated during package creation, and commands allow verification of the integrity of the installed files against the original files.
The `mask_sysupdate` directive, from version 3.8.0 onwards, allows the package system checksums to be taken into account:
if `afick` detects a modification
, and if the checksum matches the rpm/deb database,
then it's a false positive;
otherwise, a modification has occurred compared to the original files.
This allows the modifications introduced during package updates to be "masked."
This solution has several drawbacks.
- scanning the files takes longer
- This only works under Linux, for deb and rpm package systems.
Return to the main page