Skip to content

Security: serilog-contrib/serilog-sinks-splunk

Security

SECURITY.md

Security Policy

Reporting a Vulnerability

If you discover a security vulnerability in this project, please follow these steps to report it:

  1. Do not create a public GitHub issue for the vulnerability.
  2. Send an email to [email protected] with a detailed description of the vulnerability.
  3. Include any relevant information, such as steps to reproduce the vulnerability or proof-of-concept code.
  4. Provide your contact information so that we can follow up with you.

Response Timeline

We will do our best to respond to your report in a timely manner. Here is an outline of our response process:

  • We will acknowledge your report within 7 days.
  • Our team will investigate the reported vulnerability and determine its impact.
  • We will work on developing a fix for the vulnerability.
  • Once a fix is ready, we will release a security update.
  • We will publicly acknowledge your contribution if you choose to be credited.

Supported Versions

This project is actively maintained and security updates will be provided for the following versions:

  • Version 4.x.x (latest stable release)

If you are using an older version, we recommend upgrading to the latest stable release to benefit from the latest security fixes.

Security Measures

We take security seriously and have implemented the following measures to protect our users:

  • Regular code reviews and security audits.
  • Secure coding practices and adherence to industry best practices.
  • Continuous monitoring and vulnerability scanning of our systems.

Contact

If you have any questions or concerns regarding the security of this project, please contact us at [email protected].

There aren’t any published security advisories