Sometimes, opportunity comes from necessity. In the past week I was working on a larger deployment that had multiple compliance concerns. One of the specific rules required that we provide a fault tolerant solution. As you might have guessed, this required me to document how Scrutinizer leverages our Flow Replicator to provide the required fault tolerance. So when it came time to write my blog, it seemed logical to take the information that I gathered and share it with our blog community!
In the past, network admins used packet capture technology to dig down into what was happening on their network. For troubleshooting general networking issues, this was good. But networks grew, issues became global, and security became a main player in an admin’s day. Sadly, this growth presented some problems with using packet capture technology.
I love working with schools. I love seeing young students exploring technology that I could only dream about when I was younger. (In some ways, I guess that is why I live by a major university here in North Carolina.) So when I am scheduled to meet with a school, I know that it is going to be an exciting call. Yesterday was no exception.
I was working with an evaluator the other day who needed an example of how to use the Scrutinizer API to generate data and export it to a CSV file. Honestly, I knew how the API functioned, but didn’t have much experience using it. With that in mind and being the daredevil that I am, I figured this evaluator’s request would be the perfect opportunity to roll up my sleeves and get my hands dirty.
I was attending the 12th annual NC InfoSeCon conference back in October and in one of the presentations, the speaker mentioned Dark DDoS attacks. I found this part of the talk unbelievably interesting. Combine that with the recent fuel shortage here in NC and my mind started wandering with concerns over global digital terrorism and its part in the upcoming zombie apocalypse! Ok, maybe not to that degree, but I did decide to dig deeper into the methodologies behind these types of attacks.
I was having a conversation with a customer the other day about Amazon AWS monitoring. He had some interesting insight on his company’s overall migration to Amazon Web Service (AWS). He started with, “Here’s the core of it, cloud based deployment isn’t going away for us. Though there are no directives, by this time next year I’m expecting all but two of our public-facing applications to be sitting outside of our buildings.” He even went on to say, “There’s a very real possibility that within 2-3 years we decommission half of our computer rooms”. Needless to say, any application that they use for network visibility and incident response needs to support Amazon AWS monitoring. I loved his input and because of it I decided to dig deeper. Read more
Today I’m going to write about a company named Ecessa. If you haven’t heard of them before, they have a long history of building networking hardware for businesses. Since the inception of the company, one of their primary goals has been to ensure reliable and resilient Internet connectivity.
Malware Detection and determining the cause of an incident is a requirement in todays connected world. The post U.K. Parliament’s computers tried to access porn 247,000 times in 2015 is a great example. From first glance you get the impression that people at the Parliament have way too much time on their hands. When you dig a bit deeper we start to see that this the problem isn’t an HR issues but network security issue. The good news is that with the adoption of NetFlow collection and Flow Pro Defender Scrutinizer can monitor for malware. Read more
Face it—the information technology arena is an ever-changing monster and recent news about the increase with IoT vulnerabilities is no exception. A new technology can come around all of a sudden and change how we think and do things. Don’t get me wrong; it’s exciting and it’s what our world has been built on, but it’s also a little nerve-wracking. This becomes a bigger issue in the world of security, since newer technology tends not to be completely vetted. Read more
A good number of evaluators have been asking me what’s the best way to evaluate our free virtual Netflow collector. There is a growing trend of companies moving away from dedicated hardware to a virtualized environment. However, there are many options to create such a network. Windows has Hyper-V, which is part of the Windows Server OS, VMware has ESXi to, and KVM meet these virtualization needs. Plixer supports all three of these virtual environments with our Free virtual NetFlow collector, Scrutinizer. Installation of our solution is as simple as deploying the appropriate package to the specific hypervisor.