Techniques › › AN2074
AN2074 Analytic 2074
SaaS · attack.mitre.org · ATT&CK Enterprise v20.0
<p>An analyst observes a supported security artifact/task enter an autonomous defensive-analysis workflow, the analysis begin successfully, and the same workflow subsequently record an explicit failure, refusal, termination, or abnormal terminal state inconsistent with $AuthorizedAnalysisStopConditions$.</p>
- Detects
- Part of
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| AWS:bedrock | GuardrailTrace | DC0038 Application Log Content |
| AWS:bedrock | AgentTrace.FailureTrace | DC0038 Application Log Content |
| AWS:bedrock | AgentTrace.ModelInvocationInput | DC0038 Application Log Content |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
SupportedArtifactClasses | artifact/task classes expected to complete the analysis workflow; derive from product capabilities and clean executions |
AuthorizedAnalysisStopConditions | known legitimate refusal/failure/cancellation states from product documentation and operational baseline |
AnalysisCompletionWindow | normal completion duration by task/artifact type |