Matasano’s Flint: Open Source Interesting but Viable?

Matasano Security, a security consulting and research firm, has released Flint, an open source tool that evaluates rules found on Cisco firewalls for outdated, redundant, or exposure to other security threats.  Flint is based on Ruby on Rails, is available as a VMware virtual appliance, and source code is available.  Per Dark Reading’s Kelly Jackson Higgins, Tom Ptacek, Principal with Matasano, said, “It’s easy to extend, and we’re hoping to get a lot of feedback from the network security community.”

In case you’ve missed it, security change and configuration management is a hot market that has traditionally focused on firewalls; Pioneers/leaders in this market include AlgoSec, Tufin, SecurePassage, and Skybox Security.  However, companies like Tufin are moving beyond the firewall to include classic network devices such as routers, switches, load balancing, and more.  Matasano’s Flint is a hybrid of sorts as their first release only supports Cisco firewalls, yet the software (caveat as I have not yet seen the open source licensing on Flint) may be extended by the community to include different functionality and device types.

Like any development model, open source has produced some winners and some forgettable products.   My question is; will a security developer community evolve around Flint or will it simply become a user community?  Empirical evidence gathered by my involvement with ZipTie, an open source framework for Network Inventory and Configuration Management, suggests the latter may be true.

Sure, there are some major differences between ZipTie and Flint.  While ZipTie is built on Java, Flint is built on Ruby.  While ZipTie is backed by AlterPoint (a commercial network change and configuration vendor), Flint is backed by Matasano Security a security consulting and research firm.  However, one undeniable similarity lies within the belief that a development community exists and will emerge to enhance, extend, or white label the solution.  ZipTie learned that while their community is vibrant, growing, and full of incredible ideas, the development community it coveted never materialized putting the burden squarely on ZipTie itself.  Faced with this reality, ZipTie morphed into AlterPoint NetworkAuthority Inventory where it continues to be available today.

Security and firewall administration is a complex and high-profile responsibility within any IT organization.  While these men and women are talented in many aspects of security, they also are specialized via security manufacturers and product types.  For example; CheckPoint Firewalls (Appliance/Blade), Juniper NetScreen, Fortinet FortiGate, Linux Firewalls, TippingPoint IPS, Snort, and more.  However, are they Ruby developers?

Development communities, in any form, are powerful additions to a company’s portfolio.  However, they are easier to find within the application world of operating systems, virtualization hypervisors, databases, and more.  For the worlds of networking and security, why not create a specialized development community that is focused on areas of the product where their involvement makes sense? Examples of such communities include; AlterPoint’s Forge and Tufin’s Open Development Platform Alliance.

While Matasano Security’s Flint is open source interesting, is it a viable alternative to its commercial competitors?  Albeit Flint receives a good geek score, I’ll leave the security and reputation of my company to the commercial vendors.  In any case, here’s to Matasano’s team as they’ve certainly drawn attention to their security consulting and research business.

Security: Moving Beyond Firewall Configuration Management

For over 20 years, the firewall has been the cornerstone of TCP/IP (Internet) security.  In fact, the firewall has crossed-over from the geek to the chic as it has appeared or starred in print, television, and movies.  While the battle between hackers and security vendors rages on, firewalls have become more sophisticated and complicated to operate and manage. Further adding to the complexity is the increasing trend to build firewalls into routers, switches, unified chassis, and more.

Over the past few years, companies like Tufin, AlgoSec, SecurePassage, Skybox Security, and more have created products that analyze firewalls configurations, rules, and policies to alert security personnel to possible issues.  They have the ability to manage multiple firewall vendors as well as analyzing configurations from multiple firewalls deployed within an organization.  These products are essential to managing and maintaining an ever complex and changing security posture that requires automation to augment and compliment human interaction.  However, to completely understand an organizations security posture we must move beyond the firewall.

While firewalls are complex, they represent only a fraction of the total number of network devices within an organization.  Security personal routinely issue changes to routers, switches, IDS/IDP, and more that impact the entire network infrastructure.  Adding to the complexity are new devices and technology, such as WAN acceleration and virtualization, which are becoming mainstream.  These changes are important to maintain security and regulatory compliance within an organization.

However, the broad impact of these changes (access control lists, port security, network access control, VPNs, and more) may never be fully understood until after the changes are made. High availability and disaster recovery only adds to the complexity as they require synchronized changes/configurations across multiple devices and manufacturers.

Of course, using modeling software from companies like OPNET coupled with internal testing/procedures will aid organizations in making these changes.  The issue is how fresh the information obtained is and the time allotted to make the change given the severity/urgency of the security issue.

Imagine building a security software management platform that allows security and network engineers to jointly view, analyze, and document all security changes while coupling them to a sophisticated and easy to use GRC engine.  A proposed firewall change would trigger a review of the firewall policies followed by a warning that an ACL must be changed on 2 downstream routers while suggesting a re-ordering of said ACL to mitigate a potential security risk and alerting that a HA router must be updated. Next, the GRC engine would require documentation to ensure PCI compliance is maintained.  The coup de grace would be wrapping the entire platform within a visual interface that allowed for layered views of all security/network devices.

Is this farfetched?  Perhaps, but the recent uptick in stories about cyber warfare and cloud computing security threats have created an environment that is ripe for change and innovation.