Closed lars-devs closed 6 months ago
Hi @lars-devs. First I strongly recommend to not expose any ports to the public internet. If you want to do so you should use a more random port. Censys only scans ports that are associated with standard services.
Hi @Der-Henning,
Regarding the exposed ports, You're absolutely right. The reason why I decided to do so is that I run the scanner on three servers (1 account per server), each one taking care of 2-3 weekdays to prevent rate limit. On one server I run Prometheus to scrape the three servers and Grafana to visualize.
Do You have an idea, how to easily manage to take the metric data from my servers into one Grafana instance?
Regards, Lars
I would recommend creating a vpn with wireguard on one of your servers and connect all your servers to the vpn. This is especially useful for your server management as you do not have to expose your ssh port to the internet (see latest hack https://nvd.nist.gov/vuln/detail/CVE-2024-3094) by connecting to the vpn with your local machine. Also grafana is only available inside the vpn and not exposed to the internet. If you use a fritzbox for your home network the newest fritzos includes a wireguard server. Using this your remote servers can be available as if they are in your local network. Another way (exposing your hopefully random ssh port) is to use port forwarding via ssh to forward the metrics ports to your grafana / prometheus server.
Thanks for Your suggestions! I'll take a look at the VPN approach to avoid exposing unnecessarily exposed ports.
Hi, I enabled the metrics server to create fancy graphs with Grafana and found out, that Censys scanners tries to access the metrics. This requests lead to an exception.
Fully blocking access from Censys is possible, though.