Sigvex
Security2 min read

Security at Sigvex

Public security page covering application security, infrastructure, data protection, monitoring, third-party, and disclosure.

Open Security at SigvexAll guides
securityplatformpolicy

What it is

A public page describing how Sigvex — the platform — is secured. Sections: Our Commitment, Application Security (Secure Development, Input Validation and Sandboxing, Browser-Based Fuzzing), Infrastructure Security (Hosting and Network, Access Controls), Data Protection (Encryption, Data Handling), Monitoring and Incident Response (Monitoring, Incident Response), Third-Party Security, Responsible Disclosure, Contact.

Why it exists

Customers evaluating Sigvex for procurement need a single public page describing platform security posture. This page is that document; it is also linked from the Footer so visitors can find it without signing in.

Who uses it

  • Procurement / legal reviewer — evaluates Sigvex against their security requirements.
  • Prospective customer — reads the page before signing up.

How to open it

  1. Footer → Security.
  2. Direct URL — /security.

Using the page

  1. Our Commitment — high-level statement of the security programme.
  2. Application Security — Secure Development, Input Validation and Sandboxing, Browser-Based Fuzzing.
  3. Infrastructure Security — Hosting and Network, Access Controls.
  4. Data Protection — Encryption, Data Handling.
  5. Monitoring and Incident Response — Monitoring, Incident Response.
  6. Third-Party Security — third-party controls and vendor review.
  7. Responsible Disclosure — links to /security/disclosure.
  8. Contact — where to reach the security team.

Inputs and outputs

Input Source Required
None.
Output Format Destination
Policy page HTML In-page render

Controls reference

  • Inline section links and external links where cited in the copy.

Limits

  • Public page; no sign-in required.
  • The page is read-only; feedback on security posture should go through the Responsible Disclosure flow.

Troubleshooting

Symptom or error Cause Action
Broken internal link Linked page has moved or been renamed Report via the Responsible Disclosure flow.