Skip to content

Known Limitations

SecureObs is in private beta. This page lists limitations that may affect how a team evaluates the product or relies on it in CI.

Security And Trust

  • Public SOC 2, ISO 27001, HIPAA, FedRAMP, or similar compliance reports are not available yet.
  • Microsoft Entra ID is the only login provider today.
  • The role model is intentionally simple: Owner, Admin, and Member.
  • SCIM provisioning is not implemented.

Product Scope

  • SecureObs complements scanner-specific platforms; it is not a full replacement for products such as Snyk, Wiz, Semgrep AppSec Platform, or SonarQube.
  • CodeQL, SonarQube, Snyk, and OWASP ZAP are not active bundled scanner drivers in the current SecureObs scanner image.
  • Source-code deep links are still limited.
  • PR comments are tier-gated and run from customer CI credentials.

Notifications

  • Email notifications are disabled in private beta.
  • Outbound webhooks to Slack, Teams, PagerDuty, or similar systems are not implemented.

Scale And Reliability

  • SecureObs is not yet intended as the sole release-control system for production-critical deployments unless your team explicitly accepts private-beta availability and support expectations.
  • Very large finding lists are bounded by server-side limits and dashboard pagination is still evolving.