stride-repudiation

A repudiation threat occurs when an action in a system cannot be reliably attributed or proven. STRIDE threat modeling identifies these vulnerabilities by finding gaps in auditability and accountability, such as missing or incomplete audit logs.

To identify repudiation threats in a system architecture, analyze workflows and action provenance to locate actions logged without reliable actor identity. This process exposes vulnerabilities where evidence is weak or missing, ensuring accountability.

Yes, finding repudiation vulnerabilities requires knowledge of system workflows and action provenance. This prerequisite understanding is necessary to accurately determine where audit logs are missing or incomplete and where accountability is insufficient.

The best way to audit accountability gaps in a repository is to apply the STRIDE methodology to review actions that cannot be reliably reconstructed. This identifies vulnerabilities where evidence is weak, such as actions logged without reliable actor identity.

STRIDE threat modeling handles missing or incomplete audit logs by treating them as repudiation vulnerabilities. It specifically focuses on these gaps in auditability to highlight where actions cannot be reliably attributed or proven.

You should not use a specialized repudiation threat analysis if your goal is to evaluate other STRIDE categories like spoofing, tampering, information disclosure, or denial of service, as this approach focuses exclusively on auditability and accountability gaps.