Securing the Web Interface
By default, the Kismet web server listens on all interfaces,
allowing for remote connections to the UI.
This setting is fine in a controlled environment,
but we should restrict access before we use Kismet in a real world scenario.
We can edit our kismet site configuration file
so our Kismet web server listens on our loopback interface.
We will test the new configuration
by attempting to access the Kismet web interface using our system’s IP address.
Our browser fails to open the web interface.
Navigating to localhost,
we can gain access to the Kismet login function.
We can also enable HTTPS on the web server
to encrypt our communications with the web server.
This step isn’t necessary in a lab environment.
However, we recommend setting this up before
running Kismet on a public network.
When we are ready to stop Kismet,
we can filter the running processes to find its process id.
And then use the kill command to terminate the Kismet process.