Cybersecurity for Small Businesses in India: A 30-Day Protection Plan

Protect your business in 30 days with an India-specific cybersecurity plan covering accounts, UPI payments, vendors, email authentication, backups, CERT-In reporting and incident response.

By InkRiver Admin

Cybersecurity for Small Businesses in India: A 30-Day Protection Plan Cybersecurity for small businesses is not mainly about buying an expensive security platform. It starts with knowing what the business depends on, deciding who owns each risk and installing a small number of controls in the right order. That matters for an Indian business whose operations may span laptops, personal phones, WhatsApp, UPI, internet banking, cloud accounting, ecommerce marketplaces, outsourced payroll and a website managed by an external agency. One compromised email account can be enough to redirect a vendor payment, reset other passwords or impersonate the founder. Threats are also becoming easier to scale. In a July 2026 statement, the Government of India said AI can enable automated reconnaissance, faster vulnerability exploitation, credential compromise and convincing multilingual impersonation. The same update described CERT-In’s use of malicious-domain detection, threat-intelligence exchange and cyber exercises to improve resilience. This is a reason to improve basic controls—not a reason to chase every new AI security product. PIB, 30 July 2026 CERT-In’s dedicated MSME guidance provides an even more practical starting point: 15 elemental cyber-defence controls supported by 45 baseline recommendations. They cover asset management, email, endpoints, patching, incident response, logs, training, vendors, backups, governance, passwords, access, data protection and vulnerability assessment. CERT-In’s MSME controls The following cyber security plan for a small business converts that baseline into 30 manageable days. Before day one: appoint an owner Name one employee as the security in-charge and one senior decision-maker as backup. This does not need to be a full-time cybersecurity hire. In a ten-person company, it might be the operations head, founder or technically capable administrator. The owner’s job is to maintain the checklist, coordinate vendors, preserve records and make sure incidents are escalated. CERT-In’s MSME baseline recommends a single point of contact for information-security activities and regulatory communication. Create a one-page contact sheet containing: Security owner and alternate Founder or senior incident decision-maker IT support provider Domain, email and website administrators Bank, payment gateway and UPI provider contacts Accountant or finance lead Cyber-insurance contact, if applicable Legal or privacy adviser CERT-In reporting details National Cyber Crime Reporting Portal and financial-fraud helpline 1930 Do not store the only copy inside the system you may lose access to. Keep an offline or printed copy. Days 1–5: discover what you need to protect You cannot protect an account or device nobody remembers owning. Build a simple asset inventory in a spreadsheet. Record business laptops, desktops, phones, routers, servers, point-of-sale devices and removable drives. Add software and online services: company email, domain registrar, website hosting, cloud storage, accounting, payroll, CRM, marketplace seller accounts, social media, payment gateways and internet banking. For every item, capture: Field What to record Asset Device, application, account or dataset Business owner Person accountable for it Administrator Person or vendor with technical control Data handled Customer, employee, financial or operational data Login method Individual account, shared account, SSO or other MFA status Enabled, unavailable or pending Backup What is backed up, where and how often Criticality What stops if this asset is unavailable Vendor Provider and support contact Exit plan How access and data can be recovered or transferred Prioritise the systems that can move money, reset other passwords, publish as the company or expose personal data. Email, the domain registrar, banking, payment gateways and cloud administration usually belong in the first tier. Remove former employees, unused administrator accounts and obsolete applications. Replace shared logins with named accounts wherever the service permits. CERT-In recommends unique user IDs, role-based access and least privilege because shared accounts make it harder to know who did what. Day-five outcome: one inventory, one owner per critical asset and no unknown administrator accounts. Days 6–10: lock down identities and email Turn on multi-factor authentication for company email, banking, cloud administration, social media, ecommerce, website hosting and the domain registrar. Prefer an authenticator app, passkey or hardware security key where supported. SMS is still better than a password alone, but number-porting and SIM-swap risks make stronger methods preferable for high-value accounts. Give every user a unique password and use a reputable password manager. Never reuse the email password for another service. Store account-recovery codes securely and make sure recovery email addresses and phone numbers still belong to the business. Next, protect the company’s domain from spoofing. Ask the domain or email administrator to configure: SPF, identifying the systems permitted to send mail for the domain DKIM, adding a cryptographic signature to outgoing mail DMARC, instructing receiving servers how to handle messages that fail authentication and providing reports CERT-In’s MSME baseline explicitly recommends SPF, DKIM and DMARC. Roll out DMARC carefully: begin with monitoring, identify legitimate senders such as the CRM or invoicing platform, then move toward enforcement. An incorrect policy can block valid mail. Create one finance rule: any request to change a vendor’s bank account, UPI ID or payment instructions must be verified through a second channel using a known contact—not a phone number supplied in the request. The same rule applies when a founder apparently asks for an urgent transfer. Day-ten outcome: MFA on critical accounts, recovery methods checked, and an authenticated company email domain. Days 11–15: secure devices, Wi-Fi and software Enable automatic security updates on supported operating systems, browsers, business applications, phones, routers and website software. Replace products that no longer receive security updates. Use licensed endpoint protection and leave built-in operating-system security features enabled. Encrypt laptops and phones, enforce screen locks and configure remote-lock or remote-wipe capabilities for mobile devices. Restrict software installation to authorised users. Remove pirated software and unnecessary browser extensions. Change router default passwords. Use WPA2 or WPA3 encryption and place visitors and unmanaged personal devices on a guest network separated from business systems. Do not expose remote-desktop tools directly to the internet. If remote access is necessary, protect it with an encrypted VPN and MFA. Review the website as well. Confirm who maintains its plugins, framework, certificates and backups. A “marketing website” is still a business asset if customers use it to submit enquiries or payments. Subscribe the security owner or IT provider to relevant vendor notices and CERT-In advisories. Patch critical internet-facing systems promptly rather than waiting for the next convenient quarter. Day-15 outcome: supported and encrypted devices, separated Wi-Fi, controlled software installation and an assigned patch owner. Days 16–20: protect payments, vendors and data UPI and other digital-payment processes require operational controls as well as technical ones. Use a dedicated business device or tightly managed user profile for banking and payment administration where practical. Limit transaction rights to the people who need them. Turn on bank and gateway alerts, reconcile transactions daily and review settlement-account changes. Never approve a collect request or scan a QR code merely because a caller says it is necessary to receive money. Separate preparation and approval for higher-value payments. Even if a small team cannot implement formal maker-checker access, require an independent callback before a new beneficiary or changed payment instruction is approved. Now review third parties. List the vendors that can access customer information, email, accounting, payroll, the website or internal systems. Ask: What data and systems can the vendor access? Does each worker use an individual account with MFA? How quickly will the vendor notify us of an incident? Can we retrieve and delete our data when the contract ends? Who removes access when the assigned contractor changes? Does the vendor retain logs and backups appropriate to the service? Is there a named emergency contact? CERT-In’s MSME baseline calls for risk-based vendor due diligence and expects third parties to meet equivalent minimum controls. A contract cannot remove your operational dependence on the vendor. Finally, reduce unnecessary data. Do not retain identity documents, exported customer lists or former-employee records indefinitely merely because storage is cheap. Record why each sensitive dataset is needed, who can access it and when it should be deleted. Day-20 outcome: verified payment-change procedures, daily payment visibility and a risk-ranked vendor list. Days 21–24: create backups that can actually restore the business A synchronised cloud folder is not automatically a backup. If ransomware, accidental deletion or a compromised administrator can alter every connected copy, recovery may fail. Choose the business’s critical data and systems: accounting, invoices, customer orders, website files, operational documents and essential configuration. Set a regular schedule and keep at least one encrypted copy isolated from the main network or primary administrator account. CERT-In recommends a combination of secure offsite and offline copies. Then test restoration. Select a sample file, mailbox, accounting export or website backup and restore it to a safe location. Record: What was restored Which account and instructions were required How long it took What was missing Who can perform the restoration if the usual administrator is absent The test matters more than a green “backup completed” notification. Day-24 outcome: documented backup scope, an isolated copy and evidence of a successful restore. Days 25–27: prepare for a cyber incident in India Write a one-page incident-response card. It should tell an employee what to do when an email account is hijacked, a laptop shows ransomware, the website is altered, customer data leaks or a suspicious payment is made. Use this order: Escalate: contact the security owner immediately. Contain: isolate an affected device or disable a compromised account without unnecessarily destroying evidence. Preserve: retain emails, timestamps, screenshots, transaction IDs and relevant logs. Do not casually wipe or reformat systems. Protect money: notify the bank, payment service or UPI provider. For financial cyber fraud, call 1930 and report through the National Cyber Crime Reporting Portal. Assess reporting: determine whether the incident is one of the categories that must be reported to CERT-In. Recover: reset compromised credentials from a clean device, close the attack path and restore verified data. Communicate: decide who informs employees, customers, vendors, regulators or insurers. CERT-In’s 2022 directions require covered entities—including body corporates—to report listed cyber incidents within six hours of noticing them or having them brought to their attention. Listed categories include unauthorised access, ransomware, phishing, data breaches, digital-payment incidents, compromised social accounts, cloud attacks and attacks on ecommerce or AI systems. Reports may be made to incident@cert-in.org.in or 1800-11-4949. The directions also require covered entities to designate a CERT-In point of contact and maintain ICT logs securely for a rolling 180 days within Indian jurisdiction. Read the official CERT-In directions Because coverage and other notification duties can depend on the entity and incident, obtain professional advice where uncertain. Do not allow uncertainty to delay containment or the collection of basic facts. Day-27 outcome: a usable response card, current contacts and a clear six-hour escalation path. Days 28–30: train, test and assign the next review Run a 30-minute exercise using a realistic scenario: The accountant receives an email from a familiar vendor requesting an urgent bank-account change. Ten minutes later, the founder receives a WhatsApp message apparently confirming it. Ask the team who verifies the request, which known number they call, whether payment is paused, what evidence is preserved and who decides whether the event is reportable. Train employees to report suspicious activity quickly without fear of blame. Cover phishing, password reuse, unsafe attachments, personal devices, public Wi-Fi, payment verification and the handling of customer information. CERT-In’s baseline recommends awareness training for employees and contractors at least twice a year. At the end of day 30, record five measures: Percentage of critical accounts protected by MFA Percentage of supported devices fully patched Number of unknown or shared administrator accounts Date of the last successful backup restoration Time taken to reach the security owner during the exercise Set a monthly access and patch review, a quarterly restore test and scenario exercise, and a six-monthly staff refresher. Consider an annual baseline audit or risk review proportionate to the business. NIST’s small-business guide reinforces this continuing cycle through the functions Govern, Identify, Protect, Detect, Respond and Recover. NIST CSF 2.0 Small Business Quick-Start Guide Low-budget cyber security solutions for business Control Low-budget approach Owner Proof it works Asset inventory Shared spreadsheet with restricted access Operations All critical assets have an owner MFA Built-in authenticator app or passkeys Account owners Critical-account report shows MFA Passwords Business password manager Security owner No shared or reused admin credentials Endpoint security Supported OS with built-in protection IT support Devices report current updates Email authentication SPF, DKIM and monitored DMARC Domain admin Authentication checks pass Backups Encrypted offsite plus isolated copy System owner Quarterly restoration record Payment verification Callback to a known number Finance Beneficiary-change log Vendor control Access list and contract checklist Operations Departed vendor users removed Incident response One-page card and contact sheet Security owner Timed tabletop exercise Staff training Short, scenario-based sessions Team lead Attendance and exercise results The best cyber security tips for a small business are the ones that become routine. Buy new tooling only after identifying the control it will provide, its owner and the evidence you will review. A modest business with accurate inventory, MFA, verified payments, tested backups and a practised response can be better protected than one with an expensive dashboard nobody monitors. FAQs What should a small business protect first? Start with company email, the domain registrar, banking and payment systems, cloud administrator accounts, customer data and the systems required to deliver the core service. These assets can move money, reset other accounts or stop operations. Is antivirus enough for a small business? No. Endpoint protection is useful, but it cannot replace MFA, patching, email authentication, access control, vendor checks, backups and incident-response procedures. Does a small Indian business need to report incidents to CERT-In? CERT-In’s directions apply to specified covered entities, including body corporates, and require listed incidents to be reported within six hours. CERT-In’s MSME baseline also tells MSMEs to follow the directions. Confirm applicability for the entity and event, but create the reporting path before an incident. What are the most useful cybersecurity controls on a limited budget? Asset inventory, unique accounts, MFA, automatic updates, SPF/DKIM/DMARC, payment callbacks, restricted administrator rights, isolated backups and a tested response card offer substantial practical value without an enterprise security stack. How often should staff receive cybersecurity training? CERT-In’s MSME baseline recommends training employees and contractors at least twice a year. Shorter reminders and scenario exercises between formal sessions can keep payment fraud and phishing procedures familiar. What should we do first after a suspicious UPI or bank transfer? Contact the bank or payment provider immediately, call 1930 for financial cyber fraud, preserve transaction details and report through cybercrime.gov.in. Also check whether the event triggers CERT-In or other notification requirements. Sources CERT-In: 15 Elemental Cyber Defense Controls for MSMEs CERT-In Directions under Section 70B, 28 April 2022 PIB: Government Strengthens Cyber Resilience Against AI-Enabled Threats, 30 July 2026 CERT-In Advisories National Cyber Crime Reporting Portal NIST CSF 2.0 Small Business Quick-Start Guide FTC Cybersecurity for Small Business