Rework is extra labor and processing needed to correct something that did not meet the expected target. In cyber security, it usually means the additional work required after a failed build, a misconfigured control, a bad patch, a blocked deployment, or a compromised system that must be cleaned and rebuilt. Rework is not the original task; it is the correction cycle that follows it.
It matters because rework consumes time, staff attention, and system capacity, often while teams are under pressure to restore service. Attackers can increase rework by triggering repeated failures, forcing defenders to inspect logs, reimage endpoints, rotate credentials, or validate systems again. Defenders try to reduce rework with automation, standard baselines, testing, and clear recovery playbooks, because every extra correction step slows response and raises operational cost.