Softechinfra
Business

Post-Diwali, Pre-GSTR-3B: 9 Cyber-Hygiene Checks Indian SMBs Almost Always Skip in Festive-Recovery Week

Written after Diwali week in late October 2025, with GSTR-3B for October due 20 November 2025. Patch backlog is a week behind, off-boarding gaps are a fortnight behind. The 9 cyber-hygiene checks Indian SMBs almost always skip in festive-recovery week.

Softechinfra EditorialSoftechinfra Editorial
May 15, 202614 min read
Post-Diwali, Pre-GSTR-3B: 9 Cyber-Hygiene Checks Indian SMBs Almost Always Skip in Festive-Recovery Week

Diwali week wrapped on October 21, 2025. GSTR-3B for the October period was due on 20 November 2025. The intervening four weeks are when Indian SMBs traditionally let cyber-hygiene slip — staff returning in waves from holiday, the patch backlog has accumulated, off-boarding from late-September departures is still pending, vendor renewals quietly auto-charged through the festive shutdown without anyone noticing. This is the post-Diwali, pre-GSTR-3B sprint we run with clients — 9 checks, roughly 4 hours total, almost always finds something nobody knew was open.

9
Cyber-hygiene checks in this sprint
4 hrs
Total time to complete for a 30-person SMB
Nov 20
GSTR-3B filing deadline (October period)
2-3
Items typically found open per audit (out of 9)

The 60-second answer

Run nine checks: patch backlog, leaver off-boarding, dormant SaaS subscriptions, expiring SSL/domain renewals, abandoned shadow IT from Diwali sales campaigns, post-festive backup verification, after-hours admin logins during the shutdown window, vendor invoice anomalies, and the tax-portal MFA refresh. Each is a 15-30 minute task. Expect to find at least a couple of open items. A typical expensive miss is a leaver's IAM role left live for weeks: even if the access logs show nobody used it, it could just as easily have been an attacker.

Why this matters now

The festive-recovery period is the highest-risk hygiene window in the Indian SMB calendar. Three structural reasons:

First, the Diwali week itself has minimum staffing, so any incident in that window often gets logged but not acted on. The triage backlog accumulates.

Second, the rush of campaign launches in the 2 weeks before Diwali typically introduces shadow IT — a marketing team signs up for a new analytics tool, sales for a new outreach platform, support for a new chat widget. Most of these never get reviewed, and some never even get used after Diwali.

Third, and most underrated: the staff calendar is fragmented. Some teams returned Oct 22, some returned Oct 27, some have not returned by Nov 5. Joiners and leavers in the gap window slip through the off-boarding process. October leavers' IAM roles, GitHub access, Slack accounts often stay live until the December audit.

GSTR-3B on November 20 is the natural forcing function — by then your accounting team is reconciling October, and the cyber-hygiene sprint should be complete so the books are clean.

The 6-week leaver-account problem. Industry data suggests about 50% of departing employees retain some form of access for over a month after leaving. For a typical 30-person Indian SMB, that translates to 1-3 forgotten access grants per quarter. The cost is bounded only by what those accounts can do — and "ex-employee with valid GitHub PAT" is a category that has produced six-figure rupee incidents in our consulting practice.

The 9 checks (in priority order)

1
Patch backlog
OS, browser, CMS, framework, container image patches that landed during Diwali week. Apply criticals immediately. Document the rest with target deadlines.
2
Leaver off-boarding
Every employee who left between Oct 1 and today: confirm IAM, GitHub, Slack, Google Workspace, Microsoft, ESP, and CRM access has been fully revoked.
3
Dormant SaaS subscriptions
Subscriptions that auto-renewed during the festive shutdown but nobody is using. Cancel before next billing cycle.
4
SSL and domain renewals
Any SSL certificate or domain expiring between Nov 1 and Dec 31 — renew now while staff is back. Expiries during November-December festive shutdowns are an annual disaster pattern.
5
Shadow IT from Diwali campaigns
Audit the SaaS apps signed up for during the campaign rush. Determine which to keep, which to off-board, which to bring under proper governance.
6
Backup verification
Confirm backups ran nightly through Diwali week (often missed because the backup admin took leave). Run one full restore test on a tier-1 system.
7
After-hours admin login review
Pull admin login logs from Oct 19-21 (Diwali days). Anything that looks unusual — a login from an unfamiliar IP or country, a login at 3 AM IST when the team was off — gets investigated immediately.
8
Vendor invoice anomalies
Review vendor invoices received during the festive window. Phishing emails impersonating vendors with payment-update requests are common — verify any new bank-account changes via voice call.
9
Tax-portal MFA refresh
GST portal, IRP, e-Way Bill — re-confirm MFA still works for every authorised user. Stale OTP-via-SMS configurations are a common pre-3B surprise.

The 4-hour walkthrough

Block 4 hours one morning the week of Oct 27-31. One founder/CTO + one engineer + one ops person. Coffee, a Notion doc, a fresh checklist. Each step has a verification before moving on.

1
Hour 0-0:30: Patch backlog scan
Run your endpoint patch-management report (Intune, Jamf, ManageEngine). List devices missing updates from the last 14 days. Push criticals immediately. Document non-criticals with 7-day deadlines. Run the same on servers (apt list --upgradable, yum check-update). Verify: a patch-status report showing zero criticals open and a documented plan for non-criticals.
2
Hour 0:30-1:00: Leaver off-boarding
Pull HR list of every departure since Oct 1. For each, run through your off-boarding checklist: Google Workspace deactivated, Microsoft 365 deactivated, GitHub org access removed, Slack deactivated, AWS IAM role disabled or deleted, CRM access revoked, ESP access revoked, VPN access removed. Verify: for each leaver, every row checked. Most SMBs find 1-3 missed items per audit.
3
Hour 1:00-1:30: SaaS subscription audit
Pull the corporate-card statement for October. List every recurring SaaS charge. Map each to a current active user/team. Anything that did not get used in October: cancel before the November charge. Verify: a list with "keep / cancel / under-review" decisions for each subscription, owner assigned for each.
4
Hour 1:30-1:45: SSL and domain renewals
Run an SSL expiry scan (sslshopper.com, ssllabs.com). List domain registrations and their expiry. Renew anything expiring before Dec 31 today. Verify: no SSL or domain expiring before Dec 31 without a renewal in process. SSL expired during a customer's December campaign in 2023 — never again.
5
Hour 1:45-2:15: Shadow-IT discovery
Ask each functional lead: "What new SaaS tool did your team start using between Oct 1 and Oct 21?" Capture the list. For each: is it processing customer data, does it have OAuth integration with our core stack, is there a DPA in place, who owns it. Verify: a list with one named owner per tool and a "bring-under-governance / keep-as-is / off-board" decision.
6
Hour 2:15-2:45: Backup verification + restore test
Confirm backup jobs ran every night Oct 18-26 (often the backup admin took leave; jobs may have failed silently). Pick one tier-1 system; restore yesterday's backup to a separate environment; confirm it works. Verify: 9/9 nights of backups present, one successful restore test signed off.
7
Hour 2:45-3:15: After-hours admin login review
Pull admin login logs from Google Workspace, Microsoft 365, AWS Console, GitHub org, your CRM, and your support tool — for the dates Oct 18-22. Filter for: logins from unfamiliar IPs/countries, logins between 11 PM and 6 AM IST, MFA failures followed by success. Verify: every flagged login has a confirmed-OK explanation OR is being investigated as a potential incident.
8
Hour 3:15-3:45: Vendor invoice anomalies
Review every vendor invoice received between Oct 15 and today. Flag: new vendors not in your master list, existing vendors with changed bank details, invoices with amounts significantly different from baseline, urgency language ("pay today to avoid disconnection"). For any flagged invoice, voice-call the vendor's known phone number to verify. Verify: every flagged invoice has a verification record.
9
Hour 3:45-4:00: Tax-portal MFA refresh
Sign into the GST portal, IRP, and e-Way Bill portal. Confirm MFA works for every authorised user. Re-test from any device that has not been used since before Diwali. Confirm the registered mobile number receives the OTP. Verify: every authorised user can sign in with MFA on a clean session.

The 4-question SaaS-license sanity audit (within step 3)

Within the SaaS-subscription audit, ask 4 specific questions for every paid SaaS:

Question What it surfaces
How many seats are paid vs. used in the last 30 days? Stale seats from leavers, trial users still on payroll seats, double-purchases
What is the renewal date and the auto-renewal terms? Avoid surprise renewals; many vendors auto-renew without notice 30 days before
Is this on annual or monthly billing — and which is cheaper at our usage? Annual is typically 15-25% cheaper; many SMBs default to monthly out of inertia
Could a smaller plan or a competitor at lower price serve us? Right-sizing; no need to be on Enterprise tier if Pro tier covers your use case

These four questions in aggregate often save Indian SMBs 15-30% of their SaaS spend. The festive-recovery sprint is the natural moment to ask them — books are being closed for October, the team is reviewing the budget anyway.

Common mistakes (each one hurts)

Symptom: "We finished the audit but never wrote down the action items." Cause: the audit ran in conversation, not in a doc. Fix: do the audit in a Notion or Google Doc, with each finding and owner captured live.

Symptom: "Two leaver accounts are still active." Cause: off-boarding checklist is not the source of truth — HR has it, IT has a separate one, neither is complete. Fix: one master off-boarding checklist, owned by IT, signed off by HR for each leaver.

Symptom: "We did not catch the auto-renewed subscription." Cause: corp-card statement was not pulled in time. Fix: the audit happens in the same week the October corp-card statement closes — typically Nov 1-3.

Symptom: "An ex-employee's GitHub PAT was used to push code." Cause: PATs persist after the user account is deactivated unless explicitly revoked. Fix: include "revoke all PATs" in your off-boarding checklist AND run a quarterly org-wide PAT audit.

Symptom: "The SSL renewal failed during December." Cause: the renewal happened automatically but DNS-01 challenge failed because the DNS provider had changed. Fix: monitor SSL expiry from outside your stack (sslshopper alerts, BetterStack); test renewal automation quarterly.

When NOT to do all 9 checks

If you ran a full IT audit within the last 30 days, skip steps 1, 2, 3, 5 — focus on the festive-specific items (4, 6, 7, 8, 9). If your team is fully on the books and you had no Diwali shutdown (rare for Indian SMBs but possible for global teams headquartered in India with non-Indian operating hours), the after-hours review is less material.

If you are a sole-founder business with no employees besides yourself, off-boarding and shadow-IT do not apply. The 9 checks become 5: patch, SSL/domain, backup, vendor anomalies, tax-portal MFA. Roughly 90 minutes total.

The GSTR-3B trap. If your tax-portal MFA refresh fails on Nov 18-19 (the day before deadline), you will be unable to file on time. Late filing of GSTR-3B incurs interest at 18% per annum on tax dues plus a late fee of up to ₹5,000 per return per Act (CGST + SGST = ₹10,000 in practice). The 15 minutes of MFA refresh on Oct 28 prevents this. Do not skip step 9.

The post-Diwali sprint checklist (print this)

  • All endpoints patched; criticals zero, non-criticals scheduled within 7 days
  • Every leaver since Oct 1 has 100% of access revocations confirmed
  • Corporate-card statement reviewed; auto-renewed unused SaaS cancelled
  • Zero SSL or domain expiries before Dec 31 without active renewal
  • Shadow-IT inventory complete; each tool has a named owner and a governance decision
  • Backup jobs verified for Oct 18-26; one successful restore test signed off
  • Admin login logs Oct 18-22 reviewed; every anomaly explained or under investigation
  • Vendor invoices Oct 15-onward reviewed; bank-detail changes verified by voice call
  • GST portal, IRP, e-Way Bill MFA tested for every authorised user from a clean session
  • Action-item tracker with owners and due dates committed to a shared doc

Example: a 42-person D2C e-commerce SMB

    Take a hypothetical 42-person D2C e-commerce SMB coming out of a Diwali sale that spiked its AWS bill and added several new SaaS tools. Here is what the 9-check sprint could find:
  • Unpatched browser vulnerabilities on staff laptops. Push the patches the same hour.
  • A September leaver who still has Slack access and a GitHub PAT with repo:write scope. Revoke both.
  • SaaS subscriptions that auto-renewed during Diwali week and nobody uses. Cancel them.
  • An SSL certificate due to expire during a planned year-end campaign. Renew it now.
  • New tools added for the sale (shadow IT). Keep the useful ones, bring any tool holding PII under governance, cancel the rest.
  • Backup nights that failed silently because the storage target was nearly full. Clean up and turn on auto-pruning.
  • Admin logins from unfamiliar IPs at 3 AM during the shutdown. Often these turn out to be a founder logging in while travelling, but verify each one.
  • Vendor invoices with changed bank details. Confirm every one by voice call. (The voice-call discipline is the hardest one to maintain; people skip it because it feels paranoid. It is not.)
  • A GST portal user who changed phones during Diwali and no longer gets the OTP. Update the registered mobile before the filing window.

The sprint costs about a founder day, an ops day and an engineer half-day. Not doing it costs at minimum the late fee on GSTR-3B, and at maximum a serious incident from any of the open items.

For background on the broader regulatory pressure, see our piece on the DPDP Act pre-notification readiness audit. Privacy posture is the regulatory cousin of operational hygiene.

A founder note from our team

Our founder Vivek Kumar writes about cybersec specifically for Indian SMB founders. The shortest version of his argument on hygiene sprints: most cyber-incidents in SMBs come from accumulated debt — patches not applied, leavers not off-boarded, subscriptions not reviewed — rather than novel attacks. The fix is calendar discipline, not better tools. Quarterly hygiene sprints prevent more incidents than expensive new platforms.

The festive-recovery sprint specifically maps to a moment in the calendar where the team's natural focus is back on the books (GSTR-3B is a forcing function). Pairing the cyber-hygiene check with the financial close is the cheapest way to make hygiene routine.

For complementary reading on operational discipline, see our recent AWS US-EAST-1 outage post from the Diwali eve and the Diwali phishing hardening checklist from the week before. Together they form a complete "before, during, after" Diwali cyber-hygiene cluster for Indian SMBs.

The Reddit pulse

The r/sysadmin threads each post-festive period (post-Christmas in the West, post-Diwali in India) document the same patterns: missed patches, forgotten leavers, surprise auto-renewals, expired certificates. The festive-recovery sprint is a global discipline; only the festival changes.

The r/india threads in early November typically surface phishing-impact stories from the Diwali sales window — a useful pulse for what scams actually landed on consumers, which informs your customer-comms going forward.

The r/IndiaTax threads in mid-November are full of last-minute GSTR-3B panic — most preventable with the MFA refresh in step 9 done 3 weeks earlier.

FAQ

Why the post-Diwali, pre-GSTR-3B window specifically?

The team is back on the books, the financial close is forcing attention to October, the Diwali noise is just past, and there are still 3 weeks before the Nov 20 GSTR-3B deadline. This is the natural moment when the muscle for hygiene work is available. Outside this window, the discipline atrophies.

Should we do this sprint quarterly or annually?

Quarterly is ideal. Annual is the minimum acceptable cadence. The 9 checks above can be run in any quarter — adapt the festive-specific items (after-hours review, vendor invoice anomalies in the festive window) to your quarter's calendar.

What if we have an MSP — do they not do this for us?

Most MSP contracts cover patches and backup verification. Few cover off-boarding, shadow-IT discovery, vendor invoice anomalies, or tax-portal MFA. The 9-check sprint is mostly the ops/finance/IT cross-functional work that lives between the MSP scope and the in-house team. Do not assume your MSP covers it; check the contract.

How do we make the off-boarding checklist actually work?

One master checklist (Notion or Google Doc), owned by IT, with HR sign-off as part of the offer-acceptance and exit-interview process. Every line item gets checked off with a name and timestamp. Any line item that cannot be checked within 24 hours of the last working day gets escalated to the founder. Most off-boarding fails because nobody owns the checklist; assign ownership.

What is the cost of a forgotten leaver-account in practice?

The range runs from nothing (no abuse, the audit catches it before any damage) to a very large bill (an ex-employee uses a forgotten GitHub PAT to push malicious code that takes weeks to detect and roll back, then needs incident response and customer notification). The expected value of a forgotten leaver-account is low but the variance is high. The cost of preventing it (15 minutes per leaver) is minimal.

How do we handle the vendor-invoice voice-call discipline at scale?

It only applies to invoices with bank-detail changes or invoices from new (not previously paid) vendors. For a typical 30-person SMB, that is 2-5 invoices a month. At your AP team's standard productivity, the voice-call adds 5 minutes per invoice — entirely manageable.

What is the right shadow-IT discovery cadence?

Quarterly is standard. After major events (Diwali sales, year-end campaigns, product launches) is mandatory. The audit pattern is the same: ask each functional lead what new tools they started using; map to data sensitivity; decide on governance.

Is there a tool that automates this whole sprint?

Partially. SaaS spend management (Vendr, SaaSOptics, Cleanshelf) covers steps 3 and parts of 5. Patch management (Intune, Jamf, ManageEngine) covers step 1. Off-boarding automation (Okta Lifecycle Management, BetterCloud) covers step 2 if you have an IdP. None of these is a substitute for the 4-hour sprint discipline — the sprint is the moment where humans review the automation output and catch what the tools missed.

Want a post-festive cyber-hygiene sprint?

We run the 9-check post-Diwali sprint for Indian SMBs (10-100 employees). You leave with: full audit results, gap analysis, prioritised remediation list with owners, and a quarterly recurring calendar for the discipline. First call is with the engineer who would lead the sprint. Suitable for SMBs with revenue ₹2-50 cr.

Book a 20-min Call
Tags:
Cyber HygienePost-DiwaliGSTR-3BSMB SecurityOff-boardingShadow ITPatch Management
Share this post:
Softechinfra Editorial

Softechinfra Editorial

Articles published by Softechinfra without a personal byline.

How we pick topics, use AI, check claims and correct mistakes: our editorial policy.