EFUPAL · Efupal LLC
Sovereign deployment guide
Technical acceptance criteria for dedicated institutional environments.
Configuration and domain provisioning
Select Kernel, Framework, Sector, Jurisdiction, and Topology. Five ordered catalog tokens form one DNS label under efupal.com. A URL preview is not a provisioned tenant. Wildcard DNS, TLS, host routing, organization ownership, and deployment approval must be verified before activation; the hostname alone never grants data access.
Post-quantum primitives
ML-KEM-1024 (FIPS 203) establishes shared secrets; it does not sign documents or encrypt application data by itself. ML-DSA-87 (FIPS 204) signs offline envelopes. SLH-DSA (FIPS 205) provides a hash-based signature option with different signature size and performance tradeoffs. Algorithm support does not establish FIPS module validation or confirm deployed transport security.
Offline license verification
Verify the exact UTF-8 signedPayload bytes with ML-DSA-87, using an independently provisioned and pinned Efupal LLC public key. Reject expired tokens, mismatched subjects, unapproved issuers, or invalid signatures. The visitor sandbox creates self-signed previews without deployment rights; its embedded public key must never be treated as a trusted production authority.
Zero-egress acceptance: 0 external calls
A zero-egress installation must bundle fonts, model weights, runtime libraries, and verification keys locally; disable analytics, cloud authentication, billing, and webhook dispatch; enforce deny-all outbound network rules. Capture DNS and network traffic across startup, inference, key rotation, audit export, and license verification. Accept only 0 external calls. The hosted efupal.com website uses external services and is not an air-gapped installation.
Regulatory mapping
EU AI Act: document system classification, human oversight, risk controls, and evidence. NIS2: map incident handling and supply-chain controls. HIPAA: establish applicable covered-entity obligations, access controls, and contractual safeguards. FedRAMP: requires a separate authorization process and defined boundary. DORA: map ICT risk, resilience tests, incident reporting, and supplier oversight. A catalog badge indicates mapping scope, not certification or legal compliance.
Audit and operations
Export records in sequence order and independently recompute SHA-256 chain links using the documented canonical record format. Protect signing keys outside browser code and public-key metadata stores. Test backup recovery, tenant isolation, revocation distribution, and fail-closed entitlement checks before production acceptance.