Skip to content

Lost money to a cyber fraud? Call 1930 now and file at cybercrime.gov.in. The first hour matters.

What to do, step by step →
Cyber Crime Help Desk An initiative from Kramate for Society
Business security Complete guide 6 min read

Cyber Security for Small Business in India: Starter Guide

Cyber security for small business India owners can actually do: ten controls in order, CERT-In and DPDP duties, and what the bank will not refund.

By Editorial team, Research and writing · Published
Colleagues around a meeting table reviewing documents and laptops together

In short

  • Three attacks account for most small-business losses in India: invoice and vendor-bank-change fraud, ransomware through a reused password or exposed remote access, and theft of portal credentials (GST, bank, email).
  • Ten controls, done in order, cover the bulk of the risk; the first four (MFA, backups, patching, a payment-verification rule) cost almost nothing.
  • The CERT-In directions of 28 April 2022 require incidents to be reported within six hours and logs kept for 180 days; this applies to small companies too.
  • The DPDP Act 2023 applies to any business processing personal data digitally, with penalties up to ₹250 crore; customer and employee data both count.
  • A payment your staff authorised to a fraudster is not an "unauthorised transaction" in the bank's eyes; the RBI zero-liability rule will not rescue a BEC loss. Prevention is the only defence.

Who this is for: Owners, partners and managers of Indian businesses with 5 to 200 staff: MSMEs, CA and law firms, clinics, schools, startups, traders.

The attacker who hits a 30-person trading firm in Surat does not use a zero-day. He sends an email that looks like it came from the firm's biggest supplier, with a new bank account for the next payment. Or he logs into the remote desktop with a password the owner also used on a shopping site. Cyber security for small business India owners can actually implement starts from that reality, not from enterprise frameworks.

This guide is the starter version. It gives the three attacks that cause most losses, ten controls in the order to do them, the legal duties that now apply to every business, and an honest account of what the bank will and will not do afterwards. Deeper guides are linked where they exist.

The three attacks that hit Indian small businesses

Invoice and vendor-bank-change fraud. Someone compromises a supplier's email, or yours, reads the invoice flow for weeks, then sends a plausible message: "we have changed banks, please use the new account". The accounts team updates the master and the next payment goes to a mule account. It is the single most expensive thing that happens to Indian SMEs, and our BEC explainer shows the script line by line.

Ransomware. An attacker gets in through a remote-access port left open to the internet, a reused password, or an email attachment, encrypts the file server and the Tally data, and demands payment. The backups are on the same network and are encrypted too. The ransomware playbook covers the response; this guide covers not needing it.

Portal credential theft. Phishing aimed at the person who files GST returns, logs into the bank's corporate portal or manages the company's Google account. With those, an attacker can divert refunds, add beneficiaries or read every email. Sector-specific versions exist for CA and law firms, whose clients' portal credentials are the prize.

Cyber security for small business India: ten controls in order

Do them in this order. The first four need no budget and no IT staff. Stop when you run out of time and resume next week; the order is the point.

The ten controls

  • 1. Multi-factor authentication on email, the bank portal, the GST login, the cloud drive and remote access. Authenticator app, not SMS, wherever offered.
  • 2. Backups that are offline or immutable, covering the file server, Tally or ERP data and email, tested by actually restoring a file every month.
  • 3. Automatic updates turned on for Windows, browsers, routers and any server; unsupported software replaced.
  • 4. A written payment-verification rule: no new beneficiary, no bank-account change and no "urgent" transfer without a phone call to a number already on file, and two people for anything above a threshold you set.
  • 5. A password manager for the business with shared vaults, and unique passwords for every portal; no password in a WhatsApp group.
  • 6. Remote access closed to the internet; VPN with MFA if staff need it; RDP never exposed directly.
  • 7. Least privilege: staff accounts are not administrators; the owner's day-to-day login is not the admin login.
  • 8. Email protection: SPF, DKIM and DMARC published for your domain, and a warning banner on external mail. Setup guide here.
  • 9. Offboarding on the day: access removed, shared passwords rotated, devices returned, when anyone leaves.
  • 10. A one-page incident plan: who calls whom, the CERT-In form, the 1930 number, the bank's fraud line and the insurer, printed and kept outside the computer.

Control 4 deserves a paragraph because it is a rule, not a product. Every vendor-bank-change fraud and every "CEO needs an urgent transfer" fraud is defeated by a phone call to a number you already had. Write the rule, train the accounts team on it, and make it clear that the owner expects to be called back even when the owner is the one apparently asking. Employee awareness training exists mostly to make that rule a reflex.

CERT-In directions, 28 April 2022

Under section 70B(6) of the IT Act, CERT-In issued directions that apply to all service providers, intermediaries, data centres, body corporates and government organisations. Three obligations matter to a small business: report listed types of cyber incident (ransomware, data breaches, unauthorised access, phishing of your accounts, website defacement and others) to CERT-In within six hours of noticing them; keep system and network logs for 180 days, within India; and synchronise system clocks with NIC or NPL time servers. Non-compliance is punishable under section 70B(7). The CERT-In reporting guide explains who reports what and how, and our compliance service sets up the logging and the reporting process.

DPDP Act 2023

If your business processes personal data digitally, which covers customer records, employee files, CCTV and a WhatsApp group of patients, you are a data fiduciary under the Digital Personal Data Protection Act, 2023. You must process data for a lawful purpose with notice and consent, protect it with reasonable safeguards, notify the Data Protection Board and affected individuals of a breach, and delete data when the purpose ends. Penalties can reach ₹250 crore for serious failures. The DPDP compliance checklist is the practical version, and DPDP compliance support handles it for firms without a legal team. Schools and clinics have additional duties around children's and health data, described on the schools and hospitals pages.

When something happens anyway

Print this sequence and keep it with the incident plan. Isolate the affected machine or account first: unplug the network cable, revoke the session, change the password from a clean device. Call 1930 if money has moved, with the transaction details and the receiving account. Report to CERT-In within six hours using the incident reporting form and email on cert-in.org.in. Tell the bank in writing. Preserve logs and the affected machine rather than reinstalling it. Then, and only then, start investigating. If an insurer is involved, notify them within the policy window; cyber insurance claims fail on late notice more than on anything else. For a live incident where you need people who have done this before, incident response is available on an emergency basis.

Beyond the starter list

Once the ten controls are in place, three things are worth paying for. A vulnerability assessment and penetration test once a year, scoped to what you actually run, finds the exposed remote access and the forgotten web application before an attacker does; VAPT explains what you get. Email security hardening addresses the channel through which most fraud arrives. And for a growing firm without a security hire, a fractional CISO gives you someone accountable for the programme at a cost a small company can carry. Startups facing investor or customer questionnaires, and manufacturing units with OT on the office network, have sector pages with the specifics.

Start this week with controls 1 to 4. They take an afternoon, cost nothing, and remove most of the risk described above. Put the one-page incident plan on the wall by Friday. The rest can follow over a quarter, and if you want it done with you, a scoping call is where our business services begin.

Frequently asked questions

We have 20 staff and no IT person. Where do we start?

With the four controls that need no IT person: multi-factor authentication on email and the bank, an offline backup that someone tests monthly, automatic updates turned on everywhere, and a written rule that no bank-account change or urgent payment is actioned without a phone call to a known number. Those four stop most of what hits businesses your size.

Does the CERT-In six-hour rule really apply to a small firm?

Yes. The directions of 28 April 2022 apply to service providers, intermediaries, data centres, body corporates and government organisations, with no size threshold. If you notice a ransomware infection, a data breach or a compromised email account, you must report it to CERT-In within six hours of becoming aware. Keep the form and the email address ready before you need them.

Will the bank refund money our accountant sent to a fraudster's account?

Usually not. The RBI limited-liability circular covers unauthorised transactions. A transfer your staff initiated and authorised, even under deception, is treated as authorised. Call 1930 immediately so the receiving account can be frozen; that is the realistic recovery route. Some business insurance policies cover social engineering losses, with sub-limits.

Is cloud (Google Workspace, Microsoft 365) safer than our own server?

For a small business, almost always. The providers patch, back up and monitor better than a part-time IT vendor can. The risks move to the account level: weak passwords, no MFA, over-shared drives and a departed employee whose login still works. Secure the accounts and the cloud is a good trade.

How much should a small business spend on security?

We do not quote figures because they depend on what you run. The honest answer is that the first ten controls cost mostly time and a few subscriptions. Paid help makes sense for a vulnerability assessment once a year, an incident response retainer if downtime would be severe, and DPDP or CERT-In compliance if you hold significant personal data.

If you want help with this

Talk to us
E

Written by

Editorial team

Research and writing