SECURITY

Vulnerability Disclosure Policy

Type: PolicyVersion: Draft 1.0Last updated: [Effective date]Owner: legal@closedlab.com

Draft for legal review. This document is a template prepared for ClosedLab and has not been adopted. It is not legal advice — have qualified counsel review it, and fill in the bracketed items, before publishing or signing.

We welcome reports from security researchers. This policy explains what you may test, how to report what you find, and what you can expect from us.

1.Scope

In scope: closedlab.com and ClosedLab platforms you are authorized to use (Workspace, AI, Client Portal, Cloud Console). Out of scope: client systems we build or host, third-party services, physical security, and social engineering of staff or clients.

2.Rules of engagement

  • Test only accounts and data you own or have explicit permission to use
  • Do not access, change, or delete data that is not yours; stop and report as soon as you see it
  • Do not degrade service — no denial-of-service, spam, or automated high-volume scanning
  • Give us reasonable time to fix an issue before any public disclosure

3.How to report

Email security@closedlab.com with a description, steps to reproduce, affected URLs or components, and the potential impact. Encrypted reports are welcome; our key and contact details are published at /.well-known/security.txt.

4.What to expect

  • Acknowledgment within three business days
  • An initial assessment within ten business days
  • Regular updates until the issue is resolved
  • Credit in our acknowledgments if you would like it

5.Safe harbor

If you act in good faith and follow this policy, we will not pursue legal action against you for your research, and we will work with you to understand and resolve the issue.

6.Rewards

We do not currently run a paid bug bounty program. [Update if a bounty program is introduced.]

All legal documents