PUFIN is an application designed to monitor and maintain the integrity of files within a specified folder. It utilizes PowerShell scripting language to calculate and compare hash values of files, allowing it to detect any unauthorized modifications or deletions.
The script recursively scan the given directory tree (default is from where the driver.py is). Then, script will log any file changes including;
- Modified files
- Removed files
- Added files
Take a look at our Getting Started page to set up PUFIN for its first run.
To customise the pufin.ps1 script look at the Configuration.
- File watcher. PUFIN will emit events on any produced action over your files. It will enhance your environment to the next level of security.
- Real-time alerting. PUFIN works in real-time. Any change in your files will trigger at the moment.
- Multi-OS and reliable. With powershell language at the heart of PUFIN code. It allows us to produce faster, safer and more reliable code.
- Historical logs storage of detected events.
- File integrity checking. Automated file integrity hash production. PUFIN will analyze each file change.
- Compatible with Linux, macOS and Windows.
- Open Source software. Our software is developed as a completely free open-source model. It includes a TDD methodology to produce better software.
- Neither the project nor its developer promote any kind of illegal activity and are not responsible for any misuse or damage caused by this project.
- This project is for educational purpose only.
- Please do not use this tool on other people's devices without their permission.
- Do not use this tool to harm others.
- Use this project responsibly on your own devices only.
- It is the end user's responsibility to obey all applicable local, state, federal, and international laws.
-
Contributions are welcome and encouraged, provided your code is of sufficient quality.
-
Before submitting a pull request, please ensure that your code adheres to the license under MIT license, or dedicated to the public domain (BSD, GPL, etc. code is incompatible)
-
Your pull request should fully describe the functionality you are adding/removing or the problem you are solving. Regardless of whether your patch modifies one line or one thousand lines, you must describe what has prompted and/or motivated the change.
-
Solve only one problem in each pull request. If you're fixing a bug and adding a new feature, you need to make two separate pull requests.
-
If you're fixing three bugs, you need to make three separate pull requests. If you're adding four new features, you need to make four separate pull requests. So on, and so forth.
- Star on GitHub
- Share via Facebook and Twitter
- Sponsor via GitHub — support open source contributions on a regular basis
PUFIN is licensed under MIT License. Refer to LICENSE for more information.