Impact

An unknown number of users experienced inconsistencies in the coverage levels tables within progress reports. The issue started on UTC-5 23-07-28 18:09 and was proactively discovered 6.3 months (TTD) later by analysts who noticed the inconsistency in the reported coverage level metrics. The problem was resolved in 2.4 days (TTF) resulting in a total impact of 6.4 months (TTR).[1][2].

Cause

Some files were being incorrectly marked as verified. The method of comparing the oldest allowed attack date caused some files to be erroneously marked as verified, even if they did not meet the condition of having all affected lines [3].

Solution

The method for comparing the date of the ToE line attack with the oldest allowed date was corrected [4].

Conclusion

A unit test was added, and a script was created to check metrics using data from the group being verified [5]. These measures aim to avoid similar issues in the future by ensuring accurate verification processes. INCOMPLETE_PERSPECTIVE < MISSING_TEST