Skip to content

Security: Taurus-Ai-Corp/Comply.Q-Grid

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.1.x (Q-GRID Comply) Yes
1.0.x (OpenWork) Security fixes only
< 1.0 No

Reporting a Vulnerability

DO NOT open a public GitHub issue for security vulnerabilities.

Instead, please report vulnerabilities via one of these channels:

  1. Email: security@taurusai.io
  2. GitHub Security Advisory: Create a private advisory

What to Include

  • Description of the vulnerability
  • Steps to reproduce
  • Potential impact
  • Suggested fix (if any)

Response Timeline

Action Timeline
Acknowledgment Within 48 hours
Initial assessment Within 5 business days
Fix development Within 30 days for critical issues
Public disclosure After fix is deployed

Security Practices

This project follows security best practices:

  • Post-Quantum Cryptography: ML-DSA (FIPS 204) and ML-KEM (FIPS 203)
  • NIST PQC Compliance: Following NIST post-quantum migration guidelines
  • Dependency Scanning: Automated via Dependabot
  • Code Review: All changes require review via CODEOWNERS
  • Secret Management: No secrets in code; environment variables only
  • Audit Trails: Immutable blockchain-anchored audit logs via Hedera HCS

Scope

The following are in scope for security reports:

  • packages/core/ - SDK wrapper and authentication
  • packages/api/ - Backend API server
  • packages/mcp-servers/ - Hedera MCP tools
  • products/gridera/web/ - Q-GRID Comply SaaS application
  • products/gridera/src/crypto/ - Cryptographic implementations

Out of scope:

  • Third-party dependencies (report to upstream)
  • Social engineering attacks
  • Denial of service attacks

There aren’t any published security advisories