Device security: BitLocker, credential files, isolation, lost devices, admin passwords
Video guide: Inspect device security evidence before requesting an action
Recorded October 22, 2026 in the fictional Summit Managed IT staging workspace, App 0.432.1. The deployed demo can differ from the current product; use the written guide for current behavior. No secrets revealed; no BitLocker, credential scan, isolation, password rotation or recovery test.
Full narration captions are included in the video. Open video full screen · Download subtitles · Download transcript
Video transcript
Open the intended device, then Vulnerabilities. This is an offline fictional endpoint. Security panels show reported evidence and its limitations; they do not prove current encryption, firewall state or a complete credential-file scan when data is old or missing.
Open Tools to locate operational controls. Isolation, encryption and lost-device actions need separate authorization and recovery access. We do not reveal keys or passwords and do not queue a command. A local queued badge is not proof that a real endpoint changed.
Read the guide for platform support and verification. Confirm command results, later telemetry and native state. Isolation needs actual allowed and blocked traffic checks and verified release; recovery needs independently retained usable recovery material. Preview records or a single ping are insufficient.
What it does
The device's Vulnerabilities and Tools tabs, Security > Passwords, and the compliance report together cover the endpoint security posture: disk encryption with recovery-key escrow, a daily scan for plaintext password files, one-click network isolation, lost-or-stolen device actions, rotated local administrator passwords, and failed sign-in monitoring.
BitLocker
How it works: on Windows the agent reports each volume's status, protection state, method and encryption percent a few times a day, and sends the recovery passwords on that scan only. The server strips the keys out of the metric and stores them encrypted per protector GUID. Compliance's disk-encryption check reads the status.
Steps:
- Device page > Vulnerabilities > BitLocker shows every volume with a progress bar.
- Reveal recovery key (OWNER or ADMIN) shows the escrowed 48-digit password; the reveal path records an audit attempt; verify the action and required audit evidence for your use.
- Enable BitLocker (system drive not protected): queues a signed script that encrypts with XTS-AES-256 using a TPM protector and adds a recovery password, which is reported for escrow on a later successful scan. Verify protection and usable recovery material separately before relying on recovery. A device without a ready TPM is skipped and says so. An encrypted-but-unprotected drive gets its protectors turned back on instead.
- Use the Refresh button in the device header to speed up the next report.
Credential-file scan
How it works: once a day, 15 minutes after the agent starts (and after Refresh), the agent walks each user profile (Desktop, Documents, Downloads, OneDrive and the rest, skipping AppData, Library, caches, package trees, hidden folders, links and junctions) for file names that suggest a plaintext password store: password, passwd, credential, creds, login, secret, 2FA, backup codes and similar, on document-like extensions only, with policy and how-to documents excluded. It inspects filename/path metadata, sizes and dates rather than file contents and skips cloud placeholders. Metadata can still be sensitive; path labeling depends on the installed agent build. Do not assume source-side profile aliases are present in older executables. On macOS the agent needs Full Disk Access or the profile shows as denied.
Steps:
- Device page > Vulnerabilities > Credential files: count pill, the matched files with the token that matched, size and modified time.
- Ask the user to move the contents into a password manager and delete the file; a later successful complete scan can show the hit absent. An incomplete/denied scan or no current sample does not prove deletion.
- Clients > Compliance: the check "No plaintext credential files on endpoints" fails per organization while any endpoint has a hit, listing the hostnames.
The filename heuristic is bounded (source limits: 120 seconds, 400,000 files, 200 hits, depth 12 and 64 MB per candidate). It reports truncation/denied profiles and can miss other files, encrypted archives or credentials in content. No hits is not proof that no passwords exist. macOS permissions and exact installed agent behavior need native verification; a source-file comparison does not attest an endpoint executable.
Network isolation
How it works: a signed command attempts platform-specific firewall changes. Windows attempts policy backup and application/network allowances. Linux changes IPv4 iptables, keeps established/related connections and server/relay TCP, and can broaden outbound 443/8091/8094 when hostname resolution fails; it is not process-only isolation and does not install an IPv6 equivalent. Release restores a saved policy when available; otherwise Windows can reset defaults and Linux can open/flush filter rules. Exact restoration and uninterrupted management connectivity are not guaranteed. The Antivirus Health trigger can isolate automatically on an active threat at or above a chosen severity.
Steps: Device page > Vulnerabilities > Network isolation > Isolate (type the hostname to confirm). The header pill reflects local queued state before native execution; confirm the signed command result and actual firewall/connectivity. Isolate/release command TTL is one hour. No reboot-persistence guarantee is established by this implementation. macOS is not supported yet.
Lost or stolen device
Device page > Tools > Lost or stolen (OWNER or ADMIN only), each requiring the hostname typed:
- Isolate: as above.
- Crypto-lock (Windows): attempts to force BitLocker recovery on protected volumes for the next boot. Verify the native command result and independently retained usable recovery material; dispatch is not proof of protection or recovery.
- Factory reset (Windows): Reset this PC through systemreset, with a fallback to the local MDM bridge on builds that lack it; permanent, also requires typing ERASE.
- Remote erase (Mac): for a Mac that is also enrolled in Apple MDM, an EraseDevice command over APNs.
Crypto-lock/factory-reset CTAs can remain queued up to a week; isolation uses its separate one-hour TTL. Offline devices do not execute while unreachable. A Mac erase is a separate MDM queue and requires a matching serial and push material, not an agent check-in. Verify actual delivery/completion; a dispatch message is insufficient.
Local administrator passwords (Security > Passwords)
How it works: a per-device local administrator account is created or adopted and its password rotated on a schedule by a signed command; pending/current password material is encrypted and access is role-gated. The server promotes the pending secret only after a DONE command result with exit 0; a queued request is not successful rotation. Compliance's admin-rotation check reads the rotation dates.
Steps:
- Open Security > Passwords, choose the customer, enter the admin username and how often to rotate, then choose Apply to all devices.
- Security > Passwords lists every device grouped by organization with the last rotation; the device page > Tools has the reveal.
Failed sign-ins and lockouts
The Account Lockout trigger (guide 5) has the agent count failed logons and lockouts from the Security log inside a window and report a sample (logon type, source, reason, calling process). The device's Vulnerabilities > Account security panel shows the counts, the sample and an AI summary.
Verification
- BitLocker: a volume shows Protection On and a recovery key is stored.
- Credential files: create
passwords.txton a test desktop, press Refresh, and check for it after a successful complete scan and a later reporting heartbeat. - Isolation: in an approved test with recovery access, verify the real command result, IPv4/IPv6 rules and allowed/blocked traffic, then release and verify the resulting policy. A badge or ping test alone cannot establish containment/restoration.
Troubleshooting
- BitLocker shows no data: the agent is older than 0.4.39 or the device is not Windows; the panel says which.
- Credential files shows a denied profile on macOS: grant Full Disk Access to the agent.
- Crypto-lock reports nothing encrypted: inspect actual volume/protection state and recovery requirements. Do not enable encryption or trigger a factory reset merely to test connectivity.
For Apple/Android enrollment, actual MDM commands and lifecycle limits, use MDM / EMM. Windows factory reset uses the local Windows reset/MDM bridge; it is not an RMM Windows MDM enrollment provider.
