Skip to content

Migrate Payload API calls to Threat Arsenal endpoint #211

@MarineLeM

Description

@MarineLeM

Current Behavior

External collectors (e.g. Atomic Red Team) upsert payloads in OpenAEV through the /api/payloads endpoint.

New Behavior

As part of #4458 — Consolidate Payloads & Contracts into a Unified Page, all payload creation from the frontend is now handled through the /api/threat_arsenals endpoint, which is responsible for creating both the Payload and its associated InjectorContract.

Improvement

The Payload concept is intended to be replaced in favor of the ThreatArsenal (Action) abstraction. To keep consistency across the project we should migrate the /api/payloads endpoint to /api/threat_arsenals endpoints.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureuse for describing a new feature to developneeds triageuse to identify issue needing triage from Filigran Product team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions