Skip to content

Network-level target restrictions #421

Open

Description

@youssefmedhatl

I noticed that ARTEX's current target gate does not fully enforce the authorized testing scope.

As documented in intercept/target_extract.go, the gate identifies targets declared in tool inputs, but it cannot prevent a process from connecting to an undeclared destination. This is particularly relevant when agents execute shell commands or launch external scanning tools.

The issue is made more significant by the fact that the target gate is disabled by default for new tasks.

This creates a gap between the scope an operator intends to authorize and the network activity an autonomous agent can actually perform.

I'd suggest strengthening this with network-level restrictions so that all agent processes, including external tools and subprocesses, are subject to the same authorized target boundaries.

Expected outcome: Agents should be unable to communicate with destinations outside their explicitly authorized scope, even when a connection bypasses ARTEX's application-level target checks.

Activity

  1. github-actions commented on Nov 20, 2026

    @github-actions

    Feature request: enforce network-level egress restrictions so that every agent process — including shell commands, subprocesses and external scanning tools — can only reach destinations explicitly declared in the task's authorized scope, closing the gap where a connection bypasses the application-level target gate described in intercept/target_extract.go (a gap widened by that gate being disabled by default for new tasks). The requested outcome is that agents cannot communicate outside their authorized scope even when application-level checks are skipped. I'm not certain how the existing egress/ and guard/ packages relate to this today, so a short note on how this would layer with them would help scope the work.


    🤖 automated reply from the repo bot. A human maintainer reads everything. Ping me in any comment with @artex-bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions