Hello Nessus Parser users, Karl from CyberCon Security Solutions in Ohio, made an update to Nessus Parser. I really appreciate this, as I am just crazy busy in my day job right now. I have not reviewed the code yet, but I wanted to get the script out to everyone who wanted the update, and give a shot out to Karl for his efforts.
Thanks Karl.
I have received a few requests to do some feature enhancements and update the code for the new Nessus format. I will be making them, but most likely not until the end of the summer. My day job is just really crazy right now. But please keep the feed back coming.
The ACL parser tool is intended to format ACL’s from may different devices into a common format for security professionals and network professionals to easily review the data. So during the initial development, I started with Cisco ACL’s and began moving into Fortinet. As I am nearing the end of the Fortinet, I realized I am doing the reformatting wrong. What I am doing wrong is the normalization process. So this latest release parse_acl_v0.01.a4.pl will be the last version using the current model. I am restructuring the script to format the data into a common format, that can be easily imported into a database such as “OSSAMS” or MS Excel and etc.
So what does this really mean, well the current code for the most part is not dead or I am declaring it dead, and I starting over. I will still use many of the regex and other test conditions in the current code, but the restructuring or normalizing of the data will be radically different. As I am just starting the new code today I can’t tell you what those changes will be, except for the changes will be easier to follow and I will create data models and documentation as I go.
So attached to this blog post is the final version of of the v0.1 train of code. I would like to make a special shot out to toni ‘at’ cunyat.net for giving me a patch to fix a few lines of code he found an issue with. I have incorporated these lines into this version.
parse_acl_v0.01.a4.pl