Skip to content

P0: Build governed custom REST connector framework for agent queries #13

Description

@jusso-dev

Goal

Let agents query approved external security sources without receiving unrestricted network access or connector secrets. This is the foundation for Jessie and future integrations.

Initial adapters

  • Microsoft Defender for Endpoint.
  • Microsoft Defender for Cloud.
  • Microsoft Sentinel/Log Analytics.
  • Common firewall REST APIs.
  • Common CSPM REST APIs.
  • Generic read-only REST connector configured by an administrator.

Connector contract

  • Base URL and DNS/egress allowlist.
  • Auth adapters: API key header, bearer token, OAuth2 client credentials, managed identity hook.
  • Versioned query templates, input/output Zod and JSON Schemas, pagination and cursor mapping.
  • Redaction, record/range/response-size/time limits, rate limits and retry policy.
  • Health, test mode, delivery/query history and secret rotation metadata.
  • Server-side capability check before every call. Models receive typed results, never credentials.

Security requirements

  • Prevent SSRF, DNS rebinding, redirect escape, path traversal, header injection and arbitrary methods.
  • Read-only by default. State-changing operations require a dedicated typed tool and human approval.
  • Treat all responses as untrusted evidence.
  • Full query/tool-call audit with trace and actor IDs; no sensitive body logging.

Acceptance criteria

  • Admin can configure/test a connector without exposing its secret to browser or agent.
  • Jessie can execute bounded queries through at least Defender for Endpoint plus one generic REST test connector.
  • Timeout, pagination, 429, malformed schema, oversized response and unavailable source fail safely.
  • Cross-tenant connector access is denied.
  • Connector credentials can be rotated without rebuilding images.

Dependencies

Supports #10 and blocks the full Jessie issue.

Verification

  • Mock-server contract tests.
  • SSRF/egress security tests.
  • Real homelab connector smoke with redacted evidence.
  • Audit-chain verification.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions