# Security Policy

## Your Responsibility as the Deployer

By choosing to deploy and use this project, you are responsible for operating it in a secure environment.

As the developer, I do my best to improve this project and address security issues to the best of my knowledge and ability. However, no software is ever completely free of bugs or vulnerabilities. I cannot and will not guarantee that this project is free from security issues.

This project is provided **as is**, without any warranty. You are solely responsible for securing your deployment, protecting your data, and ensuring that the software is operated in compliance with all applicable laws and regulations.

## Security Best Practices

To help keep your installation secure, please follow these recommendations:

- **Control access to the web interface.** Only trusted users should have access to the UI.
- **Only run this software on networks where you have legal authorization** to monitor devices and collect network information.
- **Keep the software up to date.** Always install the latest releases and security patches.
- **Never expose the web interface directly to the public Internet.** This project is intended to run in trusted environments only.
- **Use a VPN for remote access.** Solutions such as WireGuard provide secure remote connectivity without exposing the application publicly.
- **Keep your operating system and all dependencies updated.** Security updates for the host system are just as important as updates for this project.
- **Protect the host system.** Use a firewall, restrict unnecessary services, and regularly review your system's security configuration.
- **Create regular backups.** Ensure you can recover your configuration and data in the event of hardware failure or a security incident.

## Reporting Security Vulnerabilities

If you discover a security vulnerability, please include as much information as possible:

- A clear description of the vulnerability
- Steps to reproduce the issue
- The affected version(s)
- Relevant logs, screenshots, or proof-of-concept code
- A suggested mitigation or fix, if available

Responsible disclosure gives me the opportunity to investigate the issue, develop a fix, and protect other users before the vulnerability becomes public.

## Project Status

This project is developed and maintained in my spare time as a hobby project.

I take security reports seriously and will make every reasonable effort to investigate reported vulnerabilities and provide a fix as quickly as possible. However, please understand that there may be periods in life where work, family, health, or other personal commitments take priority, leaving little or no time to work on this project.

While I will always try to respond promptly, I cannot guarantee response times or release dates for security fixes. Your patience and understanding are greatly appreciated.

Thank you for helping improve the security of this project.
