Check your computer
Ask Ysra to check your Mac, Windows PC or Linux computer: what it reads, what it never reads, and how to read the report.
On this page
Ask "Can you check my security?", in any language, and Ysra checks the computer you're on: updates, disk encryption, firewall, antivirus, sharing, screen lock and accounts. It only reads. Nothing is changed, installed, scanned or attacked, and it takes about a minute.
In short
| Works on | macOS, Windows and Linux |
| Needs | The desktop app or the CLI on that computer, signed in as you |
| Reads | Settings and versions, listed before anything is read |
| Never leaves your computer | User names, serial numbers and the raw output |
| Lasts | One day, for this computer only |
From the desktop app#
- In an Ask or Code thread, ask "Can you check my security?"
- Under the reply, a Check this computer card shows I only look: I read its settings and change nothing. and which computer (On name).
- Open What I'll read on name to see the full list (below).
- Choose Check this computer. This confirms it's your own computer. A window from the desktop app asks you to sign a one-day, read-only check of this one computer with your key. Choose sign.
- The card says Checking… I'll post the summary here when it's done.
- A summary follows in the thread, such as I checked Sam's MacBook and found 3 things to fix. Nothing was changed. Choose Open the report.
Cancel at the signing window and nothing is checked (Nothing was signed.).
From the web app or your phone
A check is signed with the key of the computer being checked, so the web
app can't start it for you. It says: Checking a computer is signed with
its desktop app's key. Open the Ysra desktop app on that computer, or run
this in a terminal there: ysra security check.
From the terminal#
On the computer to check:
ysra security check
- If the computer isn't one of your devices yet, Ysra asks to add it: Add this computer to your devices now? [y/N]. You can remove it any time under Settings → Devices.
- Ysra prints exactly what it will read before reading anything, then asks Check this computer now? [y/N].
- It looks (about a minute), prints a short report, and gives the link to the full one.
| Option | What it does |
|---|---|
--yes |
Don't ask first. What is read is still printed. |
--json |
Print the result as JSON |
ysra security check <machine> |
Check a Linux server this computer reaches over SSH |
What is read#
- the macOS version, and when the Mac last started
- the Mac's model, chip and memory (never its serial number)
- which macOS updates are waiting, and the automatic update settings
- whether FileVault, the macOS firewall, System Integrity Protection and Gatekeeper are on
- whether the Mac logs in by itself and whether the guest account is on (yes or no only)
- how soon the screen locks
- which sharing services are on (Remote Login, Screen Sharing, File Sharing)
- which programs accept network connections
- XProtect's version (Apple's built-in malware protection)
- Time Machine: when it last backed up, how many backups there are, and whether it backs up to a disk or the network (never paths or disk names)
- how many accounts are administrators (counted, never named)
Nothing on a Mac needs an administrator. Without Full Disk Access for the app or terminal, the Time Machine lines come back as unknown.
- the Windows version, when it last started, and the latest installed updates
- the computer's maker, model, memory, processor and firmware date
- which programs accept network connections
- whether Windows Firewall is on for each network type, and how many rules let anything in
- how many local accounts and administrators there are (counted, never named)
- Remote Desktop: on or off, and whether it asks for sign-in first (NLA)
- whether the old SMBv1 file-sharing protocol is on
- Microsoft Defender's status (real-time and tamper protection, how old its definitions are) and the antivirus Windows Security lists
- User Account Control's level, updates waiting for a restart, and whether a policy turned automatic updates off
- needs an administrator: BitLocker, the audit policy, shadow copies and Windows backups
On a Windows computer in an Active Directory domain, the check also reads, as the signed-in account:
- the domain's and forest's functional level
- the domain's password and lockout policy
- user and computer accounts' settings (last sign-in, password age, delegation, Windows version): counted, never named
- how many people are in the administrator groups and in Protected Users
- whether LAPS manages each computer's local administrator password (never the password itself)
It needs the Active Directory PowerShell module (RSAT). Without it, those lines are skipped and the report says why.
- the system's release, kernel, uptime, processor, memory and disks
- hardware details and firmware date (root)
- updates waiting and when the system was last updated; whether automatic updates are on
- which services accept network connections
- the host firewall's rules: iptables, nftables, ufw or firewalld (root)
- the effective SSH settings (root)
- accounts and groups, and how many sudo rules need no password (root, counted only)
- FTP and Redis settings when they're installed (root for Redis)
- local certificates, and VPN software (OpenVPN, WireGuard, IPsec, OpenConnect) with its version
- which backup tools are installed and whether one is scheduled
Lines marked root are skipped unless you allow root checks with
ysra machines audit-root --this-computer on; see
Review the command and grant administrator rights only for that check.
What is never read or sent#
- No files, documents, mail or browsing history.
- No passwords or keys. Ysra never asks for an administrator password. Checks that need one are skipped, and the report says how to allow them.
- User names, serial numbers and the raw output stay on your computer. Only facts and counts are sent ("2 administrator accounts"), so the report can say what to fix.
- No scanning or attacking. Attack and scanning tools are refused on your computer, even if you ask.
Read the report#
The report is titled Security report, with when it was checked. While the check is still running: Still checking; this page updates by itself.
| Part | What it shows |
|---|---|
| The verdict | One line at the top, such as Nothing to fix on the machines I checked. |
| Fix these first | The urgent ones: Critical and High |
| Everything else | Medium, Low and Info |
| Each problem | What I saw, Why it matters and How to fix, with the badge Seen on your machines |
| What I checked / What I couldn't check | Every check, and the ones skipped with the reason (for example needs admin) |
Fix with Code opens Code with the fix described, when Ysra can prepare it for you. You can also Download report.
To check again after fixing, ask again or run ysra security check again.
What it means for your business#
A check on its own doesn't know if this is a test laptop or the PC with your patients' files. For servers and a whole office, start a full Mayz security review and describe the business: it changes how serious each finding is.