Using Xseth effectively

Run a scan, read the verdict, hand off the report.

Xseth is a teammate, and it pays to work it like one: scope it well, read the evidence, and let it do the triage so you spend your time on judgment. Here is the end-to-end loop, plus the screens that show the agent's thinking.

Open the console

Step by step

01

Confirm your authorization first

Only submit targets you own or have written authorization to test. This is non-negotiable and it is enforced: you can only scan domains on your authorized scope, SmartGate refuses off-limits categories outright (hospitals, governments, schools and critical infrastructure), and every target the agent derives afterwards is re-checked against your scope before anything runs. If a target is out of scope, it is refused, with a reason.

02

Submit a target

Open the console, start a new scan, and enter a domain or IP. SmartGate evaluates it in real time and tells you whether it was approved or declined, and why. Once approved, the scan is queued and you can watch the recon stages progress live.

03

Read the recon results

When recon lands you get the raw map of your surface: the subdomains discovered, the open ports, the live web services with their detected technology, and the per-asset service versions. This is the evidence the assessment is built on. You can always trace a finding back to what was actually observed.

04

Work the threat assessment

The assessment is where you spend your time. Findings are ranked by severity; open one to see its evidence line, its impact, and how to remediate it. Read the badge carefully, because it has four meanings, not two: CONFIRMED means a deterministic probe reached the finding and matched, REFUTED means a probe ran and disproved it, UNPROVEN means nothing has verified it yet, and NOT PROBED means no probe class covers it at all. Disagree with any of them and record your own verdict; yours wins. The prioritized next steps tell you what to look at first.

05

Ask Thoth

Every assessment ships with Thoth, Xseth’s grounded chatbot, named for the keeper of knowledge. Ask it things like "which findings are actually confirmed?", "walk me through the highest-impact path", or "what did the agent decide, and why did it stop?". Every answer cites the pipeline data it came from, and Thoth is strictly read-only. It explains the scan; it cannot launch a new one or invent a finding.

06

Export the report

When you are ready to hand something off, download the PDF. It is a client-ready deliverable (findings with evidence, impact and remediation, plus the agent narrative) generated on demand from the assessment you just reviewed.

Seeing the reasoning

The screens behind the verdict

Beyond the assessment, four screens let you audit how the agent reached its conclusions, so the output is never a black box.

World-model

A visual map of hosts, services, subdomains, web endpoints and the edges between them: the structure the agent reasons over. Inspect a node to see what is known about it.

Attack chains

The multi-step paths where low findings combine into a high-impact outcome, each shown as a numbered kill-chain. An empty result is honest, not a failure. It means no genuine chain was found. If a probe later refutes the premise of a step, the whole chain prints broken and is down-rated, so you can watch the engine withdraw its own conclusion.

Loop decisions

The decide-loop trail: at each step, whether the agent continued or stopped, and the reasoning behind it. This is where you see the agent prove it bounds its own work.

Validation queue (operators)

Where active-payload probes wait for sign-off. The agent only proposes them; it never runs them itself. An operator reviews which finding and asset each one targets, then approves or denies. Approval mints a one-time, scope-bound token before the probe fires.

Get the most out of it
  • Re-scan as your surface drifts. Each run rebuilds the picture from scratch, so a new subdomain or a newly opened port only appears in a run that goes looking for it. Comparing one run against the last is still yours to do.
  • Trust CONFIRMED, verify UNPROVEN. Treat confirmed findings as real and reachable, and read a REFUTED one as work already done for you. Ask Thoth or run an approved probe before acting on anything still unproven.
  • Use Thoth to interrogate, not to trust blindly. Every answer is grounded in the scan's data and cites it, so ask it to show its work.