Technology Overview

A user with Administration permissions and the QuipaLoop software installed creates a Quipa Secure Loop for sharing services and other resources. When another user wishes to join the loop, they connect to the publicly accessible Secure Connection Broker (SCB) and request a connection to the loop by entering joining information including an invitation key. The loop receives the request and accepts the connection. The joining device and the loop establish a connection and the new device is joined into the loop. View Topologies

Any services or resources that are TCP/IP addressable by a device in a loop can be shared as services with other members of the loop and the QuipaLoop device can also act as a relay to make the services available on the local network. Services that have been shared into a loop can be accessed via a standard bookmark process or by launching directly from within QuipaLoop.

QuipaLoop Session Establishment

The QuipaLoop session is established in four stages which result in a secure connection between an end-user and the shared service. The session is established with no requirement for download and installation of ActiveX controls or modification of WindSock. There is no modification of proxy settings and no requirment for elevated (Administration) priveleges to run QuipaLoop, although some services such as SMB may require these priveleges to enable.

The four stages of the QuipaLoop session establishment are:

Stage 1: Secure End-point to Secure Connection Broker Session
Stage 2: End-point to End-point Session
Stage 3: Virtual Layer Session
Stage 4: Service Layer Session

Simplicity Key Features

NAT traversal technology
Maintains separation of subnets
No reliance on support of protocols such as IPSEC by the underlying network
No requirement for QuipaLoop on end-point devices
Simple and easy to set up

Agility Key Features

Multi-way sharing of services
No dependencies on fixed IP addresses for site networks
Service delivery from multiple points
Flexible network configuration
No third party access to service data

Security Key Features

Easy suspension of lost or stolen devices
No open inbound ports or port forwarding on HQ LAN
No third party access to service data
Internal secured server can be completely firewalled from internal company network
Node locked to physical USB device or credential locked to specific user
Industry standard encryption of all data

Joining Device	A Joining Device is a device that has had the QuipaLoop application software installed on it and is utilising the functionality provided by the SCB to become a member of a Quipa Secure Loop.
Secure Connection Broker	The SCB is the only required publically addressable service in the QuipaLoop system supplying several functions. The first is a licence management point that controls the creation of users, end-point devices and QuipaLoops. The second role is an authentication point to authenticate a user on an end-point device. The third role is as a connection assistant to help facilitate connections between end-point devices. The SCB does not store an IP address registry, rather it utilises Quipa’s proprietary dynamic “waiting room” process.
QuipaLoop Device	The QuipaLoop device is a device that has had the QuipaLoop application software installed on it. The QuipaLoop software allows this device to utilise the functionality provided by the SCB to become a member of a Quipa Secure Loop. Depending on the configuration of the end-point device it can act as a client, a server, a peer or any combination thereof.
Quipa Secure Loop	The Quipa Secure Loop is a virtual construction that is creating by establishing trust between a defined group of end-point devices. The Quipa Secure Loop is created via a Quipa proprietary invitation process initiated from the founding end-point device. It is used to define a perimeter into which services can be shared. It is possible to have multiple Quipa Secure Loops overlaid across a single device. Each Quipa Secure Loop maintains its own security and integrity.