Skip to content

Security: Code-Savanna/netpulse

Security

SECURITY.md

NetPulse Security Policy

Reporting a Vulnerability

The NetPulse team and community take all security bugs in NetPulse seriously. Thank you for improving the security of NetPulse. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.

To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure.

When Should I Report a Vulnerability?

  • You think you have discovered a potential security vulnerability in NetPulse.
  • You are unsure how a vulnerability affects NetPulse.
  • You think you discovered a vulnerability in another project that NetPulse depends on.

When Should I NOT Report a Vulnerability?

  • You need help tuning NetPulse for security.
  • You need help applying security related updates.
  • Your issue is not security related.

Security Release Process

NetPulse releases security patches for the latest major version.

We do not currently have a formal security release process. We will address security vulnerabilities as they are reported and release patches as needed.

Disclosure Policy

When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, involving the following steps:

  • Confirm the problem and determine the affected versions.
  • Audit code to find any potential similar problems.
  • Prepare fixes for all releases still under maintenance. These fixes will be submitted as pull requests to the NetPulse repository.

Comments on this Policy

If you have suggestions on how this process could be improved, please submit a pull request.

There aren’t any published security advisories