Your Laptop Runs Admin All Day: Settings Ordinary Users Should Flip

Archi3 min read

securitydevelopersprivacy

Contents
  1. The Admin Account Habit That Costs You Later
  2. Account and Login Changes
  3. Step 1: Create a standard account for daily use
  4. Step 2: Turn on screen lock and shorten the timer
  5. Step 3: Check which apps can read your files
  6. Developer Tool Settings
  7. Step 4: Move credentials out of your shell history
  8. Step 5: Audit your package manager configs
  9. Step 6: Pin what you install
  10. Step 7: Cut browser extensions to the ones you use
  11. Backup and Recovery
  12. Step 8: Verify your backup actually restores
  13. Step 9: Write down your recovery path
  14. What to Skip

The Admin Account Habit That Costs You Later#

Open your laptop's user settings page. There is a good chance the account you use every day, the one you log into for email, banking and code, has administrator rights. That means any script, installer or malicious document you open inherits those rights too. The fix takes about ten minutes and is one of the highest value changes an ordinary computer user can make.

This checklist is aimed at people who use developer tools but are not on a security team. No enterprise setup required. Do these in order and stop whenever a step doesn't apply to you.

Account and Login Changes#

Step 1: Create a standard account for daily use#

On Windows, go to Settings, Accounts, Other users, and add a new local account. Choose "Standard user." On macOS, open System Settings, Users and Groups, add a user, and leave "Allow user to administer this computer" unchecked. On Linux, add a user without sudo group membership.

Log out and log back in as the standard account. You will need to type an admin password when installing software. That interruption is the point: it forces a pause before anything changes system files.

Step 2: Turn on screen lock and shorten the timer#

Set the lock to trigger after five minutes of inactivity. On macOS this lives under Lock Screen. On Windows it is under Sign-in options. On Linux, check the screensaver settings in your desktop environment. A laptop left open in a coffee shop is an unlocked admin console if you skip this.

Step 3: Check which apps can read your files#

On macOS, open Privacy and Security and review Files and Folders plus Full Disk Access. Remove anything you do not recognize. On Windows, check Settings, Privacy and security, App permissions. Terminal apps and code editors often request broad file access. Grant it only where you actively need it.

Developer Tool Settings#

Step 4: Move credentials out of your shell history#

Run history | grep -i token or history | grep -i key in your terminal. If anything sensitive shows up, that file is a liability. Clear it with history -c and change your shell config to stop writing secrets to disk. Better still, use a credential helper or a local secret store instead of pasting tokens into commands.

Step 5: Audit your package manager configs#

Check ~/.npmrc, ~/.pip/pip.conf and any global config for private registry tokens. If a token sits there in plain text, rotate it and switch to an environment variable or OS keychain. Package install scripts run with your permissions, and a leaked registry token lets someone publish under your name.

Step 6: Pin what you install#

Where your tooling allows, install from a lockfile rather than a floating version range. A dependency that updates silently overnight is a change you did not review. This applies to language packages, editor extensions and CLI tools alike.

Step 7: Cut browser extensions to the ones you use#

Open your browser's extension list and remove everything you have not touched in a month. Extensions that read page content can see your banking session if you let them. Two or three well chosen ones beat twenty forgotten installs.

Backup and Recovery#

Step 8: Verify your backup actually restores#

A backup you have never restored is a guess. Pick one small folder, restore it to a temporary location, and open a file. Do this today. Then confirm the backup runs on a schedule rather than when you remember.

Step 9: Write down your recovery path#

If your disk fails tomorrow, what is the first step? Know your disk encryption recovery key location, your backup destination, and the email address tied to your accounts. Store that note somewhere that is not the machine itself.

What to Skip#

You do not need to reinstall your operating system or rebuild every project. The standard account, the lock timer, the credential cleanup and the extension sweep cover most of the risk for most people. The rest can wait for a quiet weekend.

One caveat: some development tools assume admin rights and will complain. Deal with those case by case. The occasional password prompt is a small price for not handing every stray installer the keys to your machine.

Start with step 1. If you only do one thing today, make it the standard account.

More articles