Rhombus use-case briefing

Analyst workspaces

Reach every analyst tool from a browser with one sign-in

Rhombus delivers analyst desktops, tools and team chat through a web browser, behind single sign-on the kit hosts itself. Analysts install nothing on their laptops and need no outside identity service, so the team can work offline.

Why it matters

  • Analysts work from any laptop with a browser, with no client software to install or accredit.
  • One kit-hosted sign-in and one directory control who reaches which tool, even with no outside network.
  • Throwaway workspaces start clean for each user, so one analyst's session does not carry into another's.

How it works on Rhombus

  • The application dashboard shows one tile per tool — container desktops, persistent workstations and links to kit web apps.
  • A kit-hosted identity provider signs users in once, against the kit's directory, for the dashboard, team chat, console and other supported tools.
  • Directory groups decide what each person can do, such as read-only analyst, administrator or workspace administrator.
  • Workspace images load from the kit's offline mirror. Team chat can receive alerts from the kit's security tools.

From deployment to results

  1. Deploy the mission package from the console to bring up the dashboard, identity and team chat services.
  2. Add analysts and assign their groups from the console's identity page.
  3. Run kit validation to confirm the directory, single sign-on and dashboard respond.
  4. Have analysts sign in once, launch their tools and follow alerts in team chat.

Defense and government use cases

  • Cyber protection team (CPT) and defensive cyber operations (DCO) missions at forward sites.
  • Hunt-forward teams that need consistent, role-based tool access on a disconnected network.
  • Training cohorts, where each student launches the same lab workspace in an isolated session.

Commercial use cases

  • Enterprise incident response teams that need analyst access without touching the affected network's identity systems.
  • Managed security service providers (MSSPs) that need a clean, auditable toolset for each engagement.
  • Critical infrastructure and operational technology (OT) sites where installing software on analyst endpoints is restricted.

Outcomes

  • Analysts reach their tools with a browser and one sign-in.
  • Access follows directory group membership and is managed from one console page.
  • Kit validation reports on the directory, single sign-on and dashboard before the team relies on them.

Considerations

  • Workspace licensing is part of your configuration; the edition and session count are confirmed during scoping.
  • Each kit runs one team chat platform, chosen when the kit is built.
  • Workspace images are staged on the kit in advance; heavy desktops need compute and storage sizing.

Integrated tools

  • Keycloak single sign-on
  • FreeIPA directory
  • Mattermost

Commercial products are licensed as part of your configuration. Product names are trademarks of their respective owners, and their use does not imply endorsement.

Request a briefingOverview PDF
Esc

↑↓ moveEnter openCtrl K anywhere