How Crashcart writes a security plan
A Crashcart security plan is written from two things: the answers you give in a 10-minute setup conversation, and what Crashcart reads from every computer it manages. Anything it can't learn from either goes into the draft as a marked question, and the plan can't be signed until you have answered every one. An admin at your office signs it with a name, a title and a passkey, and Crashcart sends it back for review and a new signature every year, or alerts you sooner when your computers stop matching your setup answers.
This post describes what the owner sees and does at each step. If you want to write a plan yourself, the posts on writing a WISP for a tax practice and doing a HIPAA risk analysis work without Crashcart. The guide to running IT in a small office without an IT person covers where security paperwork fits among the other jobs.
Which documents does Crashcart write?
Which documents your office gets depends on the rules that apply to it, and Crashcart works those out from the information you handle. Patient records mean HIPAA. Card payments mean PCI DSS. Customers' financial information, for tax preparation, lending or accounting, means the FTC Safeguards Rule. Federal contract information means CMMC Level 1. Every office gets the CIS Controls as a baseline.
The documents, each on your Documents page:
| Document | Who gets it |
|---|---|
| Information security policies | Every office |
| Incident response plan | Every office |
| Security risk assessment | Offices under HIPAA, PCI DSS, the FTC Safeguards Rule or CMMC Level 1 |
| Yearly security review | The same four |
| Backup and recovery plan | Required under HIPAA, offered as optional to everyone else |
| Written information security plan (WISP) | Tax and accounting firms and others under the FTC Safeguards Rule, first on the Documents page |
An office with no regulated data gets the policies and the incident plan. A bakery's policies never mention patients, because the parts written for one rule drop out of documents for offices that rule doesn't cover.
What does the owner answer at setup?
Setup is a short conversation in plain language, about 10 minutes. Crashcart asks what the business does, who uses each computer, what customer information you keep and when restarts are allowed. From those answers it decides which rules apply and builds the office's IT plan.
A few answers matter most for the security documents:
- Who is in charge of the plan. A tax firm names its qualified individual, and who stands in when that person is away. It's the owner or someone else at the firm, never Crashcart.
- How many customers you hold information on. Firms under the FTC Safeguards Rule with fewer than 5,000 are excused from a written risk assessment, the testing schedule, a written incident response plan and the yearly report. Crashcart asks, and the plan then lists the parts your firm is excused from.
- Which computers are hands-off. A machine a vendor looks after, such as an X-ray PC, can be marked hands-off. Crashcart only monitors it, and the documents list it with the reason.
If you already have a plan, such as an IRS template you filled in, paste its text next to the plan on your Documents page. The draft keeps what still applies and replaces what's out of date.
What does Crashcart read from the office's computers?
Each morning Crashcart checks every computer for antivirus, firewall, disk encryption, screen locks, who has admin rights, updates, and old or weak accounts. It also finds the other devices on your office network and checks what can be reached from the internet. Once you connect Microsoft 365, it checks who has two-step sign-in there. Each week it checks your email domain's records.
A draft is built from what Crashcart knows on the day it's written:
- your setup answers and the rules that apply
- each safeguard's status today, with the computers that fail it
- every computer, including hands-off ones and why
- the network device counts and what the internet can see
- scheduled work and the decisions you've made
- help requests from the last year (not used for the policies)
- Crashcart's notes on the office, such as exceptions you approved and old software kept on purpose
- for the yearly review, the evidence log and the documents signed during the year
That's why the plan names your own computers and accounts instead of "all workstations."
What does a Crashcart security plan contain?
For a tax firm, the WISP has a section for each part of the FTC Safeguards Rule. Each safeguard section names the firm's computers, software and accounts, says what Crashcart checks and how often, and says whether it is in place today. The plan points to the risk assessment, policies, incident plan and yearly review instead of repeating them, and names the biggest open risks from the risk assessment.
We read the Safeguards Rule table on Crashcart's page for tax and accounting firms and the product documentation on October 18, 2026, and counted. The plan covers 12 parts of the rule, from the qualified individual in 16 CFR 314.4(a) to the yearly report in 314.4(i). Crashcart has a job in all 12. In 7 of them, part of the job stays with the firm:
| Part of the rule | What stays with the firm |
|---|---|
| Qualified individual, 314.4(a) | Choosing the person |
| Written plan, 314.3(a) | Reading and signing it |
| Two-step sign-in, 314.4(c)(5) | Connecting Microsoft 365 so it can be checked |
| Monitoring or testing, 314.4(d) | Saying how penetration testing is covered, since Crashcart doesn't run penetration tests |
| Staff training, 314.4(e) | Giving the training; Crashcart reminds you and keeps the record |
| Service providers, 314.4(f) | Getting each vendor's agreement signed; Crashcart keeps the list and where each one stands |
| Yearly report, 314.4(i) | Signing it |
Every document Crashcart writes has the same layout:
- a cover with the headline, a few numbers at a glance and the count of open questions
- a contents list, with the open questions listed under it
- the body, written for your office
- on the risk assessment, a "Controls checked" table of every safeguard that applies, with its status from the daily checks and your confirmations
- "What we're doing about it", with each open item as a card
- the sign-off, with the version history
The second line of every document says it isn't legal advice.
How are questions only the owner can answer marked?
Crashcart doesn't fill a gap with a guess. Anything the facts don't say, such as your insurer's breach line, whether staff were trained or which lawyer you use, goes into the text as "[To confirm: the question]". The document highlights each one where it sits, counts them on the cover and lists them under the contents.
To answer, press Edit and replace each marked question with the real answer. Each edit saves as a new draft version. Signing is refused while any question is left.
Expect a fair number on the first draft. Crashcart's build notes for October 5, 2026 record a risk assessment drafted for its own test office, set up as a small health practice, not a customer. It took 75 seconds and left 17 open questions, all of them things only the owner would know, such as where the server is kept, business associate agreements, staff training and paper records.
How is the plan signed?
An admin at your office types their full name and title, ticks "I've read this, it's true for our business, and we'll follow it." and confirms with their passkey. Only admins can sign. People with read-only access can't.
Signing does five things:
- marks this version signed and the earlier signed version replaced
- sets the next review date a year out
- records the safeguard as done, with a note naming the document, version, signer, title and date
- records a fingerprint of the exact text signed, and that a passkey confirmed the signer
- adds the signature to the record an auditor can see
The open items in "What we're doing about it" aren't part of the fingerprint, because they keep changing as the work gets done. The text you signed stays as you signed it.
How does the plan stay current when computers change?
The plan describes the office on the day it was signed, and offices change. Crashcart keeps checking every computer each day and records each change in safeguard status in the evidence log, with the date and the rule section. When your systems no longer match your setup answers, it alerts you.
New devices show up on the network map with the date they first appeared, so a laptop bought in February goes into the plan's inventory. Your own confirmations expire too. Access changes and outside scans come back every 3 months and the rest every 12, as a "Still true?" question by email and on Windows computers. Once a confirmation passes its date, the controls table shows it as "Due again" until you confirm it.
After a big change, Crashcart can redraft a document on its own. It never redrafts one that's waiting for you.
What happens at the yearly review?
A month before a signed document's review date, you get one "Time to review your ..." message, and Crashcart drafts an update starting from the signed version. You answer any new questions, read it and sign again, and the next review date moves a year out.
The yearly security review is its own document, drafted from a year of checks, fixes and decisions, the evidence log and the documents signed during the year. You sign it too. Every version of every document stays while your account is open, and a replaced version is kept six years.
What stays with the owner?
The signature is yours, and so is the responsibility. Crashcart checks the computers and drafts the documents. It is never your qualified individual. It doesn't give staff training, sign your vendor agreements or run penetration tests. Crashcart's terms say that meeting a framework remains your business's responsibility, and that Crashcart covers its part and tells you what's left.
None of the documents is legal advice, and they don't replace a lawyer. Crashcart's breach log says your lawyer and insurer guide any breach notification. If you're unsure whether a rule applies to your office, or what a contract asks of you, ask your attorney before you sign.
This is general information, not legal advice. For your situation, ask your attorney.
More in this topic
- How to run IT in a small office without an IT person
- Guest Wi-Fi on a separate network for a small office
- Windows update restart schedule for a small office
- New employee IT setup checklist
- Who should handle IT for a small office
- How to protect backups from ransomware
- Windows 10 end of support for small businesses
- Employee offboarding IT checklist
Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.