I am writing an open source python tool aimed at inventoring/auditing and hardening of a system. When I started off with the project, I did some research around it and figured out that there were not many tools (at least open source) that did that (I would later come to realize that apparently I was wrong)
As of now I have written the core of the system which has the following features:
- It is going to be open source
- It is plugin based. Plugins are again written in python
- It is not going to install any agents/binaries on the remote machine/s
- It is going to provide visualization on top of the data collected and analysis done
- It is going to generate Ansible cookbooks to facilitate admins to use it directly to fix the system (if they wanted to use it at all that is)
- Capabilities of the system depend on the plugins's capabilities
- As of now the tool is limited to Linux alone, but there are plans to expand it to other platforms as well.
I already knew about Lynis, before I started writing the tool and it looked like Lynis missed in a few small areas that I could improve on. Hence, I went ahead to write this tool.
Now after I have written most of the part of this tool, I get to realize that there is Nessus which already does something similar. And now I am rethinking if at all it makes sense to write this tool, is it really solving a problem or have I just wasted time reinventing the wheel (once again).
I however found this comparison of Lynis and Nessus, by the author of Lynis itself, and am not really convinced as to how is it different from what Nessus already does (not that I am a fan of Nessus or anything)
So here is what I actually want to know : Does it really make sense to write another OS hardening tool like the one with the capabilities above ? Or would it actually make more sense to simply scrape the project now ??