Author: admin

ntop

Network Traffic and Security Monitoring Using ntopng and InfluxDB

Yesterday our friends at InfluxData organised a meetup at their HQ in San Francisco, CA. For all those who have been unable to attend the event, these are the presentation slides so you can learn more about the transition from RRD to InfluxDB that is happening in ntopng. Please do not forget to provide feedback on the ntop mailing list or on github. Thank you ! …
Announce

Introducing ntopng Edge (nEdge): Monitoring, Service Segmentation and Security for the Network Edge

The network edge, either wired or wireless, is becoming increasingly important as most things now happen there being the place where devices are deployed. Security-wise, central firewalls are too far from the edge, and thus devices can roam freely – and potentially create troubles – in LANs without ever hitting a security device. The consequence is that LANs are becoming increasingly insecure, and the cloud is complicating all of this as it provides in encrypted connections – that are not inspectable by monitoring and security applications – the perfect ingredients …
ntopng

Learning the ntopng Lua API

ntopng is open source, that means you can read its code and modify it according to the GPL license. The current ntopng architecture is based on three layers where the top one is written in Lua and it is used to render the web interface as well to execute periodic activities. In essence the C++/Lua API is a clean way to interact and extend ntopng without having to code in C++. So far we have used this API inside the ntop team without documenting it. This has been a mistake …
n2n

Using n2n to Steer your Internet Traffic and Circumvent Restrictions

Suppose that you are travelling abroad and you need to access some Internet sites that are not available abroad. Or suppose that you want to evade the restrictions of your ISP, of the hotel room where you are currently staying, or the WiFi hotspot you are using for connecting to the Internet. The simplest thing to do is to open a VPN and you’re done. However VPNs are not very flexible and they require a single place where everybody meet and great. n2n instead is based on the peer-to-peer paradigm …
Announce

You’re Invited to the “Monitoring with Time Series” Meetup: San Francisco June 27th

Hi all this is to invite all of you living in San Francisco and in the Bay Area to attend the “Monitoring with Time Series” meetup organised by our friends at InfluxData. I will be speaking about ntop, traffic monitoring, time series and InfluxDB. It will also be a good time to meet with our users, hear suggestions, and (perhaps) complains. The Internet is a nice place, but a physical meeting has no price. The meetup will take place at InfluxData HQ, 799 Market St Suite 400, San Francisco. The …
ntopng

Best Practices to Secure ntopng

After a fresh install, ntopng will run using a default, basic configuration. Such configuration is meant to provide an up-and-running ntopng but does not try to secure it. Therefore, the default configuration should only be used for testing purposes in non-production environments. Several things are required to secure ntopng and make it enterprise-proof. Those things include, but are not limited to, enabling an encrypted web access, restricting the web server access, and protecting the Redis server used by ntopng as a cache. Here is the list of things required to …
n2n

n2n is back !

Hi all, it is finally time to restart development activities in n2n whose code is available at https://github.com/ntop/n2n. The advent of the cloud, privacy concerns on the Internet, mobile users now producing a large amount of Internet traffic, require a secure network overlay such as n2n to build upon. Initially designed to solve our connectivity issues created by NATs, we believe it is now time to refresh it and serve modern user needs. The first activity we would like to do is to merge back in the n2n repository all …
ntopng

How ntop built a web-based traffic analysis and flow collection with InfluxDB

A couple of days ago InfluxData hosted a ntop webinar about how we have integrated InfluxDB into ntopng. Those who have not attended it can give a look at the presentation slides as well watch the webinar. In essence: ntopng is based on RRD for timeseries As networks grow, ntopng needs to store more time series more granular. RRD is file based, that is a good things as configuration is minimal, but it does not scale on mid/large networks. We need an alternative, and found InfluxDB to be the best option …
ntopng

How to use ntopng in compliance with GDPR

Today the General Data Protection Regulation (GDPR) (EU) 2016/679 is effective in the European Union. GDPR is designed to protect personal data and thus preserve privacy in particular as specified in articles 13 to 22, and 34. As we manufacture tools for traffic monitoring, we’ve to make sure that our tools can be used in compliancy with GDPR. In particular we’ve implemented a couple of features that can be useful: If you go select “Preferences” from the ntopng menu, and click on the “Misc” pane you can access the preference for …
ntop

Webinar Invitation: ntop traffic analysis and flow collection with InfluxDB

Hi all, this is to invite all of your to the How ntop built their high-speed Web-based traffic analysis and flow collection with the use of InfluxDB webinar, organised by our friends at InfluxData. The event will take place May 29th at 8AM PST (5PM CET). I will be talking about traffic monitoring and timeseries, why we used RRD, and how we have integrated InfluxDB (including ongoing developments). …
ntopng

ntopng goes Elastic: Introducing ElasticSearch 6 Support

As you ntopng users know, out of the Elastic toolset ntopng supports both ElasticSearch and LogStash. You can use them using the -F flag: --dump-flows|-F] <mode> | Dump expired flows. Mode: | es Dump in ElasticSearch database | Format: | es;<mapping type>;<idx name>;<es URL>;<http auth> | Example: | es;ntopng;ntopng-%Y.%m.%d;http://localhost:9200/_bulk; | Notes: | The <idx name> accepts the strftime() format. | <mapping type>s have been removed starting at | ElasticSearch version 6. <mapping type> | values whill therefore be ignored when using | versions greater than or equal to 6. | …
nProbe

Using nProbe for Collecting Palo Alto Flows

NOTE: This article is outdated. Please see “Collecting Proprietary Flows with nProbe” for learning  how to collect proprietary Palo Alto flows. nProbe is both a probe and a NetFlow/sFlow collector. As you all know, we have recently added the ability to collect flows with proprietary information elements. However we natively support in nProbe popular flow exporter devices such as Cisco NBAR and Palo Alto security devices. In this article we show you how to collect the latter flows in nProbe. A typical Palo Alto flow is depicted below. As explained …