> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/configuration/vulnerability-disclosure-policy.md).

# Vulnerability Disclosure Policy

How to report a security vulnerability in Silkline, what is in scope, and what to expect after you report

Silkline welcomes reports of security vulnerabilities from customers, suppliers, researchers, and anyone else who finds one. This policy explains how to report, which systems you may test, how to test safely, and how we respond.

**Version:** 1.1. **Last reviewed:** October 30, 2026.

## Report a vulnerability

Email <security@silkline.ai>. No account, form, or portal is required. Include:

* The affected URL, endpoint, or feature
* The type of vulnerability and its potential impact
* Step-by-step instructions to reproduce it, including any proof-of-concept code, requests, or screenshots
* Whether you want to be credited, and under what name

Write in English. Reports may be anonymous. Do not include another person's or organization's data in your report; describe what you could access instead.

Our contact details are also published in machine-readable form at <https://app.silkline.ai/.well-known/security.txt>.

## What to expect

| Step                      | Timeframe                                       |
| ------------------------- | ----------------------------------------------- |
| Acknowledge your report   | Within 3 business days                          |
| Confirm or rule out issue | Within 10 business days of acknowledgment       |
| Status updates            | At least every 30 days until the issue is fixed |
| Notify you of the fix     | When remediation is deployed                    |

We track every report to resolution under the same process as vulnerabilities we find ourselves, prioritized by severity and exploitability. We may contact you for more detail, and we will tell you if we decide a report is not a vulnerability and why.

## Scope

**In scope:**

* `app.silkline.ai`, including the buyer application and the Supplier Portal
* `api-gov.silkline.ai/v1/graphql`, the Silkline public API
* `auth.silkline.ai`, the Silkline sign-in service

**Out of scope:**

* Development and test environments, such as `dev-app-gov.silkline.ai`, `dev-api-gov.silkline.ai`, and `dev-auth-gov.silkline.ai`. Do not test them; report any vulnerability you notice there without further testing.
* `silkline.ai` and other marketing sites
* `docs.silkline.ai`
* Services operated by third parties, such as identity providers, email delivery, and customer-connected integrations. Report those to the vendor.
* Findings that only affect outdated or unsupported browsers
* Reports from automated scanners without a demonstrated, reproducible impact
* Missing security headers or cookie flags without a demonstrated impact

If you are unsure whether a system is in scope, email us before testing.

## Testing guidelines

You must:

* Test only against accounts and organizations you own or have explicit permission to test
* Stop testing and report immediately when you reach data that is not yours, and do not keep, copy, or share it
* Keep request volume low enough that you do not degrade the service for others

You must not:

* Run denial-of-service or load tests
* Use social engineering, phishing, or physical attacks against Silkline staff, customers, or suppliers
* Access, modify, or delete data belonging to other users or organizations
* Establish persistent access, move laterally, or pivot to other systems
* Use a vulnerability beyond the minimum needed to demonstrate it

## Authorization

If you make a good-faith effort to follow this policy, we consider your research authorized. We will work with you to understand and resolve the issue, and we will not pursue or support legal action against you for that research. If a third party brings legal action against you for activity that followed this policy, we will make it known that your actions were authorized.

This policy does not authorize testing of systems outside its scope, and it does not waive the rights of third parties.

## Disclosure

Give us a reasonable time to fix a vulnerability before you share it publicly. We ask for 90 days from your report, or less once a fix is deployed. We will coordinate the timing and content of any public disclosure with you.

When we publish information about a vulnerability, we share enough for customers to make risk-based decisions without details that would help someone exploit an unfixed system.

Silkline does not offer payment for reports. With your permission, we credit reporters of confirmed vulnerabilities.
