|
| 1 | +import {LovePage} from 'web/components/love-page' |
| 2 | +import {SEO} from 'web/components/SEO' |
| 3 | +import Link from 'next/link' |
| 4 | +import {Col} from 'web/components/layout/col' |
| 5 | +import {Row} from 'web/components/layout/row' |
| 6 | + |
| 7 | +export default function SecurityPage() { |
| 8 | + |
| 9 | + const mailto = `mailto:${email}?subject=${encodeURIComponent('Security vulnerability report')}` |
| 10 | + |
| 11 | + return ( |
| 12 | + <LovePage trackPageView={'security'} className={'relative p-2 sm:pt-0'}> |
| 13 | + <SEO |
| 14 | + title={`Security`} |
| 15 | + description={'Report security vulnerabilities to the Compass team'} |
| 16 | + url={`/security`} |
| 17 | + /> |
| 18 | + <Col className="max-w-3xl w-full mx-auto gap-6 custom-link"> |
| 19 | + <h1 className="text-3xl font-semibold">Security</h1> |
| 20 | + <p className="text-ink-700"> |
| 21 | + We take the security of our community seriously. If you believe you have found a vulnerability |
| 22 | + or security issue, please report it responsibly so we can investigate and fix it quickly. |
| 23 | + </p> |
| 24 | + |
| 25 | + <section className="space-y-2"> |
| 26 | + <h2 className="text-xl font-semibold">How to report</h2> |
| 27 | + <p> |
| 28 | + Please do not open public GitHub issues for security reports. Instead, contact us directly via one of the following: |
| 29 | + </p> |
| 30 | + <ul className="list-disc ml-6 space-y-1"> |
| 31 | + <li> |
| 32 | + Use the <Link href="/contact">contact form</Link> and choose the security category if available. |
| 33 | + </li> |
| 34 | + <li> |
| 35 | + Email us at <a href={mailto}>{email}</a>. |
| 36 | + </li> |
| 37 | + </ul> |
| 38 | + </section> |
| 39 | + |
| 40 | + <section className="space-y-2"> |
| 41 | + <h2 className="text-xl font-semibold">What to include</h2> |
| 42 | + <p> |
| 43 | + To help us triage and resolve the issue quickly, please include: |
| 44 | + </p> |
| 45 | + <ul className="list-disc ml-6 space-y-1"> |
| 46 | + <li>A clear description of the issue and potential impact</li> |
| 47 | + <li>Steps to reproduce (URLs, test accounts, exact requests/responses if applicable)</li> |
| 48 | + <li>Any screenshots, videos, or proof-of-concept code</li> |
| 49 | + <li>Your operating system, browser, and environment details</li> |
| 50 | + </ul> |
| 51 | + </section> |
| 52 | + |
| 53 | + <section className="space-y-2"> |
| 54 | + <h2 className="text-xl font-semibold">Our response</h2> |
| 55 | + <p> |
| 56 | + We aim to acknowledge new security reports within a few business days and will keep you updated as we investigate and remediate. |
| 57 | + Timeframes may vary based on severity and complexity. |
| 58 | + </p> |
| 59 | + </section> |
| 60 | + |
| 61 | + <section className="space-y-2"> |
| 62 | + <h2 className="text-xl font-semibold">Out of scope</h2> |
| 63 | + <p> |
| 64 | + Please avoid tests that could degrade service for other users (e.g., denial of service) or that involve accessing another user’s data without explicit permission. |
| 65 | + </p> |
| 66 | + </section> |
| 67 | + |
| 68 | + <section className="space-y-2"> |
| 69 | + <h2 className="text-xl font-semibold">Get in touch</h2> |
| 70 | + <Row className="flex-wrap gap-3"> |
| 71 | + <Link href="/contact" className="px-3 py-2 rounded-md border border-primary-600 text-ink-700 hover:bg-primary-50">Contact form</Link> |
| 72 | + <a href={mailto} className="px-3 py-2 rounded-md border border-primary-600 text-ink-700 hover:bg-primary-50">Email {email}</a> |
| 73 | + </Row> |
| 74 | + </section> |
| 75 | + </Col> |
| 76 | + </LovePage> |
| 77 | + ) |
| 78 | +} |
0 commit comments