NIST Cybersecurity Guide for Solopreneurs: What Founders Should Demand From the Developer They Hire

Last reviewed: February 2025. This guide reflects NIST CSF 2.0 and the current NIST Small Business Cybersecurity Corner as of that date; check the linked NIST pages for the latest revisions.
Most solopreneurs I talk to treat security as something that happens after launch, if at all. They hire a developer, ship the site or the automation, and only start asking hard questions when a client sends over a security questionnaire or a payment processor freezes an account.
I have spent the last six years building web apps and automation for founders in the USA, Australia, Canada, New Zealand and Bangladesh. I have been on both sides of this conversation: the developer being vetted, and the one cleaning up after a cheap build that leaked customer data. The pattern is consistent. Founders who ask security questions before signing get a better product, and they sleep better.
This NIST cybersecurity guide for solopreneurs is written for the founder with no IT department. You do not need a security team to use the NIST Small Business Cybersecurity Corner or the NIST Cybersecurity Framework (CSF) 2.0. You need a short list of expectations and a willingness to put them in writing.
Why a one-person business should care about NIST at all
NIST guidance is voluntary. Nobody is going to raid your home office for not following it. So why bother?
Three reasons keep coming up in real projects.
First, your clients increasingly ask. Enterprise and government buyers in the US, Canada and Australia now send vendor security questionnaires as standard procurement. If you cannot answer basic questions about encryption, access control and backups, you lose the deal before anyone looks at your portfolio.
Second, NIST gives you a shared vocabulary. When you tell a developer "encrypt data at rest and use least-privilege access," you sound vague. When you point to the CSF 2.0 functions (Govern, Identify, Protect, Detect, Respond, Recover), you sound like someone who has done this before. Developers respond differently to that.
Third, it is cheap insurance. Most of what NIST recommends for small businesses costs nothing but attention. The expensive part is the breach you avoid.
The honest truth: you are not "NIST compliant"
I want to kill a misconception early. NIST CSF is a framework, not a certification. There is no certificate that says "NIST compliant." NIST says so itself: the framework is voluntary guidance, and use of it does not establish compliance or certification. If a developer or agency tells you their build is "NIST certified," that is a yellow flag. They either do not understand the framework or they are hoping you do not.
What you can realistically do as a solopreneur is adopt the framework's structure and document how you apply it. That is often enough to satisfy a client questionnaire and, more importantly, to make your business genuinely harder to break into.
What to demand from the developer you hire
Here is the core of this guide. These are the expectations I would put in front of any developer I hire, and the ones I am comfortable being held to myself.
1. Security is scoped in writing before work starts
Vague promises ("we build secure apps") are worthless. Ask for a one-page security scope that lists what will be protected, how, and who is responsible for what after handover. If a developer cannot produce this, that tells you something.
2. Secrets are never in the codebase
This is the single most common failure I see. API keys, database passwords and payment tokens get hardcoded into a file and pushed to GitHub. Once a secret is in git history, it is compromised, even if you delete the file later.
Demand environment variables and a secrets manager. Ask to see how they handle it.
# Wrong: secret in source
const STRIPE_KEY = "sk_live_51H...";
# Right: secret from environment
const STRIPE_KEY = process.env.STRIPE_SECRET_KEY;
3. Authentication follows current standards
Passwords hashed with bcrypt or argon2 (never MD5 or SHA1), session tokens that expire, and multi-factor authentication available for admin accounts. If the build has an admin panel, MFA is not optional.
4. Data is encrypted in transit and at rest
HTTPS everywhere, with HSTS enabled. Database encryption at rest, which most managed providers (AWS RDS, Supabase, Neon) offer, but you should confirm it is turned on for your instance.
5. Third-party dependencies are tracked and updated
Every npm package is a potential vulnerability. Ask how they handle dependency updates and whether they run automated scanning. A developer who has never heard of npm audit or Dependabot is a risk. If your team leans on AI coding tools, pair this with a process for catching AI-hallucinated dependencies before they reach production.
6. Backups exist and have been tested
An untested backup is a hope, not a backup. Ask when the last restore test was. For a solo business, a daily automated backup with a monthly restore check is a reasonable minimum.
7. There is a documented handover
You should walk away with: source code access, infrastructure access, environment variable list (names, not values), a short runbook, and a description of what monitoring is in place. No lock-in, no "only we can touch it."
Contract security clauses worth insisting on
This is where founders get burned most often. The build is fine, but the contract says nothing about security, and when something goes wrong there is no recourse.
I am not a lawyer, and you should have a contracts lawyer review anything you sign. But these are the clauses I have seen work in practice, and the ones I include in my own engagements.
| Clause | What it should say | Why it matters |
|---|---|---|
| Data handling | How client and customer data is stored, who can access it, and for how long | Defines liability if data leaks |
| Confidentiality | Developer will not reuse your data, credentials or code for other clients | Prevents accidental cross-contamination |
| Security standards | Explicit reference to a recognized baseline (e.g. NIST CSF 2.0 functions, OWASP Top 10) | Gives you a benchmark to hold them to |
| Breach notification | Developer must notify you within X hours of discovering a breach | Speed matters more than perfection |
| Code ownership and access | You own the code and infrastructure; all credentials handed over at end | Prevents hostage scenarios |
| Warranty period | 30 to 90 days of bug and security fix coverage post-launch | Catches obvious mistakes before they cost you |
| Subcontractor disclosure | Developer must disclose if work is outsourced and to whom | You are buying from a person, not a mystery team |
A short, plain-English security appendix attached to the main contract is often enough. It does not need to be forty pages. It needs to be specific.
A minimum viable security checklist for your build
If you want a starter list to hand to a developer, use this. It maps loosely to the NIST CSF functions without requiring you to read the full framework.
- Govern: Written security scope and named owner (you).
- Identify: Inventory of what data you hold and where it lives.
- Protect: HTTPS, hashed passwords, MFA on admin, secrets in a manager, least-privilege database users.
- Detect: Error and access logging turned on, with alerts for failed admin logins.
- Respond: A one-page plan for what you do if a breach is suspected.
- Recover: Daily backups, tested restore, documented recovery steps.
A solo operator can genuinely get through this list in a weekend of focused work, especially if the developer has built the foundations correctly.
What "Govern" looks like in practice
Govern is the function founders skip, and it is the one that makes the rest stick. In plain terms, it means someone owns security decisions and there is a written record of them. A concrete example: before work starts, you write a one-page document that names yourself as the security owner, lists the data your product will hold (say, customer emails and Stripe payment tokens), states that payment card data never touches your servers because Stripe handles it, and sets a rule that any new third-party service must be approved by you in writing before it is added to the stack. That document takes an hour to write. Six months later, when the developer proposes adding a new analytics tool that would capture user emails, you have a rule to point at instead of an argument. That is Govern: a named owner, a data inventory, and a decision rule you can enforce.
How to vet a developer for security before you hire
When I am on the hiring side (I hire contractors for overflow work), I ask four questions. The answers tell me more than any portfolio.
- "Walk me through how you handle secrets in a Next.js app." Good answer: environment variables, a secrets manager for production, never committed. Bad answer: silence, or "we just put it in the config."
- "What does your deployment pipeline look like?" Good answer: CI/CD with automated tests, a staging environment, and a rollback plan. Bad answer: "I FTP it up."
- "Show me a recent security fix you made." Real developers have stories. Fake ones do not.
- "Who owns the code and infrastructure when we finish?" The only correct answer is: you do.
If you are hiring a Next.js developer or an automation developer, these four questions will separate the professionals from the people who watched two tutorials and started charging. For a deeper question bank you can take into interviews, see our 12 screening questions that reveal real RSC and streaming experience, and for the broader market view, the founder's guide to hiring a Next.js developer covers pricing and red flags across regions.
Regional notes: Australia and Bangladesh
NIST is a US standard, but it travels well. Two examples stand out from my own work.
In Australia, the Privacy Act and the Notifiable Data Breaches scheme mean you have legal obligations if customer data leaks, and NIST gives you a defensible process to point to when you notify. I have watched an Australian founder use exactly this: a documented CSF-aligned incident plan turned a stressful breach notification into a checklist exercise.
For founders in Bangladesh hiring local developers or agencies, the practical gap is usually process, not talent. I have worked with excellent engineers in Dhaka who simply were never asked to document security decisions. Ask for it, and most will deliver. The ones who cannot are the ones to avoid.
Where NIST is overkill, and where it is not enough
Be pragmatic. If you run a brochure site with a contact form and no user accounts, full CSF adoption is overkill. Focus on HTTPS, backups, and keeping the CMS patched. That is proportionate.
If you handle payments, personal health data, or client data under contract, you need more. That is where the NIST small business guidance earns its keep, and where you should insist your developer can speak to it.
And if you are building automation that touches client systems (CRM, email, accounting), security expectations go up again. An automation developer with access to a client's Google Workspace or HubSpot account is a privileged user. Treat them that way: scoped API tokens, audit logs, and revocation plans. If you self-host your automation stack, start with a hardened n8n deployment on a VPS with Docker, and if you are wiring AI agents into business ops, version and test their tool definitions so agent skills drift does not quietly widen their permissions.
Conclusion
You do not need a security team to demand competent security from the developer you hire. You need a short list of expectations, a written scope, and the confidence to ask questions that make a bad developer uncomfortable. The NIST cybersecurity guide for solopreneurs is, in practice, a hiring checklist disguised as a framework.
If you are planning a build, a reasonable next step is to draft your one-page security scope before you talk to any developer, then use the four vetting questions above in your first call. If you want a second opinion on that scope, or you are weighing whether a candidate can meet it, I build with Next.js, Node and AI automation and am glad to review what a right-sized security scope looks like for your project.
About the author
I am a full-stack developer with six years of professional experience building web applications and automation for founders, primarily in Next.js and Node.js. My work spans client projects in the USA, Australia, Canada, New Zealand and Bangladesh, including security cleanups of existing builds and pre-hire technical reviews. I am not a certified auditor or lawyer, and nothing here is legal advice; where the guide touches contracts or privacy law, I point you to qualified professionals. You can review my project work and client references on request before engaging me.
Frequently asked questions
Is NIST compliance required for a solopreneur?
No. NIST CSF is voluntary guidance, and NIST explicitly states that using the framework does not constitute compliance or certification. What can bite you legally is separate regulation: Australia's Privacy Act and Notifiable Data Breaches scheme, Canada's PIPEDA, or sector rules like PCI DSS if you handle card data. Treat NIST as the technical baseline that helps you meet those obligations, not as a substitute for them.
What is the difference between NIST CSF and the NIST Small Business Cybersecurity Guide?
CSF 2.0 is the organizing framework: six functions (Govern, Identify, Protect, Detect, Respond, Recover) plus categories and subcategories you map your own controls onto. The Small Business Cybersecurity Corner is a curated set of plain-language resources, templates and quick-start guides derived from NISTIR 7621, aimed at organizations without dedicated security staff. Practically, founders should start with the small business quick-start to build habits, then use the CSF functions as the structure for documenting what they did when a client questionnaire arrives.
What security clauses should I put in a developer contract?
Beyond the checklist in the table above, add two clauses founders often miss. First, a credential rotation clause: all shared passwords and API keys must be rotated at handover, so the developer retains no working access. Second, an incident cooperation clause: the developer agrees to assist with investigation and remediation for a defined period after a breach, not just notify you. Both are cheap to negotiate upfront and expensive to argue about later. Have a lawyer draft the final wording.
How do I check if a developer actually cares about security?
Move beyond interview answers to artifacts. Ask for a redacted excerpt of a past security scope document, a screenshot of their CI pipeline running dependency scanning, or a commit history showing a vulnerability patch (many developers can share a public repo example). Then test responsiveness: send one follow-up question by email and see whether the answer is specific or hand-wavy. Developers who do this work daily produce documents and links quickly; those who do not tend to pivot to portfolio talk.