Skip to content

Security: capiscio/capiscio-sdk-python

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
0.2.x
0.1.x

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to: [email protected]

Include:

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

What to Expect

  • Response time: Within 48 hours
  • Updates: Every 5 business days
  • Resolution: We aim to patch critical issues within 7 days

Disclosure Policy

  • Security issues are embargoed until a fix is released
  • Credit will be given to reporters (unless anonymity is requested)
  • CVE IDs will be assigned for confirmed vulnerabilities

Security Best Practices

When using the CapiscIO Python SDK:

  1. Keep dependencies updated

    pip install --upgrade capiscio-sdk
  2. Use signature verification

    config = SecurityConfig(
        downstream=DownstreamConfig(verify_signatures=True)
    )
  3. Enable rate limiting

    config = SecurityConfig(
        downstream=DownstreamConfig(enable_rate_limiting=True)
    )
  4. Use strict mode in production

    config = SecurityConfig.strict()
  5. Monitor logs for validation failures

    config = SecurityConfig(log_validation_failures=True)

Known Security Considerations

JWS Signature Verification

  • Uses cryptography library (audited, industry standard)
  • Supports RS256, RS384, RS512 algorithms
  • JWKS endpoints must use HTTPS

Rate Limiting

  • In-memory implementation (single-server only)
  • For distributed systems, use external rate limiter

Caching

  • Validation results cached with TTL
  • Cache keys include content hashes
  • Invalidation on configuration changes

Security Scanning

This project uses:

  • Dependabot for dependency updates
  • CodeQL for static analysis
  • Safety for Python dependency checking

Contact

For security concerns: [email protected]

There aren’t any published security advisories