Responsible Disclosure Policy
Responsible Disclosure Policy
Responsible Disclosure Policy
Responsible Disclosure Policy
Actively is committed to ensuring the security of our customers and their data. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
If you’ve found a potential security issue in our products or services, notify us at security@actively.ai based on the guidelines on this page. If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized and look forward to working with you to resolve the issue promptly.
Guidelines:
• Notify us as soon as possible after you discover a real or potential security issue.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
• Only use exploits to the extent necessary to confirm a vulnerability’s presence.
• Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.Do not submit a high volume of low-quality reports.
• Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
• Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
Reporting:
We ask that your reports:
• Describe the location the vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
• Be in English, if possible.
Actively is committed to ensuring the security of our customers and their data. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
If you’ve found a potential security issue in our products or services, notify us at security@actively.ai based on the guidelines on this page. If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized and look forward to working with you to resolve the issue promptly.
Guidelines:
• Notify us as soon as possible after you discover a real or potential security issue.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
• Only use exploits to the extent necessary to confirm a vulnerability’s presence.
• Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.Do not submit a high volume of low-quality reports.
• Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
• Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
Reporting:
We ask that your reports:
• Describe the location the vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
• Be in English, if possible.
Actively is committed to ensuring the security of our customers and their data. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
If you’ve found a potential security issue in our products or services, notify us at security@actively.ai based on the guidelines on this page. If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized and look forward to working with you to resolve the issue promptly.
Guidelines:
• Notify us as soon as possible after you discover a real or potential security issue.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
• Only use exploits to the extent necessary to confirm a vulnerability’s presence.
• Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.Do not submit a high volume of low-quality reports.
• Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
• Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
Reporting:
We ask that your reports:
• Describe the location the vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
• Be in English, if possible.
Actively is committed to ensuring the security of our customers and their data. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
If you’ve found a potential security issue in our products or services, notify us at security@actively.ai based on the guidelines on this page. If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized and look forward to working with you to resolve the issue promptly.
Guidelines:
• Notify us as soon as possible after you discover a real or potential security issue.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
• Only use exploits to the extent necessary to confirm a vulnerability’s presence.
• Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.Do not submit a high volume of low-quality reports.
• Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
• Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
Reporting:
We ask that your reports:
• Describe the location the vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
• Be in English, if possible.
ACTIVELY AI
Building the future of outbound with AI + automation.
Copyright © 2024 Taurus Labs, Inc. All Rights Reserved
ACTIVELY AI
Building the future of outbound with AI + automation.
Copyright © 2024 Taurus Labs, Inc. All Rights Reserved
ACTIVELY AI
Building the future of outbound with AI + automation.
Copyright © 2024 Taurus Labs, Inc. All Rights Reserved
ACTIVELY AI
Building the future of outbound with AI + automation.
Copyright © 2024 Taurus Labs, Inc. All Rights Reserved