Users need the ability to manually mark device requirements as completed for instance when the platform does not automatically detect them. Manually confirmed items should have a distinct visual indicator to differentiate them from automatically detected completions Proposed visual labeling: a blue checkmark instead of a green one; an "M" symbol for manual completion Use Case: A security team runs a compliance check, but the platform fails to detect a specific security setting due to a misconfiguration in the detection logic. The team verifies that the setting is correctly configured on the device through an alternative method (e.g., checking system settings directly or running a different security scan). Instead of waiting for a fix in detection logic, they manually mark the requirement as completed to ensure an up-to-date compliance status.
