Here you can see some of our CVEs - compare that to say…. Naturally, 3rd parties have done that as well. We are constantly conducting audits and pen testing of both our infrastructure (including users -) ) as well as the product itself. The endpoint is closed once the user logs out - hence the remote access via Command Center is much more secure than just exposing admin interface on a WAN - it does not stay open and requires authenticated communication to our infrastructure from the device itself. Once this SSH connection has been established, the Command Center will redirect the user to the temporary endpoint. The security there is verified by certificates. Remote access from Command Center works by telling NGFW to open an SSL proxy connection on a random port to our relay server.
These alerts are available in Command Center for you to view, but in addition to that they will be sent to any notification provider you have set up in Command Center. In addition to that, NGFW will send alerts to our cloud. Basically, the reports you see there are sent daily by the NGFW and aggregated. If 'Connect to Command Center' is checked, the NGFW will maintain a connection to our command server and will be able to execute certain instructions, as well as send report information to Command Center.
These service collect minimal information about the NGFW: UID, version, IP address, number of hosts.
#Untangle firewall documentation update
The NGFW will still communicate with our license and update services, as well as any services used by the NGFW apps, but a lot of Command Center functionality will not be available. You have the option to turn off all Command Center communication, but we feel the benefits outweigh the risks. We take that very seriously at Untangle and have layers of security in place to protect customer data and communication pathways. Hey for the question - definitely a lot of crazy stuff going on with breaches these days.