Skip to content

For security

Secure agent sandboxes that minimize blast radius.

Isolated cloud sandboxes for coding agents. Per-user scoping. Short-lived, scoped credentials. Secrets redacted from logs and the UI. Auditable transcripts. Bring your own compute and identity provider (SAML, SCIM, OIDC).

Block access outside a user's scope

# payments

  1. #payments Block access outside a user's scope

    ReedMEMBER2:14 PM
    @nori open a session on payments-api
    NoriAPP2:14 PM
    1. Checking Reed's scopes
    2. payments-api: allowed
    ✓Reed · payments scope
    Session started. Dry-run is clean.
    session 6f2d · payments-api →
    SandyMEMBER2:15 PM
    @nori open a session on payments-api
    NoriAPP2:15 PM
    1. Checking Sandy's scopes
    ✕payments-api not in Sandy's scope
    No access to payments-api. Ask an admin for the payments scope.

  2. #platform Hold elevated actions for admin approval

    IvyMEMBER4:07 PM
    @nori run this deploy every night
    NoriAPP4:07 PM
    1. Checking automation policy
    2. Elevated access required
    ✕Unattended run needs admin approval
    ✓Approval request sent
    Queued for admin approval. Nothing runs until they approve.
    Pending admin approval →

  3. #security Audit sessions that touched customer PII

    CliffMEMBER9:12 AM
    @nori how many sessions accessed customer PII in the last 24 hours?
    NoriAPP9:12 AM
    1. Querying session traces
    2. Filtering by data class: PII
    14 sessions touched customer PII. 11 eng, 2 support, 1 data.
    Open audit report →

  4. #lending Interrupt a non-compliant conversation

    SandyMEMBER11:03 AM
    @nori is it ok to approve this loan for applicant #4821?
    NoriAPP11:03 AM
    1. Running compliance check
    ✕Conversation interrupted
    Conversation interrupted. Credit decisions require a licensed underwriter.
--isolation

Why are Nori cloud agents more secure than local agents?

Nori agents Local agents
Access Isolated sandbox only

The agent never sees the host machine. Work stays inside an isolated session machine

 Anything on the laptop

Files, keys, browser sessions, email—the agent can reach whatever the user can
Setup Secure by default

Scopes, role-based access, and admin approval for privileged actions ship with the environment

 Hard to lock down correctly

Per-machine policies, drift, and exceptions make a secure local setup extremely hard
Credentials Short-lived, scoped credentials

GitHub tokens are minted per machine and revoked when a session changes hands; sign-in tokens expire in minutes; secrets are redacted from logs and the UI

 Secrets live on the box

API keys and tokens sit on disk, waiting to walk out with the laptop
--controls

Per user/team scopes.

Define what each person and team can reach. Every session only gets the access its role is granted—nothing more.

Credentials expire, the agent never leaves.

Credentials are scoped to the session and expire on their own. Work stays inside the session machine. Nothing sits on a laptop waiting to walk out the door.

Fully auditable traces.

Every session and every action is logged and searchable. Answer what ran, where, and on whose behalf—before the incident review.

Prevent non-compliant use.

Write policies once in your org skillset and every agent applies them before it answers—so credit decisions, medical advice, and other regulated acts stay with licensed humans.

--ship

Just @nori. It ships.

Start free trial Book a demo