Security and access

Trust & Security

What Bhor OE does to keep each customer's data and access separate, controlled and recorded. Plain statements about what the product does.

Patent pending

Security

Seven things the platform does

Designed from the Top. Proven from the Bottom. The same idea applies to access and data: nothing is assumed, and everything is recorded.

A person’s path, from joining to leaving

Joining

Nobody is let in silently

A new person is queued as an access request. A human approves or denies it, with a reason.

Signing in

Single sign-on

Sign in through your identity provider over OIDC or SAML, with SCIM provisioning.

Acting

Sensitive actions ask twice

Publishing a policy, accepting a risk and approving an exception each require a fresh identity check, even inside a signed-in session.

Leaving

Clean exits

When someone leaves, their access and every open session end immediately.

Every step is recorded Every security event and governance change goes to a write-once audit trail.

Underneath

Your data stays separate

Every customer’s data is separated at the database level. An automated check fails the build if any table is missing that protection.

Conflicts are caught

The platform detects conflicting permissions, and records them with every other security event.

No default keys

The platform refuses to start with a known default key or password.

You claim your own workspace

Customers claim their own workspace and create their own administrator. We cannot plant an admin inside a customer’s organization.

Questions from your security team? Contact us or write to contact@bhortech.com.

Frameworks

SOC 2 and HIPAA

Bhor OE supports the frameworks your program is measured against.

SOC 2

Bhor OE helps you build and run a SOC 2 program: it maps your requirements to the Trust Services Criteria, drafts the policies, and collects the evidence an auditor asks for.

HIPAA

Bhor OE helps covered entities and business associates manage HIPAA Security Rule and Privacy Rule requirements, from policy to evidence.

Also supported: ISO 27001, NIST and GDPR.

Bhor Tech's own status

Bhor Tech's own SOC 2 readiness is in preparation.

Framework mappings are provided to support your program. Using Bhor OE does not by itself make an organization compliant with any standard.

See it in action

View the product as the people who use it

In a guided demo, a presenter signs in once and can view the product as any role in two organizations.

Meridian Health System

A fictional organization.

Atlas Financial Group

A fictional organization.

Six roles, one sign-in

Select a role to see what that person works with.

Executive sponsor

Sees the health of the organization, not just its audit status: policy coverage, procedure maturity, control effectiveness and audit readiness on one set of dashboards.

One thread, from mission to compliance

The demo follows a single chain end to end, so you can see how each step leads to the next.

Mission Requirements Policies Procedures Controls Evidence Monitoring Audit Compliance

A small peek

Meridian Health System Fictional data · illustration only
RequirementAccess to patient records is limited to the people who need it.
PolicyAccess Control Policy
ProcedureGrant access to a record, with a manager approval step.
ControlA manager approves before access is granted.
EvidenceThe approval record, kept current.

Ask a question

Employees ask in plain language and get an answer from approved policies and procedures.

Meridian Health System Fictional data · illustration only

Asked by an employee in Operations. The answer draws only on what that person is allowed to see.

Open a vendor request, attach the vendor's security questionnaire, and send it to the risk manager. The vendor cannot be used until the request is approved.

Source: Vendor Onboarding Procedure, step 2

Every organization, person and record in the demo is fictional. The full walkthrough is shown live, in a guided session.

How we start with you

Four steps, and you stay in control

Step1

A short conversation

We talk about your industry, your size and how you deploy.

Step2

We prepare your workspace

We show you the day-one program it would start with. You can correct it before anything is created.

Step3

You claim it

You open your private link and claim the workspace with your own identity, so you are the administrator. The link works once and expires.

Step4

You adopt what you need

You adopt the frameworks you need and start from the policy and control library.

Plain about limits

What we don’t claim

We describe what the product does, and say where it stops.

✕
Compliance on its own

Using Bhor OE does not by itself make an organization compliant with any standard.

✕
A verdict from your auditor

Framework mappings are provided to support your program. Whether you meet a standard is for you and your auditor to decide.

✕
Real customer data in the demo

The organizations and data in our demo are fictional.

✕
Proof we can’t stand behind

You won’t find invented testimonials or numbers on this site.

Why it is built this way

I built Bhor Tech to fix both at the source: procedures that make compliance follow, and a local LLM designed to answer from your own knowledge, inside your environment and within each person’s access.

Rabi Kulshi, Founder · Read the full story

Ready to see it on your own organization?

Tell us about your organization and we will walk you through the platform.