remFREE Compliance Center turns endpoint evidence into a small number of human-readable states.
The important principle is that remFREE should communicate what it actually knows.
Missing evidence should not automatically be treated as proof of failure.
Compliant
Compliant means remFREE received evidence showing that the required evaluated controls satisfy the configured expectations.
No remediation is currently required for those controls.
Action Needed
Action Needed means remFREE received sufficiently clear evidence that one or more required controls do not meet the expected state.
Examples could include:
- required protection is disabled
- an expected security setting is missing
- a required configuration explicitly failed evaluation
This represents a confirmed condition that needs review or remediation.
Attention
Attention represents a condition that deserves administrative review but is not necessarily a direct compliance failure.
One example is a pending reboot after maintenance.
The endpoint may not be misconfigured, but the state still deserves attention.
Unknown
Unknown means remFREE could not confidently determine the result.
Possible causes include:
- required evidence could not be collected
- the operating system did not expose the expected information
- permissions prevented collection
- a command failed
- the result was incomplete
- an unexpected platform condition occurred
Unknown is deliberately not the same as failure.
In a security-focused system, lack of evidence should be visible without being rewritten into something the evidence does not actually prove.
Not Scanned
Not Scanned means remFREE does not yet have a current result for the required compliance evaluation.
Run a compliance collection or scan to obtain evidence.
Required controls
Organizations may choose which supported controls determine their compliance verdict.
This allows remFREE to distinguish between:
- evidence that is useful to observe
- evidence that is required for compliance
A control can therefore be informative without necessarily determining the overall device verdict.
Evidence is more useful than a badge
A compliance result should explain why it exists.
Where supported, remFREE can provide information such as:
- detected value
- expected value
- evidence
- source job
- remediation guidance
The goal is not simply to display green or red.
The goal is to produce a result an administrator can understand and defend.
Re-scan after remediation
After correcting an issue, collect compliance evidence again.
Compliance reflects the state captured by the most recent evaluation.
Changing the endpoint does not automatically change historical evidence.
A new scan confirms the new state.