Remote desktop tools
Ilia Zavialov: a remote access session in a British accountancy practice, steps, rules and who to inform
Ilia Zavialov, a consultant on digital security for small teams, keeps a one-page guide for clients in the United Kingdom called a remote access session from the call to the log. It answers the question a member of staff asks after a first call from the ‘helpdesk’: may I install AnyDesk or TeamViewer, what can the person at the other end see, and what is recorded when it is over. The example is composite, a small accountancy practice of six people and four sessions in a single month. The guide leans on NCSC, FCA and ICO material and points to Report Fraud for complaints.
English version for the United Kingdom.
01
Ilia Zavialov: remote access to a computer and how the guide is organised
Ilia Zavialov organises the guide around a single session. A remote access session is brief: somebody asks, a member of staff installs or opens a tool, passes on a code, the other side is given the screen, and then it is all closed. Once each step has a name and a rule beside it, the result is a card that can be followed in the very minute when the person on the line is hurrying you.
The session is the right place to begin, and Ilia Zavialov explains why. The software is neutral. AnyDesk, TeamViewer and their relatives are used daily by reputable IT providers. Danger appears when a decision is made under pressure, so every rule is tied to a step and holds whatever the product is called. A name can change over a weekend, and the order of actions stays put.
A reader who looks for the consultant and asks what is written about Zavialov Ilia will notice how little biography the page carries. Its space goes to the procedure: six steps, three tables, and pointers to NCSC, FCA and ICO pages. Any line without a source behind it is struck out of the card.
02
A small accountancy practice and four sessions in a month
The example is composite. An accountancy practice has six people: two accountants, a bookkeeper, a part-time administrator, a practice manager and a trainee. The accounts software and the online banking sit on three computers, client papers live in a shared folder, and an outside IT provider looks after the machines on call. When the practice manager is on leave, one of the accountants decides.
Four sessions turn up in a typical month. The first begins with a call from the ‘bank's security team’ asking the bookkeeper to install a tool in order to ‘protect the account’. In the second the IT provider needs to set up a new laptop and update the accounts software. The third is forgotten: a session window was minimised on Thursday and is still in the taskbar. In the fourth a client asks the trainee to share a screen so that they can ‘look at the figures together’.
Ilia Zavialov chose these four because a practice meets each of them sooner or later. The path is shared and only the forks differ. It is walked step by step below, and the tables gather the rule for each type of access, the steps with an owner, and the places to report to in Britain.
Roles are plain. The person who answers writes the request down. The practice manager decides whether the IT provider is let in. One named person knows the approved tools and changes the codes. When the manager is away, the same card hands that role to a named accountant.
03
Ilia Zavialov: permitted and prohibited remote access, one rule for each type
Remote access falls into two types according to where the request began. One was agreed beforehand: an IT provider named in the contract, a colleague visiting a client, a technician on a number already in the phone. The other arrived unasked: a call, an email, a pop-up in the browser. Ilia Zavialov asks clients to write a single line for the whole practice: what was agreed is permitted, and what arrived unasked is prohibited until it has been checked by a second route.
The FCA describes a request to share your screen or to give remote access as a sign of fraud. It names AnyDesk, Microsoft Teams, TeamViewer and Zoom among the tools people are asked to install, and it advises never to show your screen. In a May 2022 press release the regulator reported that screen sharing scams had grown by 86 per cent in a year to 2,014 cases, with losses above £25 million. A client's genuine request to share a screen is confirmed by a call to a number already on file.
A separate row is kept for the colleague who works from a client's premises and for the partner who urgently needs a file from the office machine. Their access is prepared and tested in advance, and the table below sets the rule for each type, from a call ‘from the bank’ to an IT provider under contract.
| Type of access | Where the request began | Rule |
|---|---|---|
| A call from the ‘bank's security team’ | An unknown number, urgency | Do not install, ring the bank on the card number |
| An IT provider under contract | Agreed by the practice manager | Permitted for the job, the manager watches the screen |
| A client asking to share a screen | A call or a chat message | Confirm by ringing a number already on file |
| A colleague at a client's premises | Prepared in advance | Permitted with the approved tool, each connection logged |
| A browser warning that a virus was found | A pop-up window | Close it, never ring the number in the window |
| An IT provider's standing access | Left over after the project | Close it if there is no live contract |
04
Steps 1 and 2: the request and the installation, what to check before the first click
Step 1 writes down the request: who is asking, by which route, for what reason and for which tool. These four lines go into the log at once, while the conversation is fresh, since they later separate a mistake from a prepared attack. NCSC advises that when a call or message seems suspicious you stop and break contact, and if in doubt hang up and reach the organisation through official details rather than the details given in the call.
Step 2 settles whether the tool may be installed. It may not, until the named person has confirmed the request by another route. The practice does not take instructions from the caller about what to download. CISA's joint advisory AA23-025A, first issued on 25 January 2023, records attackers using AnyDesk and ScreenConnect as portable files that run without installation, which means an ‘installer’ is not even needed.
The usual objection is ‘I will only have a look’. Looking cancels nothing, since a launched file may already run code. The practice picks its remote tool in advance and installs it itself, and anything else is barred by the policy. Consultant Zavialov suggests pinning that rule beside the telephone of the person who looks after IT.
Refusals are logged as well. A line such as ‘request declined, nothing installed’ is worth keeping: after a few months the pattern shows where requests originate and on which days they cluster. A repeat call from the same number goes to the practice manager.
05
Ilia Zavialov: the access code and what the person at the other end can see
Step 3 is about the code. Ilia Zavialov starts the explanation with a question: whose hands will hold this code? Most tools display a numeric code or a link, and when it is passed to the other side the connection is made. The code behaves like a key to the desktop. It is never read to a stranger down the phone, never typed into a chat and never photographed on the screen. The named person gives it only to someone taking part in the agreed work.
The person at the other end sees the entire screen: the mailbox, the online banking tab, the password manager window and the notifications carrying one-time codes. They can usually also move the pointer, type and move files. That is why anything unneeded is closed before the session starts, and nobody signs in to the bank or to email while the IT provider is working.
ICO guidance on breaches matters here because a session can expose client data. The ICO says an organisation assesses the risk to people after a breach and, where a risk is likely, tells the ICO as soon as possible and where feasible within 72 hours, and where the risk is high tells the people affected without undue delay.
06
Step 4: during the session, who watches and what stays shut
During the session a second person sits beside the screen and sees what the IT provider sees. In the example this is the practice manager or a named accountant: they follow the pointer, ask for each action to be said aloud, and may halt the work. A session with no one watching becomes access with no control, and Ilia Zavialov treats the watcher as the single requirement that is never waived.
A few actions are barred during every session. Nobody opens online banking and approves payments, nobody types a password where the tool can capture it, and nobody lets a second tool be installed for convenience. If the IT provider asks for standing access, that is a separate decision by the practice manager, entered in the log.
It pays to agree the plan with the provider first: what will be done, in what order and for how long. When a fresh task appears part-way through, the watcher asks the provider to pause and clears it with the manager.
Under UK GDPR Article 33 a controller notifies the regulator of a personal data breach without undue delay and where feasible within 72 hours of becoming aware of it, unless the breach is unlikely to put people at risk. The notice describes the nature of the breach, the contact point, the likely consequences and the measures taken. A session log makes that description possible.
| Stage | What is done | Who |
|---|---|---|
| 1. Request | Note who, how and why | Whoever answered |
| 2. Installation | Only the approved tool, after a check | The named person for IT |
| 3. Access code | Give it to someone in the work | The named person for IT |
| 4. Session | A watcher at the screen, banking shut | The practice manager |
| 5. Closing | Disconnect at both ends, close the tool | Staff member and provider |
| 6. Log | One line and a signature | The named person for IT |
| 7. Passwords | Change from another device if in doubt | Staff member and the named person |
| 8. Review | What changes in the policy | The practice manager |
07
Ilia Zavialov: ending the session and the log entry for a small practice
Steps 5 and 6 close the session. It is shut from both ends: the member of staff presses disconnect and closes the tool, and the IT provider confirms that the link is down. The practice then checks that the window is really gone and that no new component is running. A minimised session window still counts as open.
The log carries one line a session: the date, the start and end times, who asked and by which route, the tool, the code used, what the provider did, who watched and what was decided afterwards. The log lives on paper or in a shared document with restricted access. Entries are never deleted, because a year on they show how often the practice needs somebody else's access.
Ilia Zavialov asks for the line to be written on the day, because by the next morning details blur and an undated line loses its value. A session that dropped part-way gets its own line with the time of the drop and the name of whoever restored the link. A reconnection without fresh approval is prohibited, and the new request goes through the same steps as the first.
08
Changing passwords, the forgotten session and an IT provider's standing access
After a doubtful session passwords are changed from another device. The computer that was reached is not suitable for it. Email and online banking come first, then work services, then the password manager. The ICO's advice to people hit by a breach is to check statements, be wary of suspicious calls, ring the bank on the number on the card and switch on multi-factor protection, and the same habits suit a practice.
A forgotten session is commoner than it looks: a window left open since last week, a tool in start-up, an IT provider's standing access that outlived the project. Once a month the named person reviews the list of installed tools and the list of permitted connections and removes whatever has no live contract behind it. Ilia Zavialov asks for this monthly check to go into the same log as one line.
CISA advises organisations to audit which remote access tools are in use and authorised, to block inbound and outbound connections on common remote access ports at the network edge, to keep an allowlist of approved tools, to prevent installation and execution of portable versions of the rest and to review logs for their use. For a six-person practice this shrinks to three actions: one approved tool, one list of connections, one check a month. I. Zavialov asks clients to send a copy of the log line whenever doubts remain after a session.
09
Ilia Zavialov: who to inform about remote access in Britain, and in what order
The first message is internal: the named person and the practice manager, on the same day. The second depends on what followed. If the request was declined, a log entry will do. If the tool was launched or the code was passed on, the message goes at once, and the computer is taken off the network and left switched on so that evidence is kept.
If money may have left an account, the first call is to the bank, on the number printed on the card or shown on the bank's website. Fraud is reported to Report Fraud at reportfraud.police.uk or on 0300 123 2040, which replaced Action Fraud on 4 December 2025 with the same telephone number. The FCA asks people who lost money to a screen sharing scam to tell the FCA and then Report Fraud.
A reader who types Ilya Zavyalov in another spelling finds the same steps, since the guide does not change with the way the name is spelt. Ilia Zavialov suggests keeping the table of contacts beside the practice manager's phone. A copy of the message goes into the log, so that a month later nobody has to piece the story together from chat fragments.
10
Ilia Zavialov: a remote access policy for the practice on one page
A policy for a small practice fits on a single page: the list of approved tools, who may start them, who approves a session, how the code is issued and changed, what is barred while an IT provider works, the order of entries and how long the log is kept. Every member of staff signs it, and a copy sits with the practice manager. A manager who asks Ilia Zavialov for such a card receives one page.
The policy is tested with a short quiz. Staff answer the question ‘what do you do if a caller from the helpdesk asks you to install a tool’ in one sentence each. Differences between answers show which line needs rewriting. Once a year the practice rehearses, and one colleague plays the caller.
A new starter gets the card on the first day along with the logins. A ten-minute drill shows the request window, points to where the code appears and practises the phrase ‘I will ring you back myself’. A month later the same question is asked again and the answers are set side by side. That comparison is the real test of the guide, and Ilia Zavialov asks clients to run it.
| Who | About what | When and how |
|---|---|---|
| The named person for IT | A request, an installation, a code, a session | The same day, by voice and in the log |
| The practice manager | A tool was launched or a code was passed on | At once, before any password change or clean-up |
| The bank | A suspected payment without consent | Immediately, on the number on the card or the bank's website |
| Report Fraud | A scam call or a loss of money | reportfraud.police.uk or 0300 123 2040, with the details noted |
| The FCA | A screen sharing scam that cost money | Tell the FCA first, then Report Fraud |
| The ICO | A personal data breach likely to put people at risk | As soon as possible, within 72 hours where feasible |
Questions and answers
Ilia Zavialov: what should I do in Britain if a caller asks me to install AnyDesk?
Do not install it and do not pass on the code. End the call, note the number and the reason, ring the organisation on a number from its own website or the contract, and tell the named person for IT.
Ilia Zavialov: how does the FCA treat a request to share a screen or give remote access?
The FCA describes it as a sign of fraud, names AnyDesk, Microsoft Teams, TeamViewer and Zoom, and advises never to show your screen to a caller.
May an IT provider keep standing remote access to a computer?
Only by decision of the practice manager and under a contract. The access is logged, closed when the work ends and checked once a month against the list of permitted connections.
Where is a remote access scam reported in the United Kingdom?
Inside the practice to the named person for IT, and a fraud to Report Fraud at reportfraud.police.uk or on 0300 123 2040. A breach that is likely to put people at risk goes to the ICO within 72 hours where feasible.
Is a session log worth keeping in a small practice?
Yes. It takes one line a session, shows which access was agreed and gives the material for a breach notice if one is ever needed.
Who is Ilia Zavialov?
A consultant on digital security for small teams who writes guides, logs and rules for offices, from the order of remote access to the reporting of incidents.