Netdata/Security - Revision history

Admin: /* Netdata over VPN */

2018-01-22T02:02:51Z

Netdata over VPN

← Older revision		Revision as of 02:02, 22 January 2018
Line 15:		Line 15:
	We can then bind netdata to that private network interface, so that only peers connecting to the machine via the VPN will be able to see netdata.		We can then bind netdata to that private network interface, so that only peers connecting to the machine via the VPN will be able to see netdata.

	To expose netdata to a ~~virtual network interface~~:		===Example===

			Suppose we have a virtual private network set up with [[Tinc]], and machine 1 (running netdata) is publicly accessible at 1.2.3.4, and accessible on the VPN at 10.6.0.1, while machine 2 (which wants to access machine 1's netdata instance) is on the VPN at 10.6.0.2.

			We want to expose the netdata instance on the IP address 10.6.0.1, and not 1.2.3.4, so that only other clients on the VPN can access netdata. This VPN is referred to as a "management LAN".

			In the netdata configuration file, <code>/etc/netdata/netdata.conf</code>, set the bind to option:

	<pre>		<pre>
	[~~web~~]		[global]
	bind to = 10.1.1.1:19999 localhost:19999		bind to = 10.6.0.1:19999 localhost:19999
	</pre>		</pre>

	~~Can also~~ bind ~~netdata~~ to multiple IP addresses/ports. ~~Hostnames~~ will be resolved~~. (According to the wiki, [[Tinc]] is a good tool for virtual management LANs~~.)		(Note, we netdata can bind to multiple IP addresses/ports. Also, hostnames will be resolved.)

	==Digital Ocean guide==		==Digital Ocean guide==

Admin: /* Netdata over VPN */

2018-01-22T01:07:44Z

Netdata over VPN

← Older revision		Revision as of 01:07, 22 January 2018
Line 22:		Line 22:
	</pre>		</pre>

	Can also bind netdata to multiple IP addresses/ports. Hostnames will be resolved. (According to the wiki, [[~~Tincd~~]] is a good tool for virtual management LANs.)		Can also bind netdata to multiple IP addresses/ports. Hostnames will be resolved. (According to the wiki, [[Tinc]] is a good tool for virtual management LANs.)

	==Digital Ocean guide==		==Digital Ocean guide==

Admin: /* Netdata Wiki */

2018-01-22T01:07:36Z

Netdata Wiki

← Older revision		Revision as of 01:07, 22 January 2018
Line 9:		Line 9:
	}}		}}

	~~How to protect a netdata instance from the internet?~~		==Netdata over VPN==

	As the ~~wiki says: "netdata is~~ a ~~distributed application. Most likely you~~ will ~~have many installations of it. Since it is distributed and you are expected to jump from server to server, there is very little usability to add authentication local on each netdata~~."		To protect a netdata instance from the internet, we'll set up a VPN, which will create an associated virtual network interface.

	~~To provide athentication, netdata wiki recommends exposing~~ netdata ~~on a~~ private network interface.		We can then bind netdata to that private network interface, so that only peers connecting to the machine via the VPN will be able to see netdata.

	To expose netdata to a ~~private LAN or~~ virtual ~~network by binding to a particular~~ network interface:		To expose netdata to a virtual network interface:

	<pre>		<pre>
Line 22:		Line 22:
	</pre>		</pre>

	~~You can~~ also bind netdata to multiple IP addresses ~~and~~ ports. Hostnames will be resolved.		Can also bind netdata to multiple IP addresses/ports. Hostnames will be resolved. (According to the wiki, [[Tincd]] is a good tool for virtual management LANs.)

	~~The~~ wiki ~~also notes that~~ virtual management ~~and administration~~ LANs ~~can be created using tools like tincd or gvpe~~

	==Digital Ocean guide==		==Digital Ocean guide==

Admin: /* Netdata Wiki */

2018-01-19T14:11:59Z

Netdata Wiki

← Older revision		Revision as of 14:11, 19 January 2018
Line 23:		Line 23:

	You can also bind netdata to multiple IP addresses and ports. Hostnames will be resolved.		You can also bind netdata to multiple IP addresses and ports. Hostnames will be resolved.

			The wiki also notes that virtual management and administration LANs can be created using tools like tincd or gvpe

	==Digital Ocean guide==		==Digital Ocean guide==

Admin at 14:11, 19 January 2018

2018-01-19T14:11:13Z

← Older revision		Revision as of 14:11, 19 January 2018
Line 1:		Line 1:
	~~Two links:~~		=Notes=

	* Netdata ~~wiki, security topic: https://github.com/firehol/netdata/wiki/netdata-security~~		==Netdata Wiki==
	* Digital Ocean guide to setting up a secure Netdata instance served up via Nginx: https://www.digitalocean.com/community/tutorials/how-to-set-up-real-time-performance-monitoring-with-netdata-on-ubuntu-16-04

			From the Netdata wiki security page: https://github.com/firehol/netdata/wiki/netdata-security

			{{Quote\|
			netdata is a monitoring system. It should be protected, the same way you protect all your admin apps. We assume netdata will be installed privately, for your eyes only.
			}}

			How to protect a netdata instance from the internet?

			As the wiki says: "netdata is a distributed application. Most likely you will have many installations of it. Since it is distributed and you are expected to jump from server to server, there is very little usability to add authentication local on each netdata."

			To provide athentication, netdata wiki recommends exposing netdata on a private network interface.

			To expose netdata to a private LAN or virtual network by binding to a particular network interface:

			<pre>
			[web]
			bind to = 10.1.1.1:19999 localhost:19999
			</pre>

			You can also bind netdata to multiple IP addresses and ports. Hostnames will be resolved.

			==Digital Ocean guide==

			Digital Ocean guide to setting up a secure Netdata instance served up via Nginx: https://www.digitalocean.com/community/tutorials/how-to-set-up-real-time-performance-monitoring-with-netdata-on-ubuntu-16-04

Admin at 14:05, 19 January 2018

2018-01-19T14:05:01Z

← Older revision		Revision as of 14:05, 19 January 2018
Line 1:		Line 1:
	Two links:		Two links:

	Netdata wiki, security topic: https://github.com/firehol/netdata/wiki/netdata-security		* Netdata wiki, security topic: https://github.com/firehol/netdata/wiki/netdata-security
			* Digital Ocean guide to setting up a secure Netdata instance served up via Nginx: https://www.digitalocean.com/community/tutorials/how-to-set-up-real-time-performance-monitoring-with-netdata-on-ubuntu-16-04
	Digital Ocean guide to setting up a secure Netdata instance served up via Nginx: https://www.digitalocean.com/community/tutorials/how-to-set-up-real-time-performance-monitoring-with-netdata-on-ubuntu-16-04

Admin: Created page with "Two links: Netdata wiki, security topic: https://github.com/firehol/netdata/wiki/netdata-security Digital Ocean guide to setting up a secure Netdata instance served up via N..."

2018-01-19T14:04:48Z

Created page with "Two links: Netdata wiki, security topic: https://github.com/firehol/netdata/wiki/netdata-security Digital Ocean guide to setting up a secure Netdata instance served up via N..."

New page

Two links:

Netdata wiki, security topic: https://github.com/firehol/netdata/wiki/netdata-security

Digital Ocean guide to setting up a secure Netdata instance served up via Nginx: https://www.digitalocean.com/community/tutorials/how-to-set-up-real-time-performance-monitoring-with-netdata-on-ubuntu-16-04

=Flags=

{{NetdataFlag}}