Update a pending proposal by modifying its threat positions and/or approving or denying it
PATCH /v1/threats/proposals/{id}
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The ID of the proposal to update
Example
123Request Body required
Section titled “Request Body required ”object
A position of a threat.
This is used to calculate the consequence of moving a threat objective to a certain likelihood and impact.
In most cases, it’s better to use a ThreatProfile than to use a Vec<ThreatPosition>.
object
Y-axis for the threat objective
X-axis for the threat objective
PK of the threat objective in the database
Responses
Section titled “ Responses ”Proposal updated
Contains detailed information about a proposal. This includes values of [Proposal] and a list of [FullProposalAction]s.
object
Contains values of threat_proposal_action::Model and a list of [InherentScore]s.
object
object
Contains information about the current scoring of a threat objective.
Inherent scores don’t exist without the context of an organization, and cannot exist without some relationship to a threat objective.
This struct should be refactored at some point to be more generic, because it doesn’t necessarily
have to relate to a proposal, nor does this struct need to include the threat_objective_name if not
requested alone.
object
The date the score was created.
An auto-incrementing PK value that uniquely identifies the score given the threat objective name
The y-axis
Determines whether this inherent score should be included in some return types of threat levels. TODO(dsgallups): bad design
The x-axis
The proposal action PK that this score is associated with
The proposal PK that this score is associated with
The threat objective PK
object
No proposal found