Authorized target and testing window are attached.
api.example.com · owner-approved
ARTEX Research examines the operating loop behind AI security agents: define authorized scope, choose a useful action, preserve proof, and stop for review when judgment matters.
Authorized target and testing window are attached.
api.example.com · owner-approved
A tenant identifier may bypass object ownership checks.
risk: horizontal access · no destructive payload
Request, response, command, and affected asset stay linked.
traffic / api-get-order · status 200 · tenant mismatch
Impact is validated before the finding becomes a report.
approval required · evidence version pinned
Static interface study. The production ARTEX workspace lives at artex.lol.
The question
A tool call is not a finding. A fluent explanation is not evidence. The useful unit is a bounded run: a target, an approved scope, a sequence of decisions, the traffic or command output behind each claim, and a human who can review the result.
ARTEX is organized around that unit. Its public console keeps tasks, assets, exploration, traffic, findings, commands, and approvals connected so an operator can inspect how a conclusion was reached.
This research page is independent from the application itself. It describes the model of work; the console is the place where that work runs.
Operating loop
The loop stays deliberately narrow. Each step creates a record that the next step can use and a reviewer can challenge.
Record the system that may be tested, the rules of engagement, the available credentials, and the actions that require approval.
output / authorization recordTurn observations into a concrete hypothesis. Choose the least invasive action that can confirm or reject it.
output / decision + rationaleInvoke the tool, capture the request and response, preserve timestamps, and connect the artifact to the asset under test.
output / command + traffic + assetSeparate technical reproduction from business impact. A person decides whether the evidence is sufficient and what happens next.
output / reviewed findingProof standard
The report begins with the artifact that supports it. Every claim should point back to the observable behavior that made it useful.
“The endpoint appears to allow cross-tenant access.”
Tenant A reads tenant B’s order after changing one object identifier.
Keep the exact command, request, response, and dependency context available.
A matching domain or timestamp is a filter. Ownership and scope determine whether the artifact is relevant.
Technical behavior becomes a security finding only after its consequence is stated and reviewed.
Retests should refer to the original finding and the new artifact, not merely repeat the original narrative.
Operating constraints
Permission is not inferred from technical reach. Scope, approval rules, and the consequences of an action remain explicit parts of the run.
Written permission and a defined testing window come before the first request.
Destructive, high-impact, or ambiguous actions require a review point rather than an optimistic default.
Asset inventories and blocklists are controls. A guardrail matters only when the workflow actually checks it.
Humans decide impact, remediation priority, and whether a result is ready for a customer report.
Continue into the console
ARTEX combines a planner, parallel security agents, traffic capture, assets, findings, and human approval in one inspectable workspace.