Skip to main content
Security & Trust

Trust is part of the operating model, not a badge added at the end.

ABEIF is designed so identity, authority, evidence, operational resilience, uncertainty and decision accountability remain explicit throughout the intelligence lifecycle.

CURRENT TRUST POSTURE

Operational controls you can verify without exposing internal implementation.

Account assurance

Password · Google · Microsoft · TOTP MFA

Scoped isolation

Organization + governed service / assessment scope

Backup & retention

Encrypted recurring backups · 30 daily · 180-day weekly coverage

Recovery evidence

Controlled restore exercised · 22m 12s measured · RPO target ≤24h

Monitoring & incidents

Production monitoring operational · incident drill exercised

Governed releases

Compatibility · runtime · type-safety · production-build validation

Operational measurements below are evidence of the current operating model. They are not contractual SLA commitments.

Governed identity and authorization

Identity does not automatically grant Organization, Assessment or executive-workspace authority. Protected experiences preserve governed authorization boundaries rather than relying on browser state alone.

Identity and account security

ABEIF supports password, Google and Microsoft account sign-in through the canonical Identity Service, with TOTP multi-factor authentication for account assurance.

Organization-controlled MFA

An Organization may keep MFA optional, require it for Owners and Admins, or require it for all active members. Account assurance remains separate from Organization membership and service authority.

Verified Organization and domain trust

Organization Verification and Corporate Domain Verification provide separate trust controls. Verification strengthens organizational identity and continuity without turning a domain or successful sign-in into access authority.

Organization and assessment isolation

Protected report and runtime access is isolated by the canonical Organization and assessment-session scope. Stable external identifiers do not replace that composite authorization boundary.

Evidence, lineage and explainability

Claims remain traceable to governed sources, declared authority and lineage. Evidence, confidence, uncertainty and contradictions remain visible rather than being hidden behind a single score.

Human accountability and AI boundaries

AI may assist interpretation, extraction and navigation. It does not replace accountable human decisions or become final Truth authority.

Backup, recovery and lifecycle controls

ABEIF operates recurring independent encrypted backups with defined retention and tested restoration procedures. Current operational retention is 30 daily recovery points and 180 days of weekly recovery coverage. Customer deletion and offboarding remain governed, request-driven processes rather than broad destructive self-service actions.

Recovery evidence

The latest controlled restore exercise measured 22 minutes 12 seconds. The current operational recovery-point target is 24 hours or less. These are current operating measurements and targets, not contractual SLA commitments; customer-specific obligations are governed by the applicable signed agreement.

Monitoring and incident response

Production monitoring and incident-response procedures are operational and have been exercised through a controlled incident drill without intentionally degrading or mutating Production customer services.

Governed production changes

Production releases pass automated compatibility, Truth/runtime, type-safety and production-build validation before promotion. Material platform changes remain versioned and traceable through the governed development process.

Evidence before badges

ABEIF does not present ISO, SOC or other certification or compliance attestations as achieved until they have been formally completed and evidenced. Enterprise identity federation / SSO remains roadmap rather than a current public capability.

Enterprise security & due diligence

Organizations evaluating ABEIF for controlled production use can request additional security, architecture, operational-resilience and data-governance information through the Enterprise channel. Detailed implementation internals remain protected rather than published as marketing material.

Public operational evidence summarizes the control outcome, not internal topology, credentials, provider secrets or implementation details.
Back to Product Overview