Fide AI

FID-076 · Open question

Authorization Boundaries and AI Control in Cybersecurity

Which controls keep capable agents within legitimate authorization when task pressure, untrusted inputs, or delegated work creates opportunities to exceed it? For autonomous cyber defense, how can response controls preserve threat containment and legitimate service availability while respecting human authority?

Research in development

See the thinking. Help shape the work.

Explore a specific question, the approach we propose, and where your expertise could help. Each brief states its current stage.

Cybersecurity

Planned

When the Defender Becomes the Threat

A proposed study of when additional oversight reduces harmful intervention without making autonomous defense ineffective. We will compare permission checks with escalation and approval under uncertain evidence.

Study direction selected. Collaborator, environment and final protocol remain to be qualified; experiments have not begun.

Explore the study brief →

Updated

Part of our cybersecurity agenda

Controlled autonomous response →Browse cybersecurity calls →

Program context

CASTLE: AI agents for network defense ↗

CASTLE develops AI agents and environments for network defense. Fide’s proposed contribution is to measure the operational tradeoff between containing a threat and preserving legitimate activity.

ANSR: evidence for trustworthy autonomy ↗

ANSR connects trustworthy autonomy with robustness and assurance evidence, and identifies the mission cost of frequent fallback. It motivates evaluating useful action alongside control and recovery; Fide is not claiming to develop ANSR’s neuro-symbolic architectures.

Research context; no funding, partnership, endorsement, or open solicitation is implied.

Why the question remains open

Completing an authorized task is not sufficient if the system expands its access or bypasses oversight along the way. This call studies whether enforceable boundaries hold under pressure, not whether an agent can recite a security policy. A defender that isolates every host may stop an attack while disrupting the organization it protects. Useful response must account for containment, service continuity, and the costs of waiting for human approval.

Working hypothesis

A proposition to test, not a finding.

Least-privilege tools and enforceable approval gates will reduce unauthorized completed actions more reliably than instruction-only controls at comparable useful-task performance. For defensive response, evidence-sensitive approval and reversible actions may improve containment at a fixed disruption tolerance relative to static approval rules. Controls may instead shift failures or impose unacceptable delay and workload; the comparison must measure these possibilities rather than presume a benefit.

Proposed method

How the question could be tested

  • 01Create isolated scenarios with explicit asset ownership, allowed actions, revocation points, and synthetic adversarial inputs. Include single-agent and delegated workflows.
  • 02Compare instruction-only policies, permission enforcement, independent monitoring, and combined controls using matched tasks and resource budgets.
  • 03Measure attempted and completed violations separately, detection latency, successful shutdown or revocation, false alarms, and legitimate task completion. Test previously unseen scenarios and adaptive challenges.
  • 04For a first defensive-response comparison, work with incident responders to specify a host-isolation decision, legitimate service requirements, explicit authority, and benign look-alikes. Compare always-request-approval, fixed-rule, and evidence-sensitive policies with thresholds chosen on development scenarios.
  • 05Test ambiguous evidence, permission changes during a run, and prespecified simulated approval delays. Measure containment and time to containment alongside service disruption, unnecessary interventions, authority violations, escalation frequency, and verified restoration of the simulated service.

Needed controls

What must constrain the study

  • 01Use only owned sandboxes with disabled external access and synthetic secrets. Review challenge designs and release artifacts for dual-use risk.
  • 02Specify monitor access and trust assumptions; separate ordinary mistakes from deliberately adversarial test-agent behavior without inferring model intent.
  • 03Pre-register intervention budgets and failure thresholds. Include benign difficult tasks so blocking everything cannot count as success.
  • 04Treat simulated approval delay as an experimental assumption, not a measurement of human review quality or analyst time. A separate practitioner study would be needed to establish those outcomes.
  • 05Keep incident families separate across development and evaluation. Compare policies at matched resources and report outcome tradeoffs and uncertainty rather than hide disruption and containment inside a single composite score.

Relationship to existing work

Extends the cross-domain questions in FID-069 and FID-074. FID-070 remains the dedicated faith-facing prompt-injection call; this brief tests cybersecurity control protocols and their tradeoffs. FID-087 studies collective resilience after an agent failure; FID-088 studies independent verification of software repairs. This call focuses on whether and how the defender is permitted to act while preserving useful defense.

Expected outputs

Artifacts the work should produce

  • 01A control-evaluation harness with safe scenarios and reproducible comparisons.
  • 02An explicit account of residual failure modes and useful-work tradeoffs.
  • 03A practitioner-reviewed response-policy comparison covering containment, service continuity, approval delay, authority changes, and recovery.

Open questions

Uncertainties the protocol must resolve

  • 01Do controls generalize across models and toolchains?
  • 02How does delegation change revocation and responsibility?
  • 03When does waiting for approval cause more harm than a bounded, reversible action?
  • 04Which service and disruption measures reflect the operator’s actual responsibilities?

Open question

Open work

Primary need: security engineering, adversarial evaluation, control protocols, independent review

  • Security engineers to implement testable permission boundaries.
  • Control researchers and operators to independently challenge protocols.
  • Incident responders to define realistic containment decisions and service requirements.

New to the Contributor Network? Share a short private introduction once, even if you join several calls. You can join the public discussion while introducing yourself.

Join the Contributor Network ↗