Implementation of RFC 9116 (security.txt) as well as possibility for encrypted contact

This page summarizes the projects mentioned and recommended in the original post on /r/safing

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • securitytxt.org

    Static website for security.txt.

  • Especially in the area you guys are operating in, I think it would be great if you could implement RFC 9116 (https://securitytxt.org/). If someone finds a vulnerability on your website, the client or even the SPN, this would make communication or a responsible disclosure process much easier. Furthermore, it would be great if the possibility for secure communication with your staff (e.g. using GPG) would be possible.

  • PrivateBin

    A minimalist, open source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES.

  • Also when sending a ticked via Portmaster we use https://privatebin.info/ (self hosted) which is encrypted and auto deletes the info after (I think) a week

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • portmaster

    🏔 Love Freedom - ❌ Block Mass Surveillance

  • Thanks for the suggestion, concerns about code is best discussed over on GitHub https://github.com/safing/portmaster/issues

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts