Last updated: November 17, 2026

Secure Ideas Disclosure Policy

Introduction

Secure Ideas, LLC is applying to become a CVE Numbering Authority (CNA). This policy explains:

  • how to report vulnerabilities in Secure Ideas services;
  • how Secure Ideas discloses vulnerabilities found by our research team;
  • how we handle vulnerabilities found during client engagements; and
  • how we assign and publish CVE IDs.

This policy is in line with RFC 9116 and the CVE Program’s CNA Operational Rules.

Contact

Part A: Reporting vulnerabilities in Secure Ideas services

Scope

This part covers services owned and operated by Secure Ideas, LLC, including:

  • www.secureideas.com
  • clientportal.secureideas.com
  • professionallyevil.com

Vulnerabilities in third-party software or services we use (for example, our website hosting platform) should be reported to that third party. If you are unsure who owns an issue, report it to us and we will help route it.

How to report

Email security@secureideas.com. Please include:

  • the affected URL or service;
  • steps to reproduce; and
  • the potential impact.

You may report anonymously. If you want credit, or want a CVE ID considered, include a way to reach you.

We will acknowledge receipt of your report within three (3) business days. Verification and remediation timelines are set case by case and coordinated with the reporter.

Safe harbor

Good-faith research that follows this policy is authorized, and we will not pursue legal action against researchers who comply with it.

Guidelines

  • Notify us as soon as possible after discovery.
  • Avoid privacy violations, accessing data that isn’t yours, and modifying or destroying data.
  • Use exploits only to the extent needed to confirm a vulnerability.
  • Do not access client data. If you encounter client data, stop and report it immediately.
  • Give us reasonable time to fix the issue before public disclosure.
  • Do not submit a high volume of low-quality reports.

Not authorized

  • Denial of service testing
  • Physical testing or social engineering
  • High-volume automated scanning that degrades our services

Bug bounty

Secure Ideas does not run a bug bounty program. In exceptional cases where a vulnerability poses an imminent threat to client data, we may offer a discretionary reward. Secure Ideas alone decides whether a reward applies.

Rewards are not available for:

  • vulnerabilities already known to Secure Ideas and being addressed;
  • low-impact or informational findings, including best-practice observations that pose no security risk; or
  • vulnerabilities in third-party software or services, which should be reported to the third party.

Part B: Vulnerabilities discovered by Secure Ideas research

This part covers vulnerabilities our research team finds in third-party software and services outside of client engagements.

Coordination

When our research team finds a vulnerability, we will:

  1. Notify the vendor or maintainer through their published security contact. If the vendor is a CNA, we follow their disclosure process.
  2. Share enough technical detail for the vendor to reproduce and fix the issue.
  3. Work with the vendor on a fix and a coordinated public disclosure date.

Disclosure timeline

Our default is to disclose publicly 90 days after first notifying the vendor, or when a fix is released, whichever comes first.

  • We may extend this deadline when a vendor is actively working on a fix and communicating with us.
  • We may shorten it if the vulnerability is being actively exploited.
  • If a vendor does not respond after [3] attempts over [30] days, we may escalate. Options include the vendor’s CNA or our Root, CERT/CC, or CISA (for industrial control systems and operational technology).

CVE assignment

We assign CVE IDs only to vulnerabilities within our CNA scope. If the affected product is within another CNA’s scope, we request the CVE ID from that CNA and do not assign it ourselves.

We publish the CVE Record when the advisory is published, and in all cases within [24 hours] of public disclosure.

Part C: Vulnerabilities found during client engagements

Vulnerabilities identified during paid services are governed by the client’s contract. These services include penetration testing, assessments, and PETaaS®.

  • Findings in client-owned systems and software are confidential client information. Secure Ideas will not publicly disclose them or assign CVE IDs to them.
  • Findings in third-party products discovered during an engagement belong to the client to report. Secure Ideas encourages clients to report these to the affected vendor and can help with that coordination.
  • Secure Ideas will disclose or assign a CVE ID for an engagement finding only with the client’s written authorization. In that case, the finding is handled under Part B.

Part D: CVE Record disputes and corrections

To dispute or request a correction to a CVE Record that Secure Ideas published, email security@secureideas.com with “CVE Dispute” in the subject line.

We will:

  • acknowledge disputes within 3 calendar days;
  • respond with a decision, or with notice of an extension, within 5 days of acknowledgment; and
  • escalate unresolved disputes to our Root as described in the CVE Program dispute policy.

Policy review

We review this policy at least annually. The “Last updated” date at the top reflects the most recent review.

This website uses cookies

We use cookies to personalize content, provide social media features, and analyze our traffic. We also share information about your use of our site with our analytics partners. You can change your preferences at any time. For more information, please see our Privacy Policy