GUIDE · PROFESSIONAL FIRMS SECTOR

IT for professional firms: security, privacy and continuity

This guide explains what cyber security means for a professional firm, which data and systems must be protected and which confidentiality and privacy obligations matter. By the end you will know where to start, which topics to explore and how to discuss priorities with your IT supplier.

Updated october 2026
10 min read
Altovar Technical Editorial Team

1. What we mean by cyber security in a firm

For a professional firm, cyber security is the set of measures that prevent people who should not see the data from accessing it, that keep it intact, meaning unaltered and not lost, and that make it available when needed. These are three distinct properties that often pull in different directions: confidentiality, integrity and availability. The firm already knows professional secrecy as a duty. What changes with digital is the perimeter: client files no longer sit in a locked cabinet, but on computers, servers, cloud services, email and phones.

Distinguishing the three concepts helps decision-making. An attack that encrypts all the firm's files hits availability. An email sent to the wrong recipient hits confidentiality. A document altered without anyone noticing hits integrity. The measures for each case differ, and your IT supplier should be able to tell them apart without using the word security as a slogan.

2. What data and systems a firm actually handles

The first step is to inventory what the firm uses, not what the supplier has installed. Inside are client files, accounts or case files, correspondence, digital signatures, credentials for public portals and documents exchanged with counterparties. Each category has a different level of sensitivity and a different retention period, which depends on the type of document and the obligations of the profession.

The table shows the most common systems, the main risk and the question to ask the supplier. It does not need to be perfect at the first attempt, but it must exist and stay up to date when the firm hires a collaborator, changes software or opens a new channel with clients. An inventory left untouched for years no longer describes the real risk. Once the table is ready, compare it with the actual list of people using each system, because the differences between the two documents are often the first risk to close.

SystemData involvedMain riskQuestion for the supplier
Computers and laptopsLocal copies of files and emailTheft or malwareWho manages updates and disk encryption?
Practice management softwareClient records, cases, feesUnauthorised access and data lossWho creates and revokes accounts, and where are the backups?
EmailCommunications with clients and counterpartiesPhishing and sending to the wrong recipientsWhat authentication is required, and how are attachments handled?
Shared archive or cloudComplete filesOpen sharing and accidental deletionWho sees what, and how is a previous version restored?
BackupsCopy of everything elseUntested copy, or one connected to the infected networkWhen was the last full restore tested?

3. Confidentiality and availability: two goals to balance

The firm often needs two things that seem to conflict: documents must be accessible to those working on them at any time, including from outside the office, and nobody else must be able to read them. Measures that are too rigid block the work: passwords that are impossible to remember, access that requires a technician every time, or a single account shared by everyone. Measures that are too lax leave open the risk of stolen credentials or a forgotten external share.

The practical way to balance is to decide, for each type of data, which goal prevails. For the most sensitive files, confidentiality prevails and access requires more steps. For the diary and operational documents, availability counts for more, and a lighter control is accepted alongside robust backup. Writing this decision down prevents it from being reopened every time an incident happens.

4. Privacy and confidentiality obligations: the general picture

A firm that processes personal data is subject to the GDPR, the European regulation on data protection. The regulation requires processing only the data that is necessary, protecting it with measures appropriate to the risk, limiting access by role and knowing which processing takes place. For personal data breaches that pose a risk to individuals, notification to the authority must be made within 72 hours of becoming aware of the event. That is why you need to know who decides what in case of an incident, before it happens.

Professional secrecy is a duty that derives from the profession and the rules of the relevant professional body, and does not depend on whether the data is on paper or digital. If the firm gives a supplier access to its systems, the duty of confidentiality must extend to them through written agreements. Where applicable, the NIS2 Directive, transposed in Italy by D.Lgs. 138/2024, may add risk management obligations: it depends on size and activity, so it should be checked with an adviser.

5. Common mistakes

The first mistake is thinking security is only the supplier's problem. The supplier installs and configures, but decisions about who accesses what and which data is used remain with the firm. The second is believing an antivirus is enough. An antivirus helps, but it does not replace personal accounts, updates, separate backups and an incident procedure. The third is treating security as a one-off project.

A fourth mistake concerns external collaborators: a consultant with permanent access to the management software, a technician who still holds the credentials of an old engagement, an account shared by several people. Every exception left open becomes a forgotten risk. Periodically request the list of active access and compare it with the people who really work in the firm. The remedy is simple but must be repeated: at every change of engagement, and at least once a year, the principal checks access and signs the list.

6. A generic example: the email asking to change the bank account

Imagine a firm with a few collaborators and a shared management system. One day an email arrives that appears to come from a regular client, asking to change the bank details for a payment. The message is well written and carries the correct signature, and one of the collaborators is about to make the change. This is a typical fraud case that touches confidentiality and, indirectly, the client's trust.

No technical measure alone stops this case. A procedure is needed: every change of bank details is verified by a phone call to a number already known, not to the one given in the email. Email access with strong authentication is also needed, so that the theft of one password does not give access to everything. And staff must know what to report and to whom. The supplier can help build these steps.

7. Which topics to explore, and in what order

This guide is the general map. Some topics merit dedicated in-depth guides, and it is best to read them in a precise order. The first is professional secrecy and the obligations of those who hold it, because it defines what is sensitive and what is owed. The second is how to exchange documents with clients without losing control, because that is where data most often leaves the firm. The third concerns remote working and the management of permissions between partners and collaborators.

The other topics follow from these: how to sign and store documents with legal value, how to archive digital files and for how long, how to choose between a cloud management system and one installed in the firm, and how to recognise fraud that uses falsified voice and video to appear as known people. An operational checklist closes the picture. The advice is to read the topic on professional secrecy first and do the checklist straight away, so you have a concrete starting point.

8. When security becomes a business decision

Security enters decisions when the firm changes software, hires collaborators, opens a new office, adds a channel with clients or evaluates a new supplier. At each of these moments, ask what effect the choice will have on data, access and continuity. It is not a technical constraint to delegate: it is part of the choice, like cost or start-up time.

Continuity also matters. If the firm's system stops for a day, how much work is lost, which deadlines are at risk and who responds to clients? These questions do not require technical expertise to ask, and the answer guides investment priorities better than any list of tools. Write the answers on a single page, because a topic with no owner and no recorded recovery time remains, in practice, unresolved.

9. How to start

This week do two things. First, write the list of the firm's systems and data, even in a simple form, with the name of whoever manages each one. Second, ask your IT supplier for the list of active accounts and the date of the last backup restore test. If either answer does not arrive or is vague, you have already identified the first point to fix. Also note the date you made the list, so you know when to review it.

Then choose the most urgent topic for your firm, usually professional secrecy or document exchange, and set a short meeting with the supplier and, if needed, a data protection adviser. There is no need to complete everything within a month: what matters is that decisions are written down and that someone is responsible for them. Bring the list already prepared, so the meeting stays short.

Frequently Asked Questions

Does a small firm really need to worry about cyber security?

Yes. Client data has the same value regardless of the size of the firm, and a small firm often has no staff dedicated to security. The complexity of the measures changes, not the substance: personal accounts, updates, separate backups, procedures for changes to payment details and a supplier who responds. A consultant or the supplier can define the level proportionate to your activity.

Is an antivirus enough to protect the firm?

No. An antivirus is a useful but partial measure. It does not protect against an account with a weak password, a well-crafted phishing email that leads to credentials being handed over, a forgotten external share or accidental deletion. You also need strong authentication, separate and tested backups, and a written incident procedure.

Who is responsible for security: the principal or the IT supplier?

The principal remains responsible for decisions: which data to process, who can access it and which suppliers to use. The IT supplier is responsible for carrying out the technical parts entrusted to it, and this must be written into the contract. Where responsibilities are unclear, problems have no owner until the first serious failure.

When must I notify the Garante, the Italian data protection authority, of an incident?

For personal data breaches that pose a risk to individuals, notification to the authority must be made within 72 hours of when you became aware of the breach. This is not a deadline to discover during an emergency. Prepare in advance a procedure that says who assesses the incident, who drafts the notification and who decides, and check the details with an adviser.

Is cloud less secure than a server in the office?

Not automatically. It depends on the supplier, the configuration, the access and the handling of backups. A poorly configured server in the office can be more exposed than a well-managed service. The useful question is who controls what, where the data is stored and who can lawfully access it, and the answers should be requested in writing.

Where do I start if I have little time?

Make an inventory of systems and data, request the list of active accounts and check the last restore test. Then use the operational checklist and choose a single point to improve within the month. With little time it is better to do a few verifiable things well than to make many generic statements.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →