Security

Vulnerability disclosure

If you find a security issue in stsmedia.co or the Command Center, tell us privately so we can fix it before it is used against clients or visitors.

This page describes how STS Media intends to operate. It is not legal advice, not a certified audit, and not an official policy until a qualified professional reviews it.

In scope

  • stsmedia.co public pages and forms
  • Command Center authentication, session handling, and server actions once Auth is connected
  • Misconfigured headers, cookie flags, or access control that exposes another person’s data

Out of scope

  • Social engineering of staff or clients
  • Physical attacks, DDoS, or spam against mailboxes
  • Findings that require a compromised device, jailbreak, or malware on the victim
  • Issues in third-party products (Calendly, Stripe, Google, Supabase platform bugs) — report those to the vendor, and you may copy us if our configuration is involved
  • Missing best-practice headers that do not create a practical exploit, unless they weaken an existing control

Rules for good-faith research

  • Act in good faith. Do not access, modify, or delete another person’s data.
  • Do not run exploits against production that degrade service. A proof that a control is missing is enough.
  • Do not include live credentials, client files, or exploit payloads that could be reused against others. Describe the issue and the affected URL or control.
  • Give us a reasonable window to fix before public disclosure. We will acknowledge reports we can reproduce.
  • There is no bug bounty and no paid retainer for reports at this time. We will thank researchers we can verify, and we will list a first name or handle on the acknowledgments page if you want that.

What to include

  • The URL or Command Center screen
  • What you expected versus what happened
  • Browser or tool, and whether you were signed in
  • Impact: could someone read, change, or delete data they should not?
  • A contact email if you want a reply

Machine-readable contact: /.well-known/security.txt. Acknowledgments: /security/acknowledgments.

Describe the URL, what you expected, and the impact. Do not paste passwords, client files, or reusable exploit code.

Back to security practices

Essential cookies only: security, sign-in, and appearance. See the cookie notice and your rights.