Responsible Disclosure Policy
Data security is a top priority for DecisionLogic, and DecisionLogic believes that working with skilled security researchers can identify weaknesses in any technology.
If you believe you’ve found a security vulnerability in DecisionLogic’s service, please notify us; we will work with you to resolve the issue promptly.
- If you believe you’ve discovered a potential vulnerability, please let us know by emailing us at email@example.com. We will acknowledge your email promptly
- Please provide us with a reasonable amount of time to resolve the issue before disclosing it to the public or a third party
- Please make a good faith effort to avoid violating privacy, destroying data, or interrupting or degrading the DecisionLogic service. Please only interact with accounts you own or for which you have explicit permission from the account holder
While researching, we’d like you to refrain from:
- Distributed Denial of Service (DDoS)
- Social engineering or phishing of DecisionLogic employees or contractors
- Any attacks against DecisionLogic’s physical property or data centers
Thank you for helping to keep DecisionLogic and our users safe!
We may revise these guidelines from time to time. The most current version of the guidelines will be available at www.decisionlogic.com/security/.
DecisionLogic is always open to feedback, questions, and suggestions. If you would like to talk to us, please feel free to email us at firstname.lastname@example.org.
To submit a vulnerability report to DecisionLogic’s Product Security Team, email email@example.com.
Preference, Prioritization, and Acceptance Criteria
We will use the criteria from the next sections to prioritize and triage submissions.
What we would like to see from you:
- Well-written reports in English will have a higher probability of resolution
- Reports that include proof-of-concept code equip us to better triage
- Reports that include only crash dumps or other automated tool output may receive lower priority
- Reports that include products not on the initial scope list may receive lower priority
- Please include how you found the bug, the impact, and any potential remediation
- Please include any plans or intentions for public disclosure