Back to home
Security

We designed the platform to be trustworthy.

Security is not a feature list. SentriScope is built with security by design: tenant isolation, governed architecture, auditability, and explainable decision support, so organizations can evaluate trust through architecture, not buzzwords.

Explore tenant architecture View documentation Contact
Security by design

Architecture before controls

Controls matter. Architecture decides whether those controls can be trusted. SentriScope prioritizes structural guarantees over decorative security language.

Governed behavior over opportunistic automation

Governance comes before automation. SentriScope favors deterministic, explainable behavior: least privilege by default, defense in depth across tenant boundaries, and explicit denial when context is missing or unauthorized. Security posture is designed into tenant scope and auditability, not bolted on as a marketing layer.

Tenant architecture
  • Architecture and isolation before feature-level controls
  • Governance before automation
  • Deterministic, explainable decision support
  • Least privilege within tenant scope
  • Defense in depth: multiple independent boundaries
Isolation architecture

Tenant isolation, fail-closed by design

Trust starts with separation. Each tenant workspace is isolated at the data and API boundary, and unauthorized or missing context is denied by default.

  1. 1 Tenant data boundary Tenant data is scoped at the data and API layer. No cross-tenant access by design.
  2. 2 Access within the tenant Role-based access controls who can view, change, and govern risk decisions inside your workspace.
  3. 3 Isolation modes Shared or dedicated database modes are available to match organizational isolation requirements.
  4. 4 Fail-closed authorization Missing or unauthorized context results in denial, not a permissive fallback.

Fail-closed behavior

Unauthorized or unrecognized access is denied by default. There is no silent fallback when context is missing or unauthorized.

Tenant data isolation

Tenant data is isolated by design at the data and API boundary. Shared or dedicated database modes are available to match organizational isolation requirements, with no cross-tenant access by design.

See tenant architecture

Governance

Boundaries, roles, and accountable decisions

Enterprise trust requires clear who-can-do-what boundaries, and a durable record of why decisions changed.

RBAC with least privilege inside your tenant

Role-based access control enforces least privilege within your tenant workspace. Decision overrides require governance records (reason, approver, and expiry) so risk scoring changes remain accountable.

Tenant trust architecture
  • RBAC with least-privilege defaults
  • Tenant boundaries on data and operations
  • Clear role boundaries inside the workspace
  • Audit lineage for sensitive and governed actions
  • Provenance on canonical records
  • Append-only governance records for overrides and sensitive actions
Audit architecture

Evidence that can be verified over time

Sensitive actions are recorded in a tamper-evident audit trail. Cryptographic hash chaining links each entry to the previous one, so post-hoc tampering is detectable and chain integrity can be independently verified.

Tamper-evident audit

Hash-chained audit logging for sensitive actions, designed so alterations after the fact leave a detectable break in the chain.

Decision lineage

Risk decisions and governed overrides retain lineage: what changed, who approved it, why, and when it expires.

Historical evidence

Audit history supports retrospective review of security-relevant operations without exposing raw chain values publicly.

Traceability

Connector, identity, LLM, and governance operations are designed to leave an auditable trail for analysts and evaluators.

Export under access control

Audit evidence export is available to authorized roles within tenant boundaries. Export is an access-controlled capability, not an open public dump of audit data.

Retention posture

The platform is designed to support organizational retention and governance programs. Specific retention schedules and purge behavior are deployment- and agreement-dependent, not presented as a universal compliance outcome.

Guardrailed AI

Decision support, not autonomous security operations

When enabled, LLM assistance is bounded. It supports analysts; it does not run the security program.

Read-only, schema-grounded, tenant-scoped assistance

LLM workflows are read-only, schema-grounded, and explainable. They operate within tenant scope and are plan-gated when configured. Credentials do not enter prompt context. Output is filtered and SQL validation enforces read-only query behavior before execution. The model assists investigation and understanding. It does not silently decide or act.

Product capabilities & AI posture
  • Read-only LLM workflows
  • Schema-grounded queries with SQL validation
  • Explainable decision support for analysts
  • Tenant-scoped and plan-gated when enabled
  • No autonomous remediation
  • No autonomous security operations
  • No hidden decision making
Operational trust

Controls that support day-to-day assurance

Beyond isolation and audit architecture, operational controls reinforce identity, access, privacy, and resilience.

  • Identity
    MFA & step-up authentication TOTP-based multi-factor authentication for tenant users, with step-up authentication for sensitive operations.
    Scoped tenant identities Identity context respects tenant boundaries, with no shared identity plane across tenants.
  • Access control
    Least privilege & RBAC Role-based access with clear tenant scope. Least privilege enforced as the default posture.
    Fail-closed authorization Missing or unauthorized context results in denial, not a permissive fallback.
  • Audit
    Tamper-evident hash chain Cryptographic linking of audit entries for sensitive actions, with independent integrity verification.
    Decision governance records Overrides require reason, approver, and expiry, appended to the tamper-evident audit chain.
  • Observability
    Operational visibility Connector health and operational state support analysts without exposing tenant secrets publicly.
    Security-relevant event coverage Audit coverage spans identity, connector, governance, and LLM-related operations.
  • Connector governance
    Governed ingestion Connector sessions are tenant-scoped, audited, and designed for safe synchronization, not passive pipes.
    Encrypted credential references Connector credentials are stored as encrypted references, never in plaintext. Encryption in transit and at rest.
  • Privacy
    Tenant data boundaries Tenant data stays within tenant scope. Marketing and documentation surfaces do not expose tenant identifiers or operational secrets.
    No credentials in LLM context Guardrailed AI workflows are designed so credentials never enter prompt context.
  • Workspace resilience
    Defense in depth Tenant isolation, RBAC, and auditability form independent layers, not a single control point.
    No autonomous remediation The platform does not autonomously remediate findings or execute unsupervised security operations.
Compliance positioning

Engineered to support enterprise governance

SentriScope is designed to support enterprise governance programs: isolation, auditability, access control, and decision lineage that help organizations meet their own assurance requirements.

Support for governance, not certification theater

The platform helps organizations demonstrate control design through architecture: tenant isolation, tamper-evident audit, RBAC boundaries, and governed AI. We do not claim SOC 2, ISO, FedRAMP, or other certifications on this page. Compliance outcomes depend on your deployment, policies, and independent assessment. SentriScope provides architectural foundations that support those programs.

  • Designed to support enterprise governance
  • Helps organizations evidence control design
  • No automatic compliance claims
  • No certification badges presented as attained
Documentation

Published guidance, not an internal dump

Public documentation is curated. Architecture explanations and Knowledge Hub articles are published through a certification workflow. Internal engineering docs are not automatically exposed.

  1. 1 Public documentation The documentation hub lists certified, publishable articles only.
  2. 2 Architecture Conceptual architecture guidance for evaluators, without implementation secrets.
  3. 3 Knowledge Hub Published articles grouped for learning: foundation through security depth.
  4. 4 Published guidance Content that has passed publication review, not raw internal repositories.

Open documentation hub

Evaluate trust through architecture

Review tenant architecture, ask about isolation and audit requirements, or talk to our team about enterprise governance.

Tenant architecture Contact