Skip to content

DocsOrganizations

OpenPulse

Organizations

Private access

A private network on WireGuard: policy as a document, just-in-time access and short-lived SSH certificates.

Built Private access gives your organization its own encrypted network. Devices and servers join through OpenPulse sign-in, nothing is reachable until a rule allows it, and sensitive access opens for a set time after a second person approves. It opens by request, one organization at a time, and we set up your network and first policy with you. Request access to start.

Who can do what#

RoleIn Private access
MemberReads devices, resources and the policy, requests access, sees their own requests and certificates, binds and removes their own devices.
AdminEverything a member can, and manages resources, applies the policy, decides requests, ends grants, removes any device and reads the access record.
OwnerEverything an admin can, and links the organization to its network.

Devices and servers#

People#

A person brings a device onto the network by signing in with OpenPulse. Only an active member of your organization is admitted. A person can also bind a device by proving a key it holds, which lets a rule name bound devices.

Servers and internal apps#

Add a resource under Private access → Resources. Its name is 2 to 32 lowercase letters, digits and dashes. The Console shows a setup key and the command that joins the server. The key works once, expires within the hour and is shown once.

The policy#

One document per organization, in YAML or JSON, says who reaches what. A new network allows nothing. Under Private access → Policy the Console shows what a document changes before you apply it, and keeps every applied version with who applied it and when.

policy.yaml
version: 1rules:  - name: dispatch-to-tours    from: [group:dispatch]    to: [resource:tours-app]    ports: [443]    protocol: tcpjit:  - resource: db-prod    max_minutes: 120    approvers: [group:sre]    ssh_principals: [ops]

Rules#

FieldValue
name2 to 48 lowercase letters, digits and dashes, unique in the document.
fromgroup:<name>, person:<did> or bound:<group>.
toresource:<name>, group:<name>, bound:<group> or person:<did>.
portsOptional list of ports. Leave it out for all ports. Ports need tcp or udp.
protocoltcp, udp, icmp or all. The default is tcp with ports and all without.
bidirectionalWhether the path also opens in the other direction. The default is false.

Groups are the groups of your organization, so a rule can name what your provider pushes over SCIM. A document with an unknown key, group or resource is refused, with the path of each error.

Just-in-time access#

A resource listed under jit is reached through a request.

FieldValue
resourceThe resource this entry covers.
max_minutesThe longest grant, 5 to 240 minutes. The default is 60.
approversGroups whose members may approve. Admins and the owner always may.
ssh_principalsThe Unix accounts a granted SSH certificate may name.
self_approveOptional. Lets the requester approve their own request, still with their own passkey, for an organization with one person who can approve.
  1. Ask

    The person picks the resource and gives a reason and a duration of at least 5 minutes.
  2. Approve

    A second person confirms with a fresh passkey step. Without self_approve, the requester cannot approve their own request.
  3. Reach

    The path opens for the set time. An admin or the requester can end it early.
  4. End

    The grant closes on its own within about 15 seconds of its end, and the request stays listed.

SSH certificates#

A granted request that carries an SSH public key gets a certificate signed by your organization's certificate authority. It names the accounts the policy allows and ends with the grant, four hours at most. To trust the authority on a server, copy its key from Private access → SSH certificates:

On the server
# Save the key shown in the Console as /etc/ssh/openpulse_user_ca.pub# Add this line to /etc/ssh/sshd_config, then reload sshdTrustedUserCAKeys /etc/ssh/openpulse_user_ca.pub

Offboarding#

When a person leaves your organization, their devices and network user are removed and their grants and certificates are revoked. A check also runs every five minutes and removes anyone who is no longer an active member. If they sign in again, they are rejected.

The access record#

Private access → Access record lists every join, policy change, request, approval and certificate for your organization. Each entry is hashed over the one before it, so a removed or changed entry breaks the chain. Admins and the owner can read it. It is separate from your organization's audit log.