Skip to main content
Blog
Back to Blog

Solopreneur cybersecurity: NIST's guide as a checklist

On November 2, 2026, NIST published a cybersecurity guide written for solopreneurs: businesses whose only paid worker is the owner. It is sound, but it is a 33-page white paper organized around a federal framework, and the first reaction on Hacker News was a request for a short, practical version. This is that version for a solo founder running a software or online business. It covers what to secure first and why, an afternoon checklist mapped to NIST's actions, an account inventory you can copy, how to review the apps and AI tools connected to your accounts, backups, a one-page incident card and a short security note for your first business customers. It is useful without a Soloop account and is not legal or compliance advice.

The short answer

Secure your email account first, because it can reset every other account you own. Then protect your password manager, domain, code host, payments and cloud accounts with passkeys or an authenticator app, list every account and connected app in one place, keep a backup that is not connected to your computer and test restoring it, and write down who to call before anything goes wrong.

That covers most of what NIST lists as the first actions for a one-person business. The rest of its guide, from insurance to supplier contracts, matters as you sign larger customers, and you can work through it later.

What NIST published

NIST Cybersecurity White Paper 50, Small Business Cybersecurity: Non-Employer Firms, replaces the older small business guide NISTIR 7621 and narrows it to the smallest firms. It draws on the Cybersecurity Framework 2.0 and organizes 22 actions under six functions: Govern, Identify, Protect, Detect, Respond and Recover. Each action has a reason, a way to start and what to add as the business grows. A separate spreadsheet holds worksheets and three hypothetical businesses: an intellectual property attorney, a maker selling online from a home workshop and a marketing consultant.

NIST itself says its tables are not a checklist or compliance criteria, so the checklist below is an editorial selection for a software founder, not an official one. NIST also uses the term "super intelligence (SI)" for AI, following a September 29, 2026 executive order; this guide says AI.

Release

Published November 2, 2026, as a lay-language guide for solopreneurs; replaces NISTIR 7621 with a narrower scope; includes worksheets and three hypothetical use cases.

NIST news release
Audience

Of 34.8 million U.S. small businesses, 81.9% have no paid employees other than the owners; the guide covers sole proprietors, freelancers, single-member LLCs, independent contractors and gig workers.

NIST CSWP 50, Introduction
First actions

Phishing-resistant MFA on sensitive accounts; recognizing phishing and ransomware; standard rather than administrator accounts; passphrases of at least 15 characters, a password manager or passkeys; an inventory of key assets; protected, tested backups; updated software; an offline contact list for incidents; a list of legal, regulatory and contractual requirements.

NIST CSWP 50, section 1.1

What to secure first, and why

A solo software business usually runs on a dozen cloud accounts, and they are not equally important. Start with the accounts that can reset or impersonate the others, then the ones that hold money and customer data.

Accounts in the order a solo founder should secure them
DimensionWhy it comes hereFirst move
1. Primary emailPassword resets for almost everything arrive here, and customers trust mail from it.Turn on a passkey or authenticator app, save the recovery codes offline and check forwarding rules and signed-in devices.
2. Password managerIt holds every other credential.Use a long unique passphrase plus a second factor, and keep its recovery kit on paper.
3. Domain registrar and DNSWhoever controls the domain controls your email, website and sign-in links.Turn on MFA and the registrar lock, and make sure renewal notices reach an address you read.
4. Code host and cloudSource code, deploy keys and customer data live here.MFA on GitHub and your hosting or cloud console; remove old keys, tokens and unused projects.
5. Payments and bankDirect financial loss and payout redirection.MFA, payout and login alerts, and confirm any change to bank details through a known contact.
6. Social, ad and outreach accountsYour public voice and ad spend; a takeover can post or spend in your name.MFA, review connected apps and remove the ones you no longer use.
7. AI tools and agentsThey may read your files, mail or code and act through your accounts.List what each can access, check data retention and training settings, and revoke what you do not use.

The afternoon checklist

Each item names the NIST action it comes from. Do them in order; stop when the afternoon runs out and continue next week.

  • Write down every account the business depends on, using the inventory below (Identify: asset inventory).
  • Turn on passkeys or an authenticator app on email, password manager, registrar, code host, cloud, payments and bank, and store recovery codes offline (Protect: MFA and password managers).
  • Replace reused or short passwords with unique passphrases of at least 15 characters from a password manager (Protect: first actions).
  • Use a standard, non-administrator account on your laptop for daily work and keep family members on separate accounts (Protect: least privilege).
  • Turn on automatic updates for your operating system, browser and phone, and change the default password on your router (Protect: patching and default passwords).
  • Review apps and AI tools connected to Google, X, GitHub and other accounts, and revoke what you no longer use (Govern: third-party risk; NIST's AI precautions).
  • Turn on login, password-reset, payout and domain-change alerts wherever they exist (Detect: monitoring).
  • Set up a backup with at least one copy not connected to your computer, then restore one file to prove it works (Protect: backups).
  • Fill in the incident card below and keep a printed copy (Identify and Respond: incident response plan).
  • List any security terms in customer contracts, card payment rules or data laws that apply to you (Govern: legal and contractual requirements).
Protect actions

Limit access to those who need it; change default manufacturer passwords; update and patch at least monthly; take awareness training at least yearly; back up regularly with at least one copy on a medium not connected to the device and test restores; enable MFA, especially phishing-resistant MFA, and consider password managers.

NIST CSWP 50, Table 7
Detect actions

Install security software, enable logging and alerts such as new-login notifications, banking and payment alerts, tracking changes to domain records and password-reset notifications; check the physical environment and enable device tracking and remote wipe.

NIST CSWP 50, Table 8

Copy the account inventory

NIST's basic inventory asks for each asset's owner, location, sensitivity, password, MFA and recovery details. The version here adds two columns a software founder needs: the apps and AI tools connected to each account, and whether alerts are on. The recovery column catches the most common lockout, an old phone number or a personal address you no longer check.

Keep business and personal accounts apart where you can. NIST recommends minimizing the mixing of personal and business devices and accounts, and closing accounts you no longer need.

Download Markdown

Review the apps and AI tools connected to your accounts

Every "Sign in with" button and OAuth connection gives another company some access to your account. NIST's AI precautions ask you to list the AI products and integrations you use, check their data retention, training and access settings before sharing sensitive material such as source code or contracts, review AI-generated content before it reaches customers and understand how your vendors' AI reaches your systems or data. The quickest way to start is each provider's list of connected apps.

Where to review and revoke connected apps
DimensionWhere to lookWhat to do
Google Accountmyaccount.google.com/linkedapps, filtered by Sign in with Google, linked accounts, access and agent access.Select each app, check what it can reach, then Remove access or Stop using for anything you do not recognize or use.
XSettings and privacy → Apps and sessions, which lists connected apps with their permissions and your active sessions.Revoke access for unused apps and log out sessions you do not recognize; never give an app your X password.
GitHubSettings → Applications → Authorized GitHub Apps; GitHub documents authorized OAuth apps separately.Revoke apps you do not recognize or no longer use, and delete old personal access tokens and deploy keys.
AI assistants and agentsEach tool's settings for connected accounts, data retention and whether your content is used for training.Disconnect accounts the tool does not need, turn off training where your data is sensitive and require approval before it sends or publishes.
AI precautions

Inventory AI products and AI features or integrations; document related legal requirements; review privacy and security settings such as data retention, training, access privileges and confidentiality before entering sensitive information; review AI-generated content before use; understand how vendors' AI systems access business systems or data.

NIST CSWP 50, section 1.9

Protect the domain your customers trust

For an online business the domain is the identity: it receives your email, serves your site and appears in every link you send. Turn on MFA at the registrar, keep the registrar lock on so the domain cannot be transferred without you, renew before it expires and turn on alerts for changes to its DNS records, which NIST lists as a detection step.

Publish SPF and DKIM for the domain you send from, and add a DMARC record. Gmail requires SPF or DKIM from every sender and SPF, DKIM and DMARC from anyone sending 5,000 or more messages a day to personal Gmail accounts. The same records make it harder for someone else to send mail that looks like it came from you.

Domain lock

A domain can be locked against unauthorized changes; the status may appear as Registrar lock or Client Transfer Prohibited.

ICANN: About Locked Domain
Gmail sender rules

All senders need SPF or DKIM and a reported spam rate below 0.3%; senders of 5,000+ messages a day need SPF, DKIM and DMARC (policy may be none), From-domain alignment and one-click unsubscribe for marketing mail.

Google: Email sender guidelines
Code host

GitHub requires 2FA for accounts selected by contributor activity such as creating releases or publishing apps or actions; an authenticator app is the primary method and passkeys or security keys are backups.

GitHub Docs: About mandatory two-factor authentication

Backups that survive ransomware

NIST notes that ransomware now reaches cloud accounts and software services as well as laptops, so a synced folder alone is not a backup: if files are encrypted or deleted, the sync copies the damage. Keep at least one copy on a medium that is not connected to your computer, check what your cloud providers back up and for how long, and protect backup accounts with MFA.

A backup you have never restored is a guess. Once a quarter, restore one file and one database export to a clean location and note the date in the inventory.

  1. List what you cannot recreate: source code, database exports, customer records, contracts, financial records and design files.
  2. Choose two places for copies, at least one not connected to your computer, and protect both with MFA.
  3. Schedule the backup and confirm the first one completed.
  4. Restore one file and one database export to a clean location and record the date.

Copy the one-page incident card

NIST asks every business to plan its response before an incident and to keep a printed or offline copy of key contacts, because the laptop or account you would use to look them up may be the one affected. For a solo founder the plan fits on one page.

The card follows NIST's Respond and Recover actions: contain the incident, document it, contact the people in the plan, communicate where laws, regulations or contracts require it, review MFA settings, sessions, file sharing and forwarding rules before reusing an account, restore from verified backups and record lessons learned.

Download Markdown
Respond and recover

Execute the incident response plan; document the incident; communicate as required by laws, regulations or policies; contain it by disconnecting devices, isolating systems and revoking sessions; verify backups before reuse; review MFA settings, user accounts, file sharing, active sessions and forwarding rules; document lessons learned. Resources include the FBI's Internet Crime Complaint Center.

NIST CSWP 50, Tables 9 and 10
Outside the U.S.

The UK NCSC's page for the self-employed and sole traders offers a free Cyber Action Toolkit, recommends passkeys over passwords where available and links its small organisations guide and Cyber Essentials.

NCSC: Advice for self-employed and sole traders

What to tell your first business customers

NIST presents good security as a way to win the confidence of customers and partners, and the first business customer often asks a version of "how do you protect our data?" before signing. A plain one-page note that states what you actually do, including what is not done yet, answers that question better than a policy copied from a large company.

Only write what is true today. Do not claim certifications, encryption settings or response times you cannot show, and update the note when anything changes.

Download Markdown

A realistic time budget

Illustrative example, not a benchmark: a solo founder with 12 important accounts spends about 10 minutes on each to add a passkey or authenticator app, save recovery codes and review connected apps, which is 120 minutes (12 × 10). The inventory takes another 30 minutes, setting up and testing a backup 45 and the incident card 15, for 210 minutes, or three and a half hours (120 + 30 + 45 + 15).

After that, the recurring work is small: install updates as they arrive, check connected apps and restore one backup each quarter, and update the inventory when you add a tool.

Where Soloop fits

Soloop is not a security product and does not audit or secure your accounts. It is one of the connected tools this guide asks you to review. According to the Soloop manual, it can research with sources, post on X after you connect it with OAuth, prepare Reddit posts for you to publish yourself, send cold email through a connected Gmail account and prepare Google Search Ads for your review and payment. Actions wait for your approval by default, and you can revoke its access from each provider's connected-apps page.

A bounded first request: I sell [product] to [buyer role] at [company type]. Research, with sources, which security questions such buyers usually ask a small vendor before a first purchase, then draft a one-page security note from my answers below. Do not send or post anything.

Sources, limitations and refresh

NIST's news release and CSWP 50, the NCSC page for the self-employed, Google's linked-apps help and email sender guidelines, X's help page on third-party apps, GitHub's documentation on authorized apps and mandatory 2FA, and ICANN's page on locked domains were read on November 4, 2026. NIST's separate spreadsheet of worksheets and use cases was not reviewed. The order of accounts, checklist selection, templates and time budget are editorial guidance; the time budget is illustrative. This is not legal, insurance or compliance advice, and following it does not certify a business.

This guide will be reviewed by February 4, 2027, or sooner if NIST revises CSWP 50 or a provider changes its connected-app or sender rules.

Product capability

The Soloop manual describes research with sources, X publishing with OAuth, Reddit preparation with manual publication, cold email through a connected Gmail account and Google Search Ads after review and payment; approval comes first by default. It does not audit or secure accounts.

Soloop product manual