Already a year has passed since we started to open source this project and looking at the goals we set out back then we surely have surpassed them all. With the help of the entire development team the AbuseIO-4 branch is progressing very nicely and with loads of features. Our developers are still very busy working on the next release, but a few items from the road map are already completed:

What to expect in version 4.0

Laravel Framework
One of the biggest improvements is the usage of the Laravel Framework instead of building all code snippets manually. All external methods/functions are either included from already provide packages from Packagist or we created the package ourselves and added it into Packagist. Especially all the parsers from notifiers are separately packaged so others can use only the parts from the AbuseIO code they would need.

The framework allows for easy updating with a single CLI command, including all the database migrations and reconfiguration of settings that are needed. Also all validations are simplified and default protection for forms, injects, methods, etc are added, this saves the developers a lot of time checking for possible issues with the system.

Domain support
Domains are, next to IP assignments, supported native in the event system. Even when the IP does not exists locally you can still treat a domain locally as if it exists in your domain administration back end. Both the IP and the domain owner are contacted for abuse cases and linked to the same ticket.

Templates
One of the commonly requested features was the support for templates for customer/end-user facing pages. With the upcoming new release every little bit of text can be updated both for customization as well as for translation. By default we supplied the system with English and Dutch texts.

CLI Tools
Basically all the interactions from the web interface can now also be done from the command line. This would reduce the need for administrators accessing the database directly and allows for scripted interaction with the system.

Accounts and Branding
Larger companies have multiple brands, each with their own requirements settings and basic configurations. With branding you can use a single AbuseIO instance for multiple brands or even resellers with restricted access to their own resources. With the branding options each brand will also be able to configure their own header text and logo’s.

Build-in multi-user support
By default the system allows the creation of multiple users each with very specific role based access to the system. Also each use is linked to an Account and therefor will only be able to access its own local resources.

More Parsers and Collectors
In the last few months we found several more sources which can be used to enrich the abuse information in the system. All these new freely available datasets will be available in the next release give you even more (aggregated) information on abuse matter in your network.