Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Security Logs #707

Open
encryptyd opened this issue Feb 15, 2024 · 3 comments
Open

Request: Security Logs #707

encryptyd opened this issue Feb 15, 2024 · 3 comments

Comments

@encryptyd
Copy link

The default logging level for miniupnpd does not show add/delete/change logs for NAT and Firewall manipulations in the routing log file.

Form a security standpoint, this is highly undesirable. Security Operations Centers will want to monitor this activity in a SIEM (Security Information and Event Manager) since this code often runs on firewalls.

Please add this very critical security functionality for add/delete/change operations, ideally in standard RFC3164 syslog compliant output, and include at a minimum:

  • internal port
  • external port
  • internal IP
  • external IP
  • protocol
  • (Nice to Have) The name of the UPNP requesting agent if available (ex. demonware, etc.)

Thanks

@miniupnp
Copy link
Owner

I see there is already LOG_INFO :

you can use the -v command line to enable them.

There is no LOG_INFO AddAnyPortMapping

@miniupnp
Copy link
Owner

also :

@encryptyd
Copy link
Author

The request was really about the 'default' logging level, The -v option is known and understood. Ideally, miniupnpd should log firewall and NAT manipulation out of the box without having to take manual action such as restarting the service in verbose mode. Also, the logs are not really in a standard format, and could benefit from some standardization that makes them easier to digest in a SIEM. Things like variable=value, or ext_port=3075. Don't use spaces like "ext port %h" or "external port: %h".

@miniupnp miniupnp added this to the miniupnpd_2.4 milestone May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants