The standards we hold,
and exactly what each one covers.
Your tenant. Your region.
Your data, your perimeter.
KnowledgeLake operates the application. You control the storage perimeter. Documents live in your Azure tenant — not in ours.
Native Entra ID.
Native to your identity perimeter.
Entra ID native
SSO, conditional access, MFA. Mapped to your Entra groups. No parallel user store.
Role-based access controls
Roles per document type, per tenant. Operator vs reviewer vs auditor vs admin scopes.
Customer-controlled break-glass
Break-glass procedures defined and executed by you. We have no vendor backdoor.
SIEM integration
Native Sentinel integration. Splunk and other SIEMs via syslog. Every audit event streams to your perimeter.
Conditional access
Honor your Entra conditional access policies. Risky sign-in flags propagate to KnowledgeLake session policies.
Session and token policies
Session length, token expiration, and re-authentication policies configurable per your standards.
Every action signed.
Every action replayable.
We use AI where it earns its place.
We don't replace operational judgment.
Most AI vendors will tell you what their AI can do. We will also tell you what it doesn't do — and where the line between automated and human-decided sits.
Policy-driven confidence thresholds
Every routing decision is policy-driven. Thresholds are customer-controlled, not vendor-tuned. You see exactly what the policy is, and you change it.
Human-in-the-loop required at policy thresholds
Below the threshold, the document lands with an operator. Period. We do not "improve" the policy to clear documents the policy said should not auto-clear.
No training on customer documents
Customer documents are not used to train models. Operational telemetry (de-identified) is used to improve the platform.
Per-document-type model isolation
Which model serves which document type is policy-controlled. No accidental cross-pollination across regulated document types.
Confidence drift detection
Confidence distributions are monitored. When the distribution drifts, you are alerted before the policy needs an update.
Reasoning explained per extraction
For reasoning-based extractions, the reasoning steps are visible in the audit chain. No black-box outputs in regulated workflows.