Solution · By Stack

Remote & Privileged Sessions

Remote access is where credentials leak and accountability disappears. Autointelli brokers SSH and RDP sessions from the browser with the password injected server-side, grants access only when approved, checks SSH commands against policy, and records the session. For everyday desktop support, remote control asks the user first.

  • Connectfrom the browser
  • Approveand time-box
  • Recordevery session
Follow a session from request to recordPick a scenario · sample data
  1. RequestA reason, a duration and an optional ticket reference
  2. ApprovalApprovers decide, and nobody approves their own request
  3. ConnectionBrowser to gateway to target, credential injected server-side
  4. Live controlCommand policy, live monitoring and terminate
  5. Record and reviewEncrypted recordings and a hash-chained audit trail
Illustrative example. Rules and settings are configured per environment.

The problem

Remote access outruns control

The easier it is to connect, the harder it is to say who did what.

01

Shared

Admins connect with passwords they can copy, share and keep. Nobody rotates them.

02

Standing

Remote access is left open long after the job it was for.

03

Unwatched

When something goes wrong, there is no recording and no record of the commands.

Where it goes wrong

Six gaps, and how each one is closed

Passwords that leave the vault

How it goes wrongA password shown to a user is a password they can keep.

Closed withThe gateway injects the credential on the server and never sends it to the browser, and the vault keeps versioned, encrypted copies.

Access that never expires

How it goes wrongA grant made for one job stays open.

Closed withJust-in-time grants with a reason, approvers and an expiry, re-checked at launch, with live sessions ended when a grant expires or is revoked.

Sessions from anywhere, any time

How it goes wrongAny network and any hour can reach a server.

Closed withSession policy limits protocols, source networks, time windows and concurrent sessions, and can show an access banner.

Commands nobody checked

How it goes wrongA destructive command runs on a production host.

Closed withSSH command policy with ordered rules: allow, warn, deny or terminate, with every command recorded.

No recording

How it goes wrongAfter an incident there is nothing to replay.

Closed withEncrypted session recordings, played back only through a fresh authorisation, with a SHA-256 integrity value.

Support tools that don't ask

How it goes wrongRemote control that connects without consent.

Closed withIntelliAsset remote control shows the user a consent prompt, lets them decline or end it, and keeps a session history.

Three ways in

The right remote tool for the job

Pick a route to see what it does and where it stops.

Privileged access

Securita360: browser-based SSH and RDP to servers, with the credential kept in the vault.

  • SSH and RDPIn the browser, no agent on the target
  • Credential injectionServer-side, never to the browser
  • Just-in-time grantsReason, approvers, expiry
  • Break-glassCapped at 60 minutes, reviewed
  • Session policyProtocols, networks, hours
  • Command controlSSH, ordered rules
  • Live monitoringWatch and terminate
  • RecordingEncrypted, with SHA-256
Sessions are SSH and RDP. VNC brokering exists but has not been verified against a live target, so it is not offered here.
Securita360 requests and approvals page with a form to submit a time-boxed request, an optional approval chain and an emergency break-glass panel; account name blurred
Requests, approvals and break-glass. Screen from Securita360 running test data.

All three keep a record. Only Securita360 adds approvals, command control and encrypted recordings.

What changes

When remote access is controlled and recorded

Passwords stay put

Credentials are injected on the server, so there is nothing for a user to copy.

Access that ends

Grants expire on their own, and revoking one ends the live session.

Risky commands stopped

SSH commands are checked against an ordered policy, and every one is recorded.

A record of every session

Encrypted recordings and a tamper-evident audit trail answer who did what.

Questions

Frequently asked

Do users ever see the password?

No. Securita360 stores credentials envelope-encrypted and injects them into the session on the server, so the plaintext is never sent to the browser.

Which protocols are supported?

SSH and RDP from the browser, with nothing installed on the target. VNC brokering is built but has not been verified against a live target, so it isn't offered here.

Is VNC supported?

Not yet as a claim. The implementation exists, but it has not been tested against a real VNC server.

How do I restrict when and from where people connect?

A session policy sets allowed protocols, source network ranges, an allowed time window and a limit on concurrent sessions per user, and an access banner can be shown.

Can I stop a session that's going wrong?

Yes. Live sessions can be watched and terminated, and a session ends when its grant expires or is revoked, within one heartbeat interval.

What does command control cover?

SSH sessions, evaluated when Enter is pressed. It has blind spots for shell history recall, tab completion and full-screen programs, and RDP has no text command channel.

How is this different from remote control?

Remote control in IntelliAsset is for helping a user at their desktop, with their consent. Securita360 is for privileged access to servers, with approvals, command control and recording.

See it on your own servers

Give access without giving away the keys

Tell us how your team connects today and we'll show you Securita360 controlling it. No commitment required.