Q4 Closing: A 12-Point Cyber-Hygiene Sprint Before Your FY-End Books Lock

Most Indian SMBs treat the financial-year close as an accounting event. The CA reconciles the ledgers, the auditor signs off, the books lock. Almost nobody runs a security check in the same window. That is a missed habit, because the FY-end close is the one time every year your whole team is already auditing access, payments, and vendor lists. This post gives you a 12-point cyber-hygiene sprint you can finish in two working days, mapped to the same accounts your auditor is already touching. ## What Is a FY-End Cyber-Hygiene Sprint? A FY-end cyber-hygiene sprint is a fixed checklist of security tasks you run in the same week your accounts close for the financial year. It piggybacks on work you already do at year-end — reviewing who has access to payment systems, who left the company, which vendors you still pay — and adds the security half: revoking stale logins, testing your backups, rotating exposed tokens, and patching what slipped. Two days, no new spend. ## Why Run This Now, at FY-End? India's financial year ends on March 31. That deadline already forces a clean-up: the finance team lists every active vendor, every payment approver, every bank login, every SaaS subscription on the books. Verizon's 2024 Data Breach Investigations Report found [68% of breaches involved a non-malicious human element](https://www.verizon.com/business/resources/reports/dbir/) — a stale account, a reused password, a missed patch. Those are exactly the things a year-end list surfaces. You are already doing half the work. The other half is security, and it takes the same source data. There is a second reason. Cyber-insurance renewals in 2026 increasingly ask for proof of an access review and a tested backup in the last 12 months. If your policy renews around the financial year, this sprint generates the evidence in the same window. ## The 12-Point Sprint (The Full List) Here is the whole checklist first, so you can hand it to whoever owns IT. The walkthrough below explains each one with the exact command or click path. ## How Do You Run Each Check? (The 2-Day Walkthrough) Split the work across two days. Day one is the read-and-list work: access, admins, vendors, MFA. Day two is the action work: rotations, the backup test, the patch sweep, the phishing test. A team of one IT person plus the finance lead can clear it. ## What the Numbers Say A few figures worth keeping in front of the finance lead when you ask for two days. ## When Should You Not Do This Yourself? This sprint is built for a 10-to-50-person firm with one IT-capable person. There are three cases where the DIY version is the wrong call, and pretending otherwise would be dishonest. First, if you are a regulated entity — an NBFC, a healthcare provider holding patient records, a payment aggregator — your obligations go well past a two-day checklist. You need a documented information-security policy, a named officer, and likely an external audit. Use this sprint as a warm-up, not the finish line. Second, if your access review turns up something live and bad — a former admin who still logs in, a payment key in a public repo, a backup that will not restore — stop and treat it as an incident. Do not quietly fix it and move on. Preserve the logs, change the credentials, and get help if you cannot trace the scope. Third, if nobody on your team can confidently run a database restore or read a DMARC record, do not learn it for the first time during the close week. Bring in help for the technical checks (6, 7, 8, 11) and keep the people-and-process checks in-house. ## A Real Example: A 28-Person Logistics Firm in Coimbatore A Coimbatore logistics firm — 28 staff, a custom dispatch app, Tally on a cloud server — asked us to run this sprint alongside their March close. Manvi, who leads our QA and security reviews, ran it over two days. The access review found three live accounts for people who had left in the past year, including one with full access to the dispatch database. The backup restore test took 41 minutes and worked — but exposed that nightly backups were missing the file-uploads folder entirely, so customer proof-of-delivery photos were never being saved off-server. The phishing test had 7 of 28 click a fake "courier KYC update" link. After a 25-minute session, a re-test two weeks later had one. We rotated their Razorpay keys and found an old test key still active in a staging environment. Total effort: two days. The pattern is the same one we apply on longer engagements through our automation and reliability work — and on data-heavy builds like Radiant Finance, where access discipline is non-negotiable — find the gap, prove the fix, schedule the recurrence. ## Related Reading For the founder's-eye view on why Indian SMBs keep getting caught by supply-chain and social-engineering attacks, our founder Vivek Singh writes about the same beat on his personal blog. ## Frequently Asked Questions ### How long does the 12-point sprint actually take? For a 10-to-50-person firm with one IT-capable person, plan two working days. Day one covers the list-and-review checks (access, admins, vendors, MFA). Day two covers the action checks (rotations, backup restore, patching, phishing test). Larger or more regulated firms should budget more. ### Do I need to buy any tools to run this? No. Every check works with free tiers: Google Workspace Admin reports, MXToolbox for DNS, GoPhish free tier for the phishing test, and Bitwarden free for password storage. The only cost is time. Paid tools speed up scheduling but are not required for a first run. ### Why run a security sprint at financial-year-end specifically? Because your team is already auditing access, payments, and vendors for the books close. The same lists — who can approve payments, who left, which vendors you pay — are exactly what a security review needs. Running both at once roughly halves the effort versus doing them separately. ### What is the single most important check on the list? The backup restore test (check 7). Most firms confirm a backup ran but never restore one, and a backup that fails on restore is no protection at all. Proving recovery works is the highest-value 90 minutes in the sprint. ### Is SMS-based two-factor good enough? It is better than nothing but it is the weakest second factor. SIM-swap fraud lets an attacker redirect your SMS codes. Use an authenticator app or a hardware security key for email, banking, and cloud admin accounts. Keep SMS only as a fallback. ### How does this help with cyber-insurance renewals? Insurers in 2026 increasingly ask for proof of a recent access review and a tested backup. Running this sprint and keeping the exported user lists, the restore-test log, and the patch record gives you the evidence in one folder, dated within the policy period. ### Can you run this sprint for us? Yes. We run the full 12-point sprint for Indian SMBs in two working days and hand back a one-page findings sheet plus the evidence pack. We can also schedule the recurring checks so the next FY-end is faster. Book a call below.