triage agent parsed authentication-results-orig instead of authentication-results and reported spf pass on a spoofed...

TL;DR

Parse the Authentication-Results header (the receiver's own verdict) and ignore Authentication-Results-Orig, which is an unauthenticated copy an attacker can include, and add a test with a forged orig header to the agent's checks. Prove it on one message or campaign before rolling it to the rest of messages in the sweep or campaign, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

triage agent parsed authentication-results-orig instead of authentication-results and reported spf pass on a spoofed message

Use this when

• You see this exact error or symptom: triage agent parsed authentication-results-orig instead of authentication-results and reported spf pass on a spoofed message.
• The failure is in the phishing triage agent and the mail or security APIs it calls, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one message or campaign first and capture the evidence before changing anything: check the triage agent run log for the campaign, the gateway or Defender record for the same message, and the original message headers, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Parse the Authentication-Results header (the receiver's own verdict) and ignore Authentication-Results-Orig, which is an unauthenticated copy an attacker can include, and add a test with a forged orig header to the agent's checks. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Validate the input against its expected format before the main step consumes it, and report the exact offending record or row instead of failing the whole run. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: rerun the agent on the single campaign or message that failed and compare its verdict and actions against the gateway record. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of messages in the sweep or campaign in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

triage agent parsed authentication-results-orig instead of fix

The verbatim error or code phrasing for this fault in the phishing triage agent; the fix is the same one in the steps above.

triage agent parsed authentication-results-orig instead of

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix triage agent parsed authentication-results-orig instead

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Microsoft Graph and Defender, Proofpoint TAP, Mimecast, Google Workspace and sandbox services used by triage agents, as named in the title.

Why it happens

This fault happens because inputs produced by other systems change format without notice, and a consumer that assumes the old format fails on the first record that differs. In this case the condition is the one named in the title, in the phishing triage agent and the mail or security APIs it calls: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zYm33ykDZk9E8rGudFbVaQ

Resolved from the public thread: https://vectle.com/posts/pst_zYm33ykDZk9E8rGudFbVaQ

Thread query: triage agent parsed authentication-results-orig instead of authentication-results and reported spf pass on a spoofed message

TL;DR: Parse the Authentication-Results header (the receiver's own verdict) and ignore Authentication-Results-Orig, which is an unauthenticated copy an attacker can include, and add a test with a forged orig header to the agent's checks. Prove it on one message or campaign before rolling it to the rest of messages in the sweep or campaign, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.