adda-access/1.1.0 · updated Jul 9, 2026

ADDA Access: devices, sessions, and tunnels

How to manage device trust, sessions, policies, and tunnels without losing continuity.

ADDA Access brings devices, sessions, policies, keys, routes, and tunnels together to maintain access continuity using trust criteria.

Operations do not end when a session is opened or closed. You must also understand whether a device lost posture, a tunnel degraded, a policy became stale, or a credential no longer deserves trust.

This guide helps connect the Access assessment with Login Shield, API Shield, incidents, tasks, and evidence so that a sensitive measure remains explainable and reversible.

Checklist

• Review devices, sessions, and policies before revoking access.
• Confirm whether the tunnel or device lost its trust score.
• Record evidence or a task when the measure affects operational continuity.

Quickstart

1. Read the overall Access status first to see coverage, trust, and degraded peers.
2. Then inspect devices or sessions to locate the source of the trust loss.
3. If the measure affects continuity, open a task or incident before closing it permanently.

Operational flow

Measure posture

Review the number of devices, active sessions, policies, and risky tunnels.

Determine whether the problem is broad or isolated.

Isolate the cause

Locate whether the risk comes from the device, session, peer, or policy.

Apply the smallest measure that resolves the problem.

Coordinate continuity

If closing, rotating, or revoking is necessary, link the measure to tasks, incidents, or evidence.

Preserve continuity and auditability.

flowchart LR
  S1["Measure posture"]
  S2["Isolate the cause"]
  S3["Coordinate continuity"]
  S1 --> S2
  S2 --> S3

Validators and checks

They run a contextual reading for this surface and return suggested steps with an operational focus.

Review Access status

Returns current Access signals and related articles.

Cross-check Access with login

Focuses on access continuity when authentication attempts are sensitive.

Examples

Payload to create or update a session

{
  "deviceId": "device_demo_001",
  "policyId": "policy_ops_001",
  "memberId": "member-demo-001",
  "riskScore": 48
}

Links and references

Related routes

Access in the workspace Access in admin

APIs

/api/adda/v1/access/status
/api/adda/v1/access/devices
/api/adda/v1/access/sessions
/api/adda/v1/access/policies

Docs and supporting routes

docs/ADDA_API.md
docs/ADDA_SOC_OPERATIVO.md

Common issues

• Closing sessions without considering policies or continuity can disrupt legitimate operations.
• Keeping a low trust score without a task or incident makes repeated decisions difficult to explain.

Suggested actions

• Escalate to an incident if the problem involves multiple devices, tunnels, or peers.
• Use evidence if you revoke a credential or interrupt meaningful continuity.

Useful reason codes

SESSION_RISK

The active session shows traits that warrant containment.

Review the policy, device, and continuity before closing it.

ACCESS_DEVICE_LOW_TRUST

The device lost operational trust.

Strengthen verification or review the device posture.

TUNNEL_DEGRADED

The tunnel or peer shows degradation or risk.

Evaluate rotation, containment, or a route change.

Score dictionary

trustScore

Device trust based on posture and activity.

deviceRisk

Accumulated risk from the agent, tunnel, and sessions.

sessionsActive

Number of active sessions associated with the device.

Protocol notes

• Secure continuity is more valuable than an early revocation without coordination.

Article history

Jul 9, 2026

New operational Access article focused on continuity, trust, and escalation.