Last Wednesday, early in the morning, I checked the customer report about “the page won’t load” again
Running a small business, the scary part isn’t being busy. It’s when a website, account, or customer-data system has a vulnerability and nobody handles it. I’ve been there too: at first I thought reporting it to the platform was enough, but two months later, the problem remained. Now I don’t rush to investigate vulnerabilities myself, but I do want to understand how proper teams usually manage them.
What Project Zero changed, and who is already using it
Project Zero is Google’s internal security team dedicated to finding software vulnerabilities. Its newly announced policy allows up to 90 days before public disclosure after a report reaches the vendor. If the vendor releases a fix, there’s no need to wait for the full 90 days. It isn’t a universal safety net for individual founders; it’s a deadline for large software companies.
I know a friend, Xiaolin, who builds a customer administration system. In Yuhang District, Hangzhou, he maintains an appointment tool for four clinics. During a security review in November 2026, he found a risk in an old version. After contacting the software author, the initial response was: “We’ll handle it in the next release.” Xiaolin later learned that external security teams were applying similar rules to collaboration: leave room for a fix before considering public disclosure. His lesson was simple: if nobody tracks the deadline, a promise is easy to forget.
The cost of following this today is manageable
Money: Reading the public policy and finding vendor contact channels costs $0. Hiring an external security professional for a small personal project usually isn’t covered by a few hundred dollars, and quotes vary widely, so I wouldn’t rush to buy.
Time: I’d spend 30 minutes listing the websites, plugins, domains, and customer-data entry points I use.
Technical barrier: Coding skills aren’t required, but I need to distinguish the services I use daily from whoever is responsible for maintaining them.
First step: Open Project Zero’s disclosure policy page, read around the section mentioning “90 days from initial report,” then create a table with asset name, owner, date of the last check, and next step.
Here’s how I’d approach it by stage
If I’m just starting with a personal website, I’d first turn on two-factor authentication, automatic updates, and customer-data backups. I wouldn’t touch complex security services yet. Not testing now is fine; I can bring in a professional when there’s a clear business risk.
If I already have one or two clients, I’d document who handles updates for each customer system. When an issue appears, I’d record the date found, the date the vendor was notified, and the promised fix date. Not everyone needs this tool, and 90 days shouldn’t be treated as identical for every kind of issue.
If I’m scaling and my team is taking over different projects, I’d put vulnerability-handling deadlines into vendor and developer workflows, then review overdue items regularly. I’ve also mistaken “the vendor has been notified” for “someone is actively fixing it”—that distinction is surprisingly easy to miss. Inviting a technically knowledgeable friend to review the checklist with me is more practical than worrying alone.