# Security Policy

- Link: https://www.agilicus.com/security-policy-html/
- Published: 2021-03-07T19:36:08+00:00
- Author: Don Bowman

# Security Policy

_Agilicus Incorporated_ is committed to ensuring the security of its products and
customers. 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.

This policy describes **what systems and types of research** are covered under this
policy, **how to send us** vulnerability reports, and **how long** we ask security
researchers to wait before publicly disclosing vulnerabilities.

We encourage you to contact us to report potential vulnerabilities in our systems.

## Authorisation

If you make a good faith effort to comply with this policy during your security 
research, we will consider your research to be authorised and we will work with 
you to understand and resolve the issue quickly, and Agilicus Incorporated will 
not recommend or pursue legal action related to your research. Should legal action
be initiated by a third party against you for activities that were conducted in 
accordance with this policy, we will make this authorisation known.

## Guidelines

Under this policy, “research” means activities in which you:

 * 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.
 * We do not accept reports about WordPress “**CVE-2017-5487**“. I assure you, you
   misunderstand what that CVE means, and, this is a public site, our authors are
   public on purpose.
 * We do not accept reports entitled “Temporary denial of service of Anti-virus 
   or privacy functionality” (see https://hackerone.com/reports/1322243) for a sample.

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.

## Test methods

The following test methods are not authorised:

 * 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

## Scope

This policy applies to all products and services offered by Agilicus Incorporated.
This includes *.agilicus.com, *.agilicus.ca as domains, and any source code released
at [https://github.com/Agilicus](https://github.com/Agilicus).

Any service not explicitly listed above, including but not limited to services provided
by customers of Agilicus, are excluded from scope and are not authorised for testing.

Vulnerabilities found in systems from our vendors fall outside this policy’s scope
and should be reported directly to the vendor according to their disclosure policy(
if any).

If you are not sure if a system is in scope, contact us soc@agilicus.com before 
starting your research.

## Reporting a Vulnerability

Information submitted under this policy will be used for defensive purposes only–
to mitigate or remediate vulnerabilities. If your findings include newly discovered
vulnerabilities that affect all users of a product or service and not solely Agilicus
Incorporated, we may share your report others who may be afected for coordinated
vulnerability disclosure process. We will not share your name or contact information
without express permission.

We accept reports via email to soc@agilicus.com, as documented in our [security.txt](https://www.agilicus.com/.well-known/security.txt).
You may choose to encrypt email via PGP via our public key [6F6B44A214A72FE516DA11A91C87BFCF5A5C2E7E](https://keys.openpgp.org/vks/v1/by-fingerprint/6F6B44A214A72FE516DA11A91C87BFCF5A5C2E7E).

## What we would like to see from you

In order to help us triage and prioritise submissions, we recommend 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 (proof of concept
   scripts, screenshots are helpful)
 * Indicate the version(s), time, date, tested against
 * Be in English if possible

## What you can expect from us

When you choose to share contact information with us, wecommit to coordinating with
you as openly and quickly as possible

 * within 3 business days we will acknowledge receipt
 * to the best of our ability confirm the existence of the vulnerability and be 
   as transparent as possible about what steps we are taking during the remediation
   process
 * maintain an open dialog to discuss issues

If you have any questions or comments, please email soc@agilicus.com