Auto Secure LoginASL Scan Evidence and Control Result Example
Read a selected native ASL Scan control result. Understand not-applicable, unknown, pass and fail states before turning an audit rule into a remediation task.
Updated October 2, 2026
One selected control from an authorized review
This excerpt comes from ASL’s October 2, 2026 self-audit at 03:33:06 UTC. It preserves one native control from the asl-core rulepack; host details, authorization signatures, observation identifiers, internal paths and all other controls are omitted.
Result: not applicable
ASL-WIN-UAC-001 — the Windows User Account Control check returned notApplicable in a Linux review. Its title describes the condition the rule looks for; it does not assert that Windows UAC is disabled on this system.
A rule can carry a high severity and remediation text even when it does not apply. Read status, scope and evidence first; do not turn a rule title into a confirmed finding.
How to read other states
- pass: the observation met that particular criterion, not every possible control.
- fail: the observation did not meet the criterion; review context and remediation.
- unknown: available evidence did not support a conclusion.
- notApplicable: the control does not apply to the observed scope.
For MSPs and consultants
Define authorization, assets, permitted checks and the time window before collecting evidence. Keep observations and provenance in the full report. Assign remediation to an owner and recheck the specific criterion before closing a finding.
This selected example does not represent every control’s status or certify security or compliance. No new scan was started to publish it.
Download native control JSON · ASL Scan · Discuss an authorized assessment