Aduana Digital de Defensa Argentina
Create ADDA access
← ADDA Manual

trustapi/1.1.0 · updated Jul 9, 2026

Trust and automation index

How to read whether a visit appears human, automated, or coordinated, and determine the next step.

The trust index summarizes the reading of an IP, domain, session, or campaign in one place. It supports human judgment with explicit reasons and a suggested action.

A score reading does not replace the operator's decision: it guides it. Reason codes clarify why a case appears benign, mixed, or risky and help escalate toward verification, limiting, a watchlist, or Evidence.

When the same pattern appears on more than one surface, the score improves when used with incidents, tasks, Access, Mail, WAF, or Intel.

Checklist

  • • Compare the automation reading with the session and domain readings.
  • • Confirm that the recommended action matches the severity.
  • • Record feedback if the reasons are insufficient to explain the decision.

Quickstart

  1. 1. Read severity, action, and reason codes as one operational sentence.
  2. 2. Cross-check the score with the affected module before blocking by default.
  3. 3. For a sensitive case, bring the reading into an incident, task, or Evidence.

Operational flow

Query

Take a reading of an IP, domain, session, or campaign.

Use the score type that best fits the case.

Explain

Turn the reason codes into shared criteria for the team.

Align technical and operational language.

Decide

Connect the suggested action with the module that will actually execute the measure.

Do not treat the score as if it were the action itself.

flowchart LR
  S1["Query"]
  S2["Explain"]
  S3["Decide"]
  S1 --> S2
  S2 --> S3

Validators and checks

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

Validate TrustAPI reading

Summarizes articles, checks, and next steps for scoring and explanation.

Examples

Payload for a session score

{
  "sessionId": "sess_ops_001",
  "domain": "login.capacero.ar",
  "ip": "198.51.100.18"
}

Links and references

APIs

  • /api/adda/v1/trust/score
  • /api/adda/v1/score/ip
  • /api/adda/v1/score/domain

Docs and supporting routes

  • docs/ADDA_API.md
  • docs/ADDA_PROTOCOLO.md

Common issues

  • • Treating the suggested action as an automatic order without reviewing the affected module.
  • • Failing to record reasons when the signal is mixed prevents later review.

Suggested actions

  • • Use Copilot and Manual when the score is not enough to justify the action.
  • • Escalate to Evidence if the reading led to blocking, revocation, or strong containment.

Useful reason codes

BOT_HIGH

Estimated automation is high for the analyzed context.

Apply progressive verification or limiting.

GEO_ANOMALY

The origin or expected path is inconsistent.

Cross-check with Access, DNS, or an incident before trusting it.

SESSION_RISK

The session shows traits that warrant close monitoring.

Review continuity and controls for the session or device.

Score dictionary

severity

Institutional priority of the signal on the ADDA scale.

action

Next operational step recommended by the engine.

reasonCodes

Explainable reasons supporting the reading.

Protocol notes

  • • The score gains value when connected to a concrete response surface.

Article history

Jul 9, 2026

Expanded the glossary and operational score journey.