Skip to content
Home » Security Basics & Strategy » Cybersecurity Is a Business Decision for CA Firms, Not Just an IT Issue

Cybersecurity Is a Business Decision for CA Firms, Not Just an IT Issue

A group of business professionals in a boardroom discussing a presentation about cybersecurity on a large screen.

Most CA firms leave cybersecurity to whoever looks after the computers: a part-time vendor, a nephew who “knows IT”, or the staff member who set up Tally. That made sense when the server was a filing cabinet. Today one Windows server holds every client’s books, returns, bank statements and portal passwords, and the duties that come with that data fall on the partners, not the vendor. Cybersecurity for CA firms is a partner’s decision about client trust, professional duty and money. This post sets out what the firm holds, which laws and rules apply, a simple way to set a yearly budget in rupees, and what to ask your IT vendor.

What your server actually holds

Walk through the shared folders on a typical practice server and you will find:

  • TallyPrime company data for dozens or hundreds of clients, often for several years.
  • GST returns, reconciliations and e-way bill records.
  • Income-tax workings, ITR acknowledgements and audit working papers.
  • Bank statements, PAN and Aadhaar copies, and payroll data for clients’ staff.
  • A spreadsheet or notebook of clients’ income-tax, GST and bank portal passwords.

That last item matters more than most partners realise. Under the IT Act’s SPDI Rules 2011, passwords and bank account or card details are “sensitive personal data”. A firm that holds them has legal duties today, not only from 2027.

The duties that sit with the partners

None of these can be handed to an IT vendor by contract. The vendor can do the work; the duty stays with the firm.

ICAI: client confidentiality

The Chartered Accountants Act 1949, Second Schedule, Part I, Clause (1), makes it professional misconduct for a member in practice to disclose information acquired in a professional engagement without the client’s consent or a legal requirement. Members in employment have a similar duty under Part II. The duty continues after the engagement ends. Whether a leak caused by weak security counts as misconduct would be decided case by case, but after an incident you would want to show a client, or ICAI, that the firm took reasonable care. The penalties for misconduct range from a reprimand to removal from the register, or a fine of up to ₹5 lakh (section 21B).

IT Act section 43A and the SPDI Rules (now)

For section 43A, a “body corporate” includes a firm or sole proprietorship carrying on professional activities. A firm that handles sensitive personal data must follow reasonable security practices backed by a documented security policy, and can be made to pay compensation to the people affected if it is negligent and they suffer loss. These rules apply until the DPDP Act’s main duties start.

CERT-In: six hours, 180 days (now)

The CERT-In Directions of 28 April 2022 require reportable cyber incidents, ransomware and unauthorised access among them, to be reported within six hours of noticing them, and logs of ICT systems to be kept for 180 days, within India. CERT-In’s FAQs (May 2022) treat a firm as a body corporate and say the reporting obligation cannot be transferred, so your IT provider cannot report on your behalf. Reports go to [email protected]. Six hours is not long on a Monday morning when nothing opens; decide now who in the firm makes that call.

The DPDP Act 2023 and Rules 2025 (from mid-May 2027)

The DPDP Rules were notified on 13 November 2025, and the main duties apply from mid-May 2027. For most of the personal data it holds about clients and staff, a CA firm will be a data fiduciary; where it only processes data on a client’s behalf, such as running a client’s payroll, it may be a data processor instead. A data fiduciary must:

  • take reasonable security safeguards, including keeping logs for at least one year;
  • tell the Data Protection Board and each affected person of a personal data breach without delay, with a detailed report to the Board within 72 hours;
  • publish a contact for questions about personal data and handle requests to access, correct and erase it.

The Act’s Schedule sets penalties of up to ₹250 crore for failing to take reasonable security safeguards and up to ₹200 crore for failing to report a breach. Those are ceilings, not typical fines: the Board must weigh factors such as the gravity and duration of the breach and whether the penalty is proportionate. Even so, they show where the law puts the weight: on safeguards and on telling people. On the same date, section 43A of the IT Act is omitted. The government consulted in January 2026 on shortening the run-up, so check the current commencement date before relying on it.

Your clients’ record-keeping duties

GST records must be kept for 72 months (CGST Act section 36), and companies must keep books of account for eight financial years (Companies Act section 128). If your server holds the only working copy of a client’s Tally data and ransomware destroys it, the client’s compliance problem becomes your relationship problem. Treat backups as part of the service you sell to clients, because in their eyes they are.

This section is general information for CA firms, not legal advice. Take advice on your own engagement letters and on what to tell clients after an incident.

What a bad week would cost your firm

Industry averages for breach costs come from large companies and say little about a 15-person practice (our post on the real cost of a data breach covers what they do and do not tell you). It is more useful to put your own numbers on one bad week. Take a sheet of paper and fill in:

  1. Work stopped. Your average fee billing per working day, multiplied by the days the server could be down. If the backups work, a rebuild and restore takes days; if they do not, the Tally data has to be re-created from client records.
  2. Timing. The same week in September or July costs more than in a quiet month, because filing and audit deadlines do not move and clients’ late fees and interest become a conversation with you.
  3. Recovery. Vendor hours for the rebuild, new hardware if needed, and partner time on calls with clients, the bank and CERT-In.
  4. Clients lost. How many clients would quietly move to another firm after being told their data may have been copied? What is their annual fee?

An example with made-up numbers: a firm that bills ₹1,00,000 a working day and loses five working days in September has ₹5 lakh of work stopped before a single vendor invoice, and that is if the backups restore. Losing three clients on ₹1.5 lakh a year each adds ₹4.5 lakh a year for as long as they stay away. Your numbers will differ. The point is to have them in front of you when you look at the budget.

A simple yearly budget, line by line

Now list what the basics cost per year. Get the quotes from your vendor; the table shows what each line buys and where a figure is known.

LineWhat it buysYearly cost (₹)
Private remote access for home and travelling staffRemote Desktop closed to the internet; staff connect through an encrypted tunnelPrixl Warden + Guard is ₹14,999 a year per server with 5 seats included, plus ₹600 for each extra person, so ₹16,799 for 8 staff (see pricing); or your vendor’s VPN / RD Gateway quote
Backups3-2-1 copies, one offline or immutable, and a restore test of the Tally data each quarterVendor quote (drives, cloud storage, their time)
Supported WindowsSecurity updates. Windows Server 2016 support ends on 12 January 2027 (Microsoft lifecycle)Licence and migration, spread over the server’s life
AntivirusMicrosoft Defender is built into Windows and Windows Server; check it is onUsually nil
Monitoring and alertsSomeone is told the same day when sign-ins, accounts or the firewall look wrongSee Warden pricing
Vendor reviewA quarterly check of the items below, with a short written noteVendor hours

Then compare the total with one bad week. If the yearly spend is a small fraction of a single bad week in September, the decision makes itself. If money is tight, spend in this order, because each step removes more risk per rupee than the one after it: close Remote Desktop to the internet, get an offline backup and test a restore, move off unsupported Windows, then add monitoring. Write the decision down with the date. If a client or ICAI ever asks what the firm did to protect their data, a dated, costed decision is a far better answer than “the vendor handles it”.

What to ask your IT vendor

You do not need to understand the technology to ask these. You need clear answers, in writing.

  1. Can anyone on the internet reach our server’s Remote Desktop? The right answer is no, tested from outside the office network, with staff connecting through a VPN, RD Gateway or a private tunnel. See how to lock RDP down.
  2. When did you last restore our Tally data from backup, and how long did it take? A backup nobody has restored is a hope, not a backup.
  3. Is one backup copy offline or immutable, so that someone signed in to the server cannot delete it?
  4. Who has administrator rights on the server, and why? Ask for the list of names. Shared “admin” logins should go.
  5. What is our minimum password length, and is there a second factor on remote access? We recommend at least 15 characters, as NIST SP 800-63B-4 does; Windows Remote Desktop has no second factor of its own.
  6. Which Windows version is the server on, and when does its support end?
  7. Are Windows Firewall and Microsoft Defender on, and how would we know if someone switched them off?
  8. Are the server’s logs kept for 180 days, as CERT-In requires? Our recommended audit policy covers which events to record.
  9. If we are hit on a Saturday, what do you do in the first hour, and who in our firm reports to CERT-In? Our incident response guide sets out the steps.

Where Prixl fits

Prixl Warden runs on the server and emails the partners, in plain English, when the server’s logs show something that needs attention: password-guessing campaigns, sign-ins outside working hours, new accounts or admin-group changes, a cleared audit log, or the firewall being switched off. Serious events are emailed immediately, the rest come in a daily digest at 18:00 IST, and a weekly summary arrives every Monday at 08:00 IST. Its 29-check security audit helps answer several of the vendor questions above, and on paid plans 21 of the checks have a one-click fix. Event history is kept for 30 days and stored in AWS Mumbai; keep the full Windows logs as well, because Warden’s history is not a substitute for the log archive CERT-In asks for.

Prixl Guard handles the first line of the budget: invited staff reach the office server through an encrypted tunnel, without a static IP or router changes, so Remote Desktop can be closed to the internet. The staff app is for Windows 64-bit today.

Neither replaces backups, updates or a good vendor. They make sure the partners hear about trouble the same day. Start your 30-day free trial, and read why simple, proactive security wins for small businesses for the thinking behind it.

Leave a Reply

Your email address will not be published. Required fields are marked *