Boni Secure Access
Controlled enterprise releasePrivate application access that starts with identity and device trust.
Give authorized people access to named private applications only after identity, device, posture, and organization policy checks.
For: Organizations protecting private web, database, administration, and operational services.
What the product connects
One operating record across the workflow
Identity
OIDC sign-in, short-lived tokens, and required multi-factor authentication.
Device
A device-bound signing key proves that a valid identity token is being used from an enrolled endpoint.
Application
The gateway, not the endpoint, selects the named private destination allowed by policy.
How it works
Each connection must satisfy the whole policy.
Access is granted for a named application and a bounded session, not as permanent network membership.
- 01
Receive configuration
The organization supplies its identity provider, gateway, trust material, profile, and approved application name.
- 02
Sign in
The user completes Authorization Code with PKCE and the organization’s required MFA.
- 03
Bind the device
The endpoint proves possession of its non-exportable key and the gateway applies the organization’s enrollment policy.
- 04
Evaluate policy
Identity, application, access profile, device status, and available posture signals are checked server-side.
- 05
Open one secure path
The client establishes a hybrid-only TLS 1.3 connection to the gateway for the approved named application.
- 06
Audit and expire
The gateway records the decision and closes access on expiry, revocation, policy failure, or administrative action.
Product scope
What the product covers.
OIDC Authorization Code with PKCE and required MFA evidence.
Device-bound proof using non-exportable operating-system key custody.
TLS 1.3 with required hybrid X25519MLKEM768 key exchange.
Named-application allowlists instead of user-selected private destinations.
Standard and strict access profiles with server-owned posture policy.
Durable device enrollment and revocation with active-session cancellation.
Per-principal and global session limits with bounded reauthentication.
Per-app iOS Network Extension support for managed deployments.
Structured access, denial, session, and revocation audit events.
Start with a defined operating scope.
Each rollout names the workflow, participants, source records, owner, success measures, and the parts that remain in existing systems.
No access by download
The public app contains no customer credential, private network route, or universal access entitlement.
No full-device anonymity tunnel
On iOS, MDM chooses the managed apps that use the App Proxy. Unrelated traffic remains outside the product.
Claims follow evidence
Platform support, managed enforcement, and buyer acceptance are claimed only after the relevant signed-device and deployment checks pass.
Customer policy remains authoritative
Each rollout names its identity source, people, devices, applications, posture, retention, administrators, and revocation process.
Connected products
Use it alone, or connect the next part of the operation.
Secure Access privacy
Read the product-specific data handling notice for the iOS app and gateway.
Read the privacy noticeSecure Access support
Find configuration, sign-in, enrollment, and connection troubleshooting steps.
Open supportCybersecurity services
Combine the product with bounded architecture, assessment, and readiness work where needed.
See cybersecurity servicesQuestions
Common questions
Is this a consumer VPN?
No. Boni Secure Access opens only organization-approved named applications. It is not an anonymity service and does not route all personal device traffic.
Can downloading the app grant access?
No. A user still needs organization-issued configuration, a permitted identity, multi-factor authentication, an enrolled device key, and a matching access policy.
What does quantum-safe mean here?
The transport requires TLS 1.3 with a standardized hybrid X25519 plus ML-KEM key exchange. Existing identity, device, and application policy checks still apply; the phrase does not replace those controls.
How is the iPhone private key handled?
The iOS app creates a non-exportable P-256 signing key in the Secure Enclave. Only the public key is enrolled with the gateway.
Start with one bounded workflow