Laurel's Vulnerability Disclosure Policy

Vulnerability Disclosure Philosophy

Laurel believes effective disclosure of security vulnerabilities requires mutual trust, respect, transparency and common good between Laurel and Security Researchers. Together, our vigilant expertise promotes the continued security and privacy of Laurel customers, products, and services.

Security Researchers

Laurel accepts vulnerability reports from all sources such as independent security researchers, industry partners, vendors, customers and consultants. Laurel defines a security vulnerability as an unintended weakness or exposure that could be used to compromise the integrity, availability or confidentiality of our products and services.

In-Scope Targets:

• All digital assets owned by Laurel, including *. laurel.ai.

Out-of-Scope Targets & Vulnerabilities:

• Findings from physical testing or social engineering.
• Reports on outdated browser versions.
• Missing security headers or "best practice" configurations without a demonstrated vulnerability.
• Do not perform any actions that could disrupt our services, such as denial-of-service (DoS) or distributed denial-of-service (DDoS) attacks.
• Do not access, modify, or exfiltrate any data that does not belong to you.
• If researchers encounter Laurel data in the course of their work, they must immediately notify the Laurel VDP contact and coordinate to ensure that the data is appropriately destroyed once the vulnerability has been remediated.

Our Commitment to Researchers

• Trust. We maintain trust and confidentiality in our professional exchanges with security researchers.
• Respect. We treat all researchers with respect and recognize your contribution for keeping our customers safe and secure.
• Transparency. We will work with you to validate and remediate reported vulnerabilities in accordance with our commitment to security and privacy.
• Common Good. We investigate and remediate issues in a manner consistent with protecting the safety and security of those potentially affected by a reported vulnerability.

What We Ask of Researchers

• Trust. We request that you communicate about potential vulnerabilities in a responsible manner, providing sufficient time and information for our team to validate and address potential issues.
• Respect. We request that researchers make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing.
• Transparency. We request that researchers provide the technical details and background necessary for our team to identify and validate reported issues, using the form below.
• Common Good. We request that researchers act for the common good, protecting user privacy and security by refraining from publicly disclosing unverified vulnerabilities until our team has had time to validate and address reported issues.

Vulnerability Reporting

Laurel recommends that security researchers share the details of any suspected vulnerabilities across any asset owned, controlled, or operated by Laurel (or that would reasonably impact the security of Laurel and our users) using the web form below. The Laurel Security team will acknowledge receipt of each vulnerability report, conduct a thorough investigation, and then take appropriate action for resolution.

Submission form

Summary title

Help us get an idea of what this vulnerability is about.

Submission title

Target

Select the vulnerable target

Targets that are not explicitly in scope may not be eligible for acceptance.

Target

Select target…app.laurel.ai*.laurel.aiOther

Technical severity

The Vulnerability Rating Taxonomy is the baseline guide used for classifying technical severity.

VRT Category

Select or search for a vulnerability type

VRT Subcategory (optional)

VRT Variant (optional)

Vulnerability details

URL / Location of vulnerability (optional) For example: https://secure.server.com/some/path/file.php

Description

Describe the vulnerability and its impact.

Provide a proof of concept or replication steps.

Maximum 25,000 characters.

Write in Markdown Preview Markdown

Embed images by dragging & dropping, selecting, or pasting them. Markdown supported

Attachments (optional)

Attach proof-of-concept scripts, screenshots, screen recordings, etc.

Add attachments

You can attach up to 20 files. Please keep individual upload size under 400MiB.

You can embed attachments (.jpg/.gif/.png, smaller than 5MB) into the Markdown fields. You can copy the embed code using the ‘Copy as Markdown’ button.

Email

By providing your email address you can claim your submission on bugcrowd.com.

Confirmation

Confirm your submission is accurate and adheres to Bugcrowd’s terms & conditions.

I agree to Bugcrowd’s terms & conditions as well as any additional rules and instructions provided by the organization hosting this program

Report vulnerability